Junior developers have always been a lot less effective than senior developers. We will need new senior developers so we will need to train junior developers. Maybe we train them by forcing them to do things the hard way. The slow way. By hand. Because if we let them do things the fast way they are going to cause some serious damage.
Employers were already refusing to hire juniors, even when 0.5-1 years' salary for a junior would be cheaper than spending the same on hiring a senior.
They'll never accept intentionally "slower" development for the greater good.
my last summer intern did everything the manual way, except for a chunk where I wanted him to get something done fast without having to learn all the underlying chunks
My team was doing this until recently but I think in February, Anthropic made team accounts available for subscription instead of API billing. Assuming that is the cost you mentioned.
Exactly.... -> Unit tests. Integration tests. UI tests. This is how code should be verified no matter the author. Just today I told my team we should not be reading every line of LLM code. Understand the pattern. Read the interesting / complex parts. Read the tests.
But unit and integration tests generally only catch the things you can think of. That leaves a lot of unexplored space in which things can go wrong.
Separately, but related - if you offload writing of the tests and writing of the code, how does anybody know what they have other than green tests and coverage numbers?
I have been seeing this problem building over the last year. LLM generated logic being tested by massive LLM generated tests.
Everyone just goes overboard with the tests since you can easily just tell the LLM to expand on the suite. So you end up with a massive test suite that looks very thorough and is less likely to be scrutinized.
I’m not sure if these fires are correlated with the staff reductions in BLM. In the interview with a resident she doesn’t mention anything about that, just that last year was very wet which provided a lot of fuel and this hot dry spring has turned it into a tinder box.
BLM provides fire lookout services that were severely cut. They also perform prescribed burns, which they no longer have staff and budget for, which would have reduced the dry grass.
And "However, the two variables would be correlated if the causal arrow were reversed" is missing "also", almost suggesting that the article gets it wrong and the two variables are not correlated because of the placement of the causal arrow...
Since we are apparently giving messaging platform reviews here, I feel exactly the same way about Microsoft Teams. It works great. It does everything I want. It doesn’t get in my way. 10 out of 10 keep up the great work guys!
> Since we are apparently giving messaging platform reviews here, I feel exactly the same way about Microsoft Teams. It works great. It does everything I want. It doesn’t get in my way. 10 out of 10 keep up the great work guys!
It looks like we found a high executive using company money to buy a product no one wants to use.
It's easy to promote Teams if your secretary is handling it for you and you don't need to suffer yourself.
The other possibility: Microsoft started an astroturfing campaign on HN.
Teams network connectivity is a plain joke. If you use suspend, or frequently change network, the thing will just never reconnect, even though you have VPN alive and all network applications perfectly running.
And the thing is just absurbdly sluggish, only display blurred grey lines instead of text in a meager attempt to look snappy.
I only use Teams for meetings and the calendar, and the occasional chat during a meeting. I find it totally fine and I don't really think about it much one way or the other. For reference I have a 2021 M1 Max with 64 GB.
Probably all managers and engineers working on Teams have similar copious amounts of memory and powerful CPUs on their devices and hardly use their own product. That would explain a lot
It honestly wasn't much different on my 2018 i5 Mini with 32 GB.
Maybe what sucks here is the experience of running it on Windows. Or maybe it sucks for large meetings? But I never have Teams meetings with > 40 people at this company.
When it is online, I agree with things asides from the "fast" part, actually. But many companies have a secondary service for async comms/chat when being Teams cannot be online, and compared to Slack.
Honestly can't tell if this is not sarcasm/rage bait.
Teams that has 3 different UI frameworks on every platform (but your best bet is the web)? With the Microsoft login that tends to loop forever redirecting to God knows where?
reply