3 ms·
"The hard part of software engineering was never writing the code." Again, are we still on this ridiculous concept. I stopped reading at that sentence. Is tha
by wewewedxfgdf 2mo ago
"The hard part of software engineering was never writing the code."
Again, are we still on this ridiculous concept. I stopped reading at that sentence.
Is that going to be the revisionist future that the industry tells itself - ""one day, LLMs came along and suddenly computers could program themselves, and it was an absolute revolution, but it made no difference at all to anything because "The hard part of software engineering was never writing the code." so people stopped using LLMs because of that. And that's how LLM's came to an end after being a short trend.""
- fellowniusmonk 2mo agoThe hard part was the rote memorization of leetcode challenges and then learning to pattern match to the particular problem in a 5 minute technical interview. The second part was that the test was being administered by a gatekeeper who was hired before those practices were put in place. The 3rd was what? Amazon or Netflix burning your ass out because they are anti-human companies?
- satvikpendem 2mo agoA great article yesterday about this very concept: https://news.ycombinator.com/item?id=49222189 https://news.ycombinator.com/item?id=49222189
- preg_match 2mo agoI think it's true. Writing code is the most fun part of my job, but it's also the least time consuming. For any given feature, everything around the code takes 10x as much time. Getting the requirements, writing the spec, refining the spec, doing the QA work, delivery. The actual "coding" part in the middle is quick, fun, and creative. Since it's quick I get to sit and think about abstractions and performance, which is great. But, it could be even quicker if I just give up and willingly write shitty code that works. I don't do that, but I could, and I doubt anyone outside of close developers on my team would ever notice.