whstl

31 ms·

811.
by whstl 1y ago
Quoting myself from another post: A lot of people in this industry have near-zero operations knowledge that doesn't involve AWS, and it's frightening. They also have near-zero knowledge on the history of the field.
812.
by whstl 1y ago
It is worth saying that AWS educates people to behave like this. In the last "mandatory education program" I participated, the AWS instructor laughed at the possibility of data loss.
813.
by whstl 1y ago
You know the quote: It is difficult to get a man to understand something, when his salary depends on his not understanding it . A lot of people in this industry have near-zero operations knowledge that doesn't involve AWS, and it&#x27
814.
by whstl 1y ago
Yes, I agree. Good point. A fizz buzz or something similar is often already too much for these.
815.
by whstl 1y ago
Also: as someone who interviews and handles hiring, the biggest bottleneck for me is my time. In enterprise sure, I had whole weeks where not much was going on, but in tech or in startups? An hour is already precious.
816.
by whstl 1y ago
Yep. The crazy one for me was QA not going through business and just marking new feature ideas as "bugs", and then informing business that "there are still lots of bugs to be fixed". Cross-functional teams can be very to
817.
by whstl 1y ago
I don’t disagree, but in those interviews the explanation is also a bit of a q&a, so an effective interviewer can detect candidates who only memorized things. Someone who can ace a q&a about Linux code is already better than average
818.
by whstl 1y ago
I agree. Live coding always has a much smaller scope than real software, and after a few interviews it is easy to learn to read the room, even for the worst developers. I think we can leave companies who don't care about quality out of
819.
by whstl 1y ago
Well, yes, but "self-managing team" implies the team manages itself, not that one person picks up the slack. As the sibling poster said, this is a sign of a dysfunctional team.
820.
by whstl 1y ago
It is indeed.
821.
by whstl 1y ago
Off topic, but: It's interesting how everyone thinks they're "managers" in "agile" teams. Scrum Masters, Product Owners. I've even had Designers and QAs trying to make decisions on behalf of the team.
822.
by whstl 1y ago
I agree with you and upvoted you but: IMO the problem from a management perspective isn't really the bad performer staying too long. Also, dealing with HR as a manager is mostly fine. They actually respect you. And just having someone
823.
by whstl 1y ago
Same way as before? I had school teachers routinely teach me wrong stuff. The only way is comparing notes, talking to peers and parents. For example: as a kid, a specific science teacher didn’t knew that seasons are different between hemisp
824.
by whstl 1y ago
Bingo. In a nutshell: parasocial relationships doing psychological and financial damage; anonymous inflammatory content doing social damage. And that’s without putting things like dating apps, advertisements and privacy violations in the m
825.
by whstl 1y ago
I have never seen this as the justification for using a framework. As a rationalization, sure, but never as the reason. They do offer more than coding standards.
826.
by whstl 1y ago
This study was about “246 tasks in mature projects”. I would expect AI to fare much better in a study about new projects or brainstorming.
827.
by whstl 1y ago
Answering because I know the answer, even though I disagree: There are some situations where having some animation can "attract attention" to parts of the UI, for guidance ("there's some info text here"), feedback (
828.
by whstl 1y ago
Or maybe we should give the author the benefit of the doubt and assume he's unhappy with both radical ends of the spectrum, which would be a refreshing take in 2025 to be honest. I don't really agree with the general argument, tho
829.
by whstl 1y ago
Yeah, that's a great argument. Not only it's harming people of average capability, it's also not even benefiting the people on the bottom. The Overton-window of supply-chain has shifted so much to one side that it no longer b
830.
by whstl 1y ago
I wish we could have this discussion without going into exaggerated extremes like "Linux". The OS rarely gets into discussions of rewriting dependencies. I recently had to rewrite a table component and it took about an hour with e
831.
by whstl 1y ago
I am not saying it doesn’t exist, just that I have been around the block for quite a while but even then didn’t personally work in a place like this. Places with average developers are more than equipped to do tasks that HN claims to be imp
832.
by whstl 1y ago
Average doesn't mean rock bottom. I've seen "Meh" do the things HN claims nobody can. Plenty of times.
833.
by whstl 1y ago
Good point. It was Software Engineering, but I still expected to see more foundational classes there :( And I'm totally ok with the React part, I just dislike the fact that React was the only real "meat" in the course.
834.
by whstl 1y ago
The problem I have with this line of thinking is that it only works when you're talking about bottom of the barrel developers. The tech world has this tendency to dumb down every advice so it caters to the lowest common denominator, bu
835.
by whstl 1y ago
This is gonna sound like an old man yell at clouds post but... I also remember university being great. I built a compiler, a toy OS and interfaced with GPS. But a few years ago I was invited to teach on another university and I was very dis
836.
by whstl 1y ago
Yep, that's a great point. Fixing this would probably require some changes at the language level, or at the module-loader level for some languages that use one.
837.
by whstl 1y ago
As the sibling poster said, you probably misunderstood my point. I'm talking about how monoliths can also fix such problems when they happen.
838.
by whstl 1y ago
Different sections of an app can use different databases, if the bottleneck is in the database. Different routes can be served by different servers, if the bottleneck is in CPU usage. Different async tasks can run on different task runner s
839.
by whstl 1y ago
I have found that too much coupling between product requirements and the architecture can be detrimental. It's often the reason why people tend do too much upfront work, but also slows down the evolution of the feature. So I don't
840.
by whstl 1y ago
I actually try to build it "well" in the first pass, even for prototyping. I'm not gonna say I succeed but at least I try. This doesn't mean writing tests for everything, and sometimes it means not writing tests at all,

More ›