357 karma · joined November 23, 2019
Edit: Also, does the app check for the sudden deceleration spike when it hits the ground so you can't, say, add some kind of parachute?
I don't think any project specifically made potential employers say 'wow, we definitely have to hire this guy', but I think having actual experience doing stuff and demonstrating an interest for the field goes a long way towards landing you those first couple of jobs.
It definitely did that to me. I remember trying out Rust and was amazed at how much abuse I'd put up with from C++ for all these years. Now I just want to try out Rust in a large enterprise project to see if it will just be replaced with a different kind of abuse...
Software engineering exists in a sort of gray area where you can often be a professional software engineer without having to be a member of any order, which is great in many ways. But I feel like one could argue that the informal expectation of software engineers to care about software outside of their work is similar to what is expected in other professions with more rigid governing bodies.
But anyways, that's not really my point: My point is just that in professions it's not uncommon to be expected to perform some kind of extracurricular activities related to your job. Often software "engineers" aren't members of a professional order, but I'd argue that the idea still applies. Tbh learning by working on a hobby project is way more appealing to me than watching some PowerPoint presentation...
And of course to our ancestors, we're spoiled kids with our electronically erasable ROM ;)
Timing the refresh just right and grabbing a super valuable chocolate was quite a thrill, probably even more than the games themselves.
The future is gonna be weird, yo.
Sometimes one particular game (MechWarrior 2: Mercenaries) would freeze and the CD drive would start spinning at warp speed, and it would still be spinning a bit due to inertia when I opened the CD tray. Once I tried to stop it with my finger and the disc launched itself across the room.
You just don't get these kinds of hijinks with modern games :(
In C++ you can really (ab)use it to do things like scoped mutex locks and "stopwatches" that start a timer on construction and print the elapsed time on destruction.
Some people find it a bit bizarre though, to each his/her own I guess.
What happens when they leave it for a few months and come back and forget how everything works?
When a client encounters an issue in the field and they have to debug it with "It doesn't work, yo." as a problem description?
When a coworker tries to modify it and breaks everything because they can't figure out how it works and there are no decent tests?
Eventually, they'll come around :) Or maybe there is no saving some people and they should stick to R&D...
I agree that embedded is a good choice if you're looking for C.
The thing people might not realize is that when you're exerting yourself, your body generates plenty of heat to keep you warm - it's really just a matter of keeping that heat contained. It's more akin to doing a winter sport like skiing, snowboarding, etc. than it is to sitting passively in a car.
I actually got a small pay increase compared to my previous role! I don't think my salary really compares to what I read about on here (like, I think your average HNer easily makes 2x what I did/do based on the posts I've read) though, so take from that what you will.
- The space evolves at a slower pace than regular "software", so I'm less stressed about keeping up with the latest/greatest;
- Resources are more constrained so there are less whacky design patterns and architecture - just simple code;
- Longer development lifecycle (due to hardware), so less being rushed to ship half-assed features.
There are downsides, too:
- Less cool algorithms (and language features), more shunting around data and debugging;
- Not as well-compensated, but still pretty good;
- Hard to be 100% remote, since you often need access to hardware.
Obviously, my experience is not universal, just my sample of n=1!