HN user

DogLover_

291 karma
Posts0
Comments96
View on HN
No posts found.

I think people are coping. Software engineering has only gotten easier over time. Fifteen years ago, knowing how to code made you seem like a wizard, and learning was tough - you had to read books, truly understand them, and apply what you learned. Then came the web and YouTube, which simplified things a lot. Now with LLMs, people with zero experience can build applications. Even I find myself mostly prompting when working on projects.

Carmack’s tweet feels out of touch. He says we should focus only on business value, not engineering. But what made software engineering great was that nerds could dive deep into technical challenges while delivering business value. That balance is eroding - now, only the business side seems to matter.

Thats fair! I just don't agree with the readable part and thinking. I personally get tired having to look at all the archaic boilerplate to find the actual logic that I want to reason about.

I have to agree with author. I don't see what people like about golang. It seems like people use it because it is cool but after a while people realize they are less productive with it.

I am still perplexed that people accept the UX of Discord. It is just so horrible that I can not get myself to use it even if I am looking for a place to engage with communities. There are way too many channels which you cannot opt out of.

That is your workflow. Many places have replaced email with Slack. For DMs people might not care how good the message is but for public channels where there are many recipients I am sure people care about the quality of their message. The fact that it might be more beneficial in an email client I don't think is relevant for Slack as a company.

That has always been the case. That is why I also believe coding will be forever changed with these models. We won't be copy/pasting into a chat-interface but this will be integrated everywhere making it a completely different way of working.

I always thought one of the drawbacks of working in america compared to europe was that there was less of a safety net. However, with all these news about layoffs I see that most tech companies provide a severance package of 16 weeks which is better than most companies in europe. Is something changing or have I been wrong in my assumptions?

The problem with backup codes is that many people don't understand how crucial they are if they loose their device. Even IT people. I believe it is a step many skips because they falsely believe they can get access in some other way if necessary.

That it has become standard makes me think the inventors/providers have not thought it through.

I may not be using the term feminism accurately, but what I mean is that men were told that any progress made for women would also be beneficial for them. While I fully support gender equality and fairness, it doesn't seem like these advancements have actually helped men. It appears to be a zero-sum scenario.

I don't think the codebases I have worked on can be considered large as such. However, to me, they were actually easier to change/refactor. There was less boilerplate, and more concrete implementation than what I see in static language projects. I usually have a harder time working with static languages because of so much boilerplate they usually have. I seem to be in a minority though.

I think you would be surprised how PRs work in many companies. We are encouraged to write small PRs and many will have automated tools that points to a Jira ticket in the description or as a comment. For this reason many leave empty descriptions. In such cases this would still help.