dsirola

It's not impossible, but I wouldn't say it's worth it. From my experience, there is more ageism in programming than there is in management so it would be even more difficult to find work, especially without prior experience.

> It may cause digestive distress. "People with dairy allergies or trouble digesting lactose [milk sugar] can experience gastrointestinal discomfort if they use a milk-based protein powder,"

What alternative do they suggest?

- 6 ounces of plain Greek yogurt

- a cup of milk

I know there are lactose free version of those, but there are also lactose free versions of the proteins...

True, but I see a trend where everybody is trying to "hack" reading by listening to audio books on 3x or other tricks which is a complete nonsense for professional books and absorbing the information.

What's the point? If you enjoy reading and reading for fun then you'll just read as much as is fun for you. If you're reading professional books, then the quantity doesn't matter. I would rather spend a year with a single book like "Designing Data-Intensive Applications" revisiting chapters and reiterating same things to really absorb that knowledge than rush 1 book per week/month/whatever.

I have one but it's been sitting in a drawer for a long time now. I went back to iPad Pro with Apple Pen as it's much easier to navigate around and I enjoy the color screen much more. It also allows me to use Miro or similar whiteboard tool. I personally regret buying it. The lag is more noticeable on an iPad, but that doesn't bother me.

Wow, 2 major things introduced over 8 years and 4 different state management libraries and people complain it's too much?

Do they pay anything to the maintainers of the packages they depend on?

I don't think that's possible since types are not present at the runtime. They are just stripped away during compilation

The methane has lower cumulative impact and is a closed loop where it gets recycled over time. [1]

[1] https://onezero.medium.com/cow-farts-are-not-the-problem-f57...

It's true that methane has a much greater impact, but only in the short term. Long term, CO2 is much more dangerous. The methane that cow produces is recycled as it circulates through the atmosphere -> plants -> cows -> atmosphere cycle. Fossil fuel burning on the other hand is not. It's released from the ground and there's no way for it to get back there. Nothing is ever black and white and to think that eliminating the animals as the food source would solve the problem is naive.

https://onezero.medium.com/cow-farts-are-not-the-problem-f57...

https://youtu.be/vpTHi7O66pI

https://medium.com/@caroline.stocks/debunking-the-methane-my...

I really like Firefox, but I had to switch back to Chrome because of resource usage. After using it for some time it got up to 3GB RAM consumption for a single tab with no plugins.

In my opinion, this is the point at which FaaS becomes viable

I think the more common term is distributed ball of mud

I strongly dislike that his words are always distorted by taking out of context this small segment of what he said.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%. A good programmer will not be lulled into complacency by such reasoning, he will be wise to look carefully at the critical code; but only after that code has been identified. It is often a mistake to make a priori judgments about what parts of a program are really critical, since the universal experience of programmers who have been using measurement tools has been that their intuitive guesses fail." - Donald Knuth

Mostly experience

You can mess up async/await in C# in exactly 0 ways. Calling .Result is just a bad practice and should never be done.

People can't even align divs properly. I would say AGI is further away than most people think.

Why is nuclear power a problem? It's one of the cleanest energy sources currently.

The report states with high confidence that balanced diets featuring plant-based, and sustainably-produced animal-sourced, food “present major opportunities for adaptation and mitigation while generating significant co-benefits in terms of human health”.

I think this says it all. The consumption is not as much of a problem as production. They don't mention how much forest is also cut to build farms and it's not like plant growing industry is any better in terms of emissions [1] and water / land poisoning with pesticides and GMO plants. Now, don't get me wrong, I have nothing against GMO that is done well, but the current direction that's only serving corporate greed instead of bettering farming industry is just disgusting. Without animals we are just as equally doomed as we are with them [2]. I also have a feeling that they're trying to optimize the 1% instead of tackling real problems caused by coal energy, cars, airplanes etc.

[1] https://agreenerworld.org/a-greener-world/it-wasnt-the-cows-...

[2] https://youtu.be/vpTHi7O66pI

They also own 21st Century Fox

The correct number is actually 100% (or close to it). It just depends how many generations back the family immigrated.

Why does it break the first rule of agile software development?

"That is, while there is value in the items on the right, we value the items on the left more."

I would say

- The ABI is not stable yet

- The compiler is not the fastest

- Doesn't work on all architectures (compared to C in the embedded space)

While those are potential downsides, they don't have to be. It all depends on what you're using it for and the language you're coming from. I would ignore the "learning curve" comments as they're (in my opinion) irrelevant. You learn it once and then reap the benefit for the rest of your career so a couple of months of investment doesn't sound that bad.

I'll name the rabbit - Peko

Sounds like a nightmare to me. Something that could've been a module in a regular application is split across multiple services introducing multiple network calls that can fail (not to mention the response time once the workflow grows). If people who don't know how to write modular code start using microservices as a solution, the only thing that changes is that you end up with distributed big ball of mud instead of the regular big ball of mud.

It was implemented 9 years ago but it could be argued that it was invented in the 1970s

https://youtu.be/eEBOvqMfPoI?t=859

It's part of the Blub Paradox[1]. If you don't know about better things, you won't miss them. But once you do know about more powerful things, it's hard to go back to living without them.

[1] http://paulgraham.com/avg.html

I feel like The Blub Paradox should be the mandatory read here http://www.paulgraham.com/avg.html

It's not a common denominator. If I need a Customer aggregate or a Payment aggregate it doesn't matter if I get it from SQL or Document database as long as I get that aggregate. My code doesn't care about query implementation.

Why wouldn't you be able to take advantage of those systems? I think it's quite the opposite where you can take the advantages without even knowing about it / affecting other parts of the system.