61 karma · joined June 22, 2021
- Studying and researching best practices for not just your current language or paradigm, but others as well. If you've got experience with Java, look into other paradigms than OOP such as Haskell / Elm that focus on Functional Programming. This can lead to learning about new ideas of programming in general, which is a good thing as it exposes you to more tools that you can use.
- Making your own things. Find areas in your life that could use some automation, or perhaps use programming as a creative outlet; the more tools you make, the more practice and experience you'll get which leads to the first point I made.
- Cringe at your old code. If it's really that bad, it's likely you've come a long way as a developer, which is good! Reflect from time to time about why you originally wrote code a certain way, and think about how you would approach the same problem now with more experience.
Putting aside the physical aspects of replacing existing roads, how would a digitally-aware road work? A bunch of bluetooth devices? And in what schema would the road 'speak' to the car? Ideally it would be an open format, but who would decide upon that?
What keeps you using Ubuntu after all these years?
I wish the Qubes OS the best of luck in future, and let's see how the GPU passthrough team goes.
I've been playing crash since I was a kid, and I never thought about why you couldn't run backwards. What a brilliant solution.
However, in the case of 1Password it's not just about being a password manager; it's also about syncing passwords between devices, staying on top of (sometimes rapidly!) changing standards between devices and browser extensions, and being aware of the evolving landscape of best security practices.
Where am I going wrong?
It's a real shame, because this is some neat hardware I wouldn't mind splurging on.