485 karma · joined April 8, 2015
Because it's the only way to get a job in industry.
I find it repugnant that theoretical scientists feel entitled to some of my income.
you think it's bleak that one's research now has to be profitable rather than being subsidized by people paying taxes?
Switzerland is about half the size of Maine. Not everything is about your perceived failings of American culture.
Does that include the lie that the story was "Russian propaganda"?
Right. Did everyone forget about the twitter files already?
IMO it applies to all languages. Fancy language features usually make for poor maintainability, e.g. metaprogramming.
According to this site[0], new car prices were about 6% higher at the end of NAFTA in 2020 compared with at the start of NAFTA in 1994. Considering inflation on other things was on average much higher and also that more recent cars are significantly safer, more performant, and fuel-efficient—i.e. more provide more value—it does look like cars did effectively get cheaper.
That is definitely not what software engineering is. It requires translating requirements and ensuring that the code is maintainable in the context of a team and the product's lifecycle.
are you trying to collect ad revenue from the actual users? otherwise a chatbot reading your page because it found it by searching google and then relaying the info, with a link, to the user who asked for it seems reasonable
Not once in my 11 year career. But almost every codebase I've worked on has had debilitating maintainability issues because the only principle other engineers seemed to follow was DRY, at the sacrifice of every principle in SOLID.
What are you doing about it?
As far as social media goes, just don't follow accounts that are annoying. If some accounts are friends in real life but insufferable online, just mute them. Other than friends I follow accounts about food and pottery, I don't see any reason to get off social media, I love it.
How do you define "enough" and what would be a case where it wouldn't be enough?
> “Don’t Repeat Yourself” (DRY) is basically good advice, but sometimes just copy/pasting things is just the more pragmatic thing to do, and not really a big deal.
Duplicating code on purpose is not about being pragmatic, it's about recognizing when DRY would violate the single responsibility principle.
The ability to weigh tradeoffs in context is what makes some engineers better than others.