HN is not a hive mind. There are people here who love Firefox, people who despite it, and everyone in between. It’s tiring to always be reading your type of comment, as if everyone is a hypocrite. Maybe, just maybe, the people making those contradictory comments are not the same individuals.
And it’s not like Mozilla is free from controversies, including several of betraying user trust. If every major browser maker is going to break your trust and sell your data, I can see why people choose their poison based on other factors.
I use neither Firefox nor Chrome. Is Safari any better? Or Brave? In some areas yes, in others no. I don’t think there’s a single browser vendor which gets it unambiguously right.
I didn't mean to say that all of HN despises Firefox, but simply that it very often brings negative sentiments, so seeing the comment I was responding to so high up in the thread made me react. It was also a kind reminder that militating is as simple as using an alternative to Chrome.
> And it’s not like Mozilla is free from controversies, including several of betraying user trust. If every major browser maker is going to break your trust and sell your data, I can see why people choose their poison based on other factors. > I use neither Firefox nor Chrome. Is Safari any better? Or Brave? In some areas yes, in others no. I don’t think there’s a single browser vendor which gets it unambiguously right.
And you're making my point about the perfect solution fallacy as well! Of course Firefox isn't perfect and has screwed up on several occasions, does that mean it's comparable to a piece of software that sends every single bit of information it can gather to its parent ad company?
It's almost as if Steve Ballmer and the legendary "developers developers developers" speech still rings true today - the key to getting people to use your software is to make life as easy for the power users as possible, let them spread the word. And it's ironic how Microsoft lost its ways there... a lot of people I know have gone from Windows to Mac and convinced their close relationships (aka those whose computers they fix) to do the same. It's just so much more relaxing to boot into an OS that doesn't try to shove advertising down your throat at every turn.
My point exactly! You're talking about which browser to use for web development. That's not relevant for engineers not touching html/js/css, and for all non tech savvy family members whose computers we set up.
IMO we need to start normalizing being militant about this stuff again, to aggressively and adversarially defend the freedom to use your computer the way you choose to use it
I'm dubious about people becoming militant about this when the software engineering industry gave Chrome a red carpet by using it and installing it on their relatives' computers while knowing very well it's adware and when switching to the alternative is incredibly cheap.
- we salvaged 100s of discarded e-bike batteries
- we found that 90% of components were like new
- batteries were thrown away because of the spot-welding and the glue which prevents repairability
- we spent 2 years (and 5 patents) to design a robust, safe, and easy to assemble system that requires nothing but a screwdriver
Our batteries have been in use since 2 years in the streets of France, on micro-mobility e-bikes, in the harshest possible conditions (rain, snow, cold, heat, shocks), and we're very happy with their performances!
We're now opening it to the general public (for conversion kits, and to replace old batteries that are no longer manufactured)
We plan to open-source at least part of the embedded software, so people can write extensions (to let their battery "talk" with any e-bike system, and share it — using WASM embeddable code — to other people on the web!)
Let's fight planned obsolescence!
(and if you're looking for a new battery, there's 25% off on https://get.gouach.com)
I own a Specialized Vado SL from 2022. Can I use your battery as a range extender?
You can continue to be a software engineer all the way to a normal-age retirement. (I'm in the US, though - I don't know about France.) But you can't be the same software engineer for the whole time.
Your code should be better designed and architected than it was 10 years ago. You shouldn't write the same bugs you did 10 years ago. You should document your code better than you did 10 years ago.
Every five years or so, you should ask yourself what you need to learn now for the next few years of your career - and then learn it. (Hat tip to my wife.) One of the coolest things about software is that you can often get paid for learning that - you can find a project at your current company that will grow you in the direction you want.
What you cannot do is continue to be a better paid version of a junior programmer. You need to be more valuable than the new people. (This is why you don't need to worry about the "growing pool of software engineers" - it's growing largely by adding new people with no experience. They can't replace you, because they don't have your experience.)
I like the personal five-year plan idea. It will help setting clear expectations and action plans. Thank you!
You're barely half way through your "commoditized workforce" lifecycle. Start doing things for yourself at any time.
Say a sentence to yourself that you want to be true. "I have made a vision detection solution for classifying cats." "I have created infographic heat maps of political manuer." "I have created a web game." And do that on the side until it is true. If you liked it as much as you thought you would, angle for that. It will at least give you something peppy for the interviews.
Otherwise, keep turning the lathe and hope abstract economic stabilities continue to grease your wheels of life.
There are several side projects I started, halted, came back to, etc. over the years, and I love them but none of them could actually pay the bills. I also struggle to be consistently productive when I'm not part of a team.
At the moment I have a good contract.
Ageism definitely becomes a factor. One thing that is important is not to contribute to it. For example, part of your post implies that as you get older you will struggle to keep up with relevant technologies.
The real concern for every software engineer and actually every job is the powerful AI that we have to anticipate within the next 0-10 years.
OpenAIs newest model, although amazing, still has some weird brittleness to it, so it's not going to literally replace an actual software engineer easily. But it is a significant step closer than the day before yesterday. Probably at least 15-20% better, or a lot more depending on how you measure it.
I keep seeing people reacting to the current state of the art AI and saying that they are not concerned. This is incredibly short-sighted. The history of technology is hundreds of major innovations breaking through performance wall after performance wall.
There are not only upgrades but also new paradigms on the way for increasing AI performance, in the areas of hardware, ML model architecture, and software. And the reality is that with this latest OpenAI model and the right feedback loop and constrained platform/domain, we can actually automate quite a lot of software engineering work.
As AI is integrated better with systems, we will definitely need fewer people doing what currently is considered software engineering. And again, don't think about what the current model can do. Look at the trajectory of history over the last 60+ years of computing. Engineers always break through barriers and consistently increase performance by orders of magnitude.
This is not just a concern for software engineering but for every job. But it can be a huge improvement if society is able to adapt and take advantage of it in an equitable way.
I think the best option is to start leveraging AI and robotics to build out goods and services. Individuals without capital or very little capital can take advantage of AI and robotics to become entrepreneurs.
It's definitely a tool I use though, but as a centralised documentation. And I keep up with it to somewhat understand how it works under the hood. But even this does not answer the question of how to prepare should it actually help making most software engineering jobs obsolete.
Reddit is a good source of anecdotal information:
https://www.reddit.com/r/coolguides/comments/7fv5oj/beginner...
https://www.reddit.com/r/microdosing/
This is also good:
https://www.thecut.com/2018/05/microdosing-guide-and-explain...