lorenzq

I don't know, he made a great point about `useEffect` and its data flow and composability problem, which I've known for some time. The part about top down state being one giant mutable variable is true, but it's also how functional programming languages do it with a state-monad-esque runtime, like Elm. It's mostly a footgun when you're irresponsible cutting across many redux state machines in a single component.

I think the author is kind of a mediocre frontend eng but it's also true that modern react + hooks are full of footguns that can get very ugly. It's the opposite outcome of what react was originally designed for, to make it easy to do the right thing.

There are >1000 Algorand validators[1] and >2000 Cardano validators[2]

[1] https://metrics.algorand.org/

[2] https://pooltool.io/

Heat dissipation is the killer

I really enjoyed Harry Potter and the Methods of rationality. I understand not everyone would like such an intelligent main character though.

Campendium misses a lot of actual spots. It might have one camping spot listed for a 25 mile radius but there are actually tons of spots in that area. It's not precise enough imo and only guides me where to start looking on satellite photos and BLM maps again.

How do you find BLM spots?

I've often had to resort to google satellite photos and referenced flat dirt patches with BLM territory maps to make sure I wasn't on private land. Wish there was an easier way.

Seriously? Who cares? That's not target demographic.

The point of a flagship phone is to push the envelope, not compete with midrange devices. If someone else is filling the midrange niche better than Google I don't really see a problem, buy that phone instead. Google can better differentiate with a flagship and by doing so pushes the rest of the industry forward on features. These features that were costly to develop will later propagate to midrange.

Stop using a big bank then

Tech workers are still a minority in the bay area.

Lets not forget property taxes, which would wipe out again half of that if not almost all of that.

Because a house is a 15 or 30 year loan. Their job market or high pay may not extend that long

[citation needed]

I need enough money to support myself and have influence while working on things society will not pay me for yet will benefit them all long term.

Why would you only have 2% yield?

You don't want to buy your groceries when they're not on sale.

Take ETH and ETC for example, they both have the same address format and accidentally sending from one chain to another results into your crypto being locked away forever.

What does implementing the cpu with logic gates entail? Does the compiler run on top of that metal you build? I’ve been thinking about how best to start from the bottom and I was thinking of getting a cheap fpga to build a cpu and compiler on. How does this course compare?

If you have a salaried job how do you justify spending that money when you can’t earn more money outside of your salary?

I read an ars technica article that this would be a possible solution but isn’t right now because the hardware to check access rights isn’t fast enough yet

If that older Unix or C++ programmer doesn't have a strong bias against Javascript, functional programming, new es6/es7 concepts, and web appliactions in general, then sure. I see many of these types of people even on HN with biases though.

Age shouldn't be used as a catch all filter, but I can see how it might be faster to screen those who have been too content to stick to their tools without catching up to industry trends.

Ohm's law was not derived. It probably shouldn't be called a law either. Capacitance, etc. can be found in Introduction to Electrodynamics by Griffiths, which is a standard E&M college text.

They've started kicking those people out again (around 7%). They check performance on your daily problems, how much you contribute to the peer projects, and a hard cut at a midterm exam where they record your screen and make sure you're not just copying solutions. They also weed people out on behavioural teamwork issues.

Some of the people who got kicked out just dropped back to the next cohort though, which is severely disappointing, because on top of paying the full tuition they are likely to fail again. I checked and there's no way those people can catch up based on their code, they're the kind of people Jeff Atwood talks about. https://blog.codinghorror.com/why-cant-programmers-program/

This is definitely the case. I got accepted to both HR and Dev Bootcamp. I chose HR because it had the better reputation and had released outcomes statistics. HR had tougher requirements to get in, you had to understand more programming than a freshman or sophomore college student. Dev Bootcamp accepted me with a logic puzzle and basic if statements and for loops. There was no competition.

HR's recent purchase of Makersquare has me a bit worried that they are outstripping the supply of smarter incoming students but I can't say for sure yet without interviewing a larger sample.