HN user

ahpearce

47 karma

Data Scientist, Software Engineer, aspiring ramen chef

Feel free reach out: adamp319@gmail.com

Posts0
Comments65
View on HN
No posts found.

Sony A7III. It has been great. The camera market has really had to keep up with smart phones so there are a lot of good options. Depending on budget, I would look at the Fuji mirrorless cameras (I think X100F, XT3, etc?). Maybe even a Ricoh GRIII if you're into travel, street, or architecture. As others have said, it will depend on what you want to shoot.

But in the markets, it is not about the technical definition of Bitcoin, it is about how the average market participant interprets what Bitcoin is... Being technically novel does not protect Bitcoin from being treated like currency, and it doesn't alleviate the negative impact of people's (erroneous) conceptualization of it.

I've been doing this a lot lately as well. It's just really easy to have a directory of compose scripts in your home dir, and setup a simple bash alias/func to stand up a quick database.

I'm really not following the logic here. Are they pointing at the jump in D vote share, and then pointing at the influx of Milwaukees ballots? Milwaukee is excessively blue (86% to Biden). Why wouldn't the vote share change drastically as that county came in? This is basic math. How does this point to fraud?

Also hilariously, they're basing their whole argument off of this apparent "trend" that they haven't supported of mail-in ballot share shifting from D to R... But then they provide an example of Georgia, where... that isn't at all the case... and then gloss over it. Laughably bad analysis.

Took 20 minutes to confirm the "trend" and immediately none of the following states follow the "trend": Alaska, Florida, Hawaii, Illinois, Indiana, Maryland --- aaaand I've stopped looking because this is silly.

Full disclosure, this was just a quick visual inspection of the data presented, plotting x='vote_share_dem' against 'timestamp'.

That is exactly the problem, though, isn't it? Unaccountable third parties are literally currently controlling the truth, via disinformation. An alarming number of people are convinced in conspiracies and untruths like the deep state, QAnon, anti-vax, flat earth... How is the ability to freely and massively distribute misinformation not a means of controlling the truth?

I think in that case, people need to pony up something of value to contribute and participate in such an environment. There are a few cases where I think this has succeed, in communities like ChangeMyView on reddit... Paid communities are kind of already starting to take off. I wonder if you could couple a subscription model and a minimum word count, with heavy moderation (of the right kind)... It'd be hard to pull of.

This is exactly it. People in this thread are saying "I don't understand why it's so crazy to say 'I'm not taking sides'"... Well because it clearly communicates that you still think there are "two sides", and that they're equivalent. That is clearly not the case, and if someone thinks otherwise, I don't even know how to have a conversation with them.

I'm not sure why they separated them. Spring is Spring imo. There's a lot of tooling that is very quickly accessible and "just works". We have 15 microservices and three or four UIs that are all Spring backend with React frontends and it isn't even a little cumbersome. We don't serve the static content from Spring as a webserver though (we use a separate nginx instance).

Vue.js 3 6 years ago

AlpineJS? A bit polarizing, but definitely lightweight...

Sorry to be a bit pedantic, but circadian rhythm is "a natural, internal process that regulates the sleep-wake cycle and repeats roughly every 24 hours." I believe you meant REM cycles, in your first sentence (which matches up to your next sentence).

That is not always a great idea. There is a reason APIs exist, and backend service layers exist on top of databases. It is a larger abstraction of the interface design pattern.

It only makes sense if you're absolutely sure you'll never need to extend or change the interaction between front-end and back-end.

Think just about schema migrations on the database. If you change your schema, you have to change your front-end. Maybe that's okay for the time, but that can get out of hand pretty quickly.

On the other hand, with a service layer, you could completely decouple that dependency on the front-end, by providing the front-end an interface (the service layer / API). The migrations on the database layer don't affect the front-end whatsoever, because the front-end communicates with the interface. You can change the underlying implementation without changing the front-end's interaction with the interface.

http://best-practice-software-engineering.ifs.tuwien.ac.at/p...

I also have a background in statistics, but landed a job as mostly a software engineer (though technically my title is Data Scientist... buzz words!). I've been building basically a cookiecutter framework for the base of a SaaS app (basic pricing, user auth, etc.), and brainstorming ideas.

As others have said, the ideal route is to validate the market first, and guarantee customers before effort is committed.

If you'd like to tag up, just to chat casually about the idea or just entrepreneurship in general, feel free to e-mail me (in bio).

It wasn't immediately apparent based on the landing page, that I would be able to export my finished novel, or that you provide some sort of security for my work (syncing, backups with Dropbox, Google Drive, maybe?). I think those will be people's two biggest questions or apprehensions.

I kind of hate the scrolljacking. It's too flashy. It's sluggish. It is kind of distracting. I think the small gif of the kanban is much more effective, and the rest of the copy is too.

Maybe a bit of top padding on the 'CenterCallout' where you say "Writing is just one click away" and "A new way to note".

You might want to sprinkle one or two more calls to action for purchase or trial in between some of the feature descriptions.

Otherwise, the kanban setup for chapters and such seems really intuitive and I'm surprised I haven't seen that before in this context. I'd definitely be interested in giving it a shot. Maybe paying the $8 will encourage me to write more. I'll bookmark it to check out after work!

rapidly test the efficacy of a vaccine

How do you test the efficacy if you don't know who you're injecting? Maybe it works really well on a certain population, and reacts harmfully to people with some pre-existing genetic trait or condition. You wouldn't know, because you took a random set of volunteers.

If you're going to counter and say "we'd still do the pre-analysis on the volunteers"... Well, that's what takes time.

As others have said, there may not be an 'event'. Some metrics need to be monitored manually before setting up an event to trigger. Sure, you might have engineers analyzing the time series data, but you also need to keep your systems up. There are multiple failure modes for various services that may require different action.

For example, perhaps you have some poorly written legacy service that has a memory leak. Let's just say for the sake of this argument, that any sort of boolean indicators (e.g. checking if the process is running) will give you an 'Okay' or green. You are still probably interested in monitoring the memory usage to make sure the service is operating correctly and/or performant. After monitoring for some time, maybe you determine your ops engineers are taking some action whenever the memory gets around 80% or something... then you can setup the trigger event. But without that manual monitoring upfront, you can't just magically set that threshold.

How does a guitarist get more "productive" in terms of speed and quality? Practice.

Build things you want to use. Or build things other people want to use. Do practice problems online (LeetCode, Project Euler, etc.). Read more documentation.

Pick a tech stack that you want to become an expert on (preferably an employable one), and start learning. Buy the books.

It sounds like you're feeling a lack of confidence in your knowledge and abilities, and the only way to improve those is to continue learning and improving.

One other consideration is: do you spend a significant amount of time on repeated processes? Perhaps during development you're 1) logging into your database, 2) dropping some tables, 3) re-running some tests that populate the database, 4) viewing the results. Can you automate such processes? Can you put together a few scripts or utilities that make you more efficient? Can you find boilerplate or scaffolding that gets you 20-30% of the way there rather than starting from scratch?