Supercool, thanks for sharing. I geeked out over the video and its production quality too. That top speed is pretty insane but I suppose it does have a 3 minute flight time. How long before we see this technology popping up in military use? Isn't Anduril or Shield AI doing something like this?
In the case that this was not a poor joke, please do consider calling 988 if in the US or any equivalent service in your locality: https://988lifeline.org
There is more to life than work - and it may be hard to see that in the face of cost and running out of money.
Have you considered any adjacent or post-software gigs? I know some folks who have left to go study a particular science or end up in teaching. A good friend of mine left engineering to become a substitute and then full-time teacher.
For those looking for additional data and more comprehensive coverage on the topic I would point you to Our World In Data's entry on outdoor air pollution.
Pretty fun read. PNR / reservation / confirmation numbers are a pretty interesting method for allowing quick changes. Obviously sharing them is ill-advised. However, how is the general, non-technical layperson supposed to know any better?
I've been doing this ever since I discovered my OnePlus 5T years ago generated a QR code to share WiFi details.
It's more of a cool factor with friends but still pretty convenient. Folks in my age group almost intuitively know how to point a camera / get the results.
When I left high school for college (to pursue engineering) I was quite envious of my friends in the liberal arts - they were assigned papers all the time and I had no outlet for writing (something I enjoyed quite a bit).
I have realized that written/technical communication is a great differentiator.
I journal every day but specifically to your question I would say just start writing.
Knowing your audience is key. I usually include an executive summary section at the top of any design document or product requirements document for a high level view of why people should care. Then I dive into a background or history to give context. At the end of the day it's a narrative and follows similar arcs - just with more direct prose and specific facts. I'll also drop this resource here from the Pragmatic Engineer newsletter. [0]
I lived not far from here when I was in Detroit. Honestly this guy is lucky not to be seriously injured.
The highway, M-10 or the Lodge Freeway, in my opinion should be converted to a boulevard that supports multimodal transit. This freeway cut off my neighborhood from the more vibrant (as it can get for Detroit) downtown and midtown neighborhoods.
I was listening to Dan Snow's History Hit podcast [0] where there was a guest episode on oligarchs & oligarchy in general. They mentioned Caesar because he was also an oligarch, like most of the other generals/Senators of Rome. Jeff Winters also wrote a book on this topic [1].
Caesar threatened the oligarchs of Rome by crossing the Rubicon with his legions which was heavily frowned upon by the others. Caesar threatened their power structure for sure and likely led to his death.
Prof Grizzle is very much about practical learning and has a pretty good sense of humor too.
When I did undergrad at Michigan, I got the sense he was one of those exceptional profs who knows what they're doing + truly cares about the non-academics.
There are a couple assumptions you're making here. For instance the firing (from your perspective likely but will they really?). Take a step back and take stock of the situation.
Communicate with your manager. Your manager not being there in that meeting definitely didn't do you any favors. Make sure the both of your are on the same page. They should have been there to deflect. Be proactive about communicating and making sure everyone is in alignment. Easier said than done especially if the company is smaller or the manager is busy. But a 20 minute time investment per week will be worth it.
Figure out why this happened. Figure out what can be fixed and move on. But be vigilant because that kind of behavior is frankly uncalled for. On the other hand getting a new job in this market should not be too hard.
"In Minnesota, the emphasis is on working hard at whatever you do, and living a good life."
Having done my undergrad at the University of Michigan and spent a year and half in Detroit afterwards, I relate a lot to this article. People are just nicer and more personable here, there is less arrogance and an attitude of "doing the work".
While your point that you don't need an iPhone has merit, one can't simply relegate themselves to text messages on a flip phone.
Far too much of the modern world including our societal systems require a smartphone. Wether its a QR code showing COVID vax status, checking email, engaging with your local bank via the app, connecting with friends, etc.
We have built a world that is so reliant on the apps ecosystem (at least in the US) so it's unhelpful to say "flip phone can get text messages".
My org (250-500 employees -- most in manufacturing) has 5 AWS accounts.
We have dev/staging/prod and then a master account used for organization management & consolidated billing. Just stood one up today for another department too.
I implemented SSO recently and am exploring the idea of giving each developer (we have a small team) their own lab account to standup whatever they need. Right now we have folks sometimes overwriting work in the dev account.
When I joined we had 3 accounts (staging/prod/payer) but slowly as we build real DevOps process its sorting itself out.
The rational for having different accounts across different departments - it helps with billing and ensuring the correct department pays for their share of AWS usage. Also better access control with Single Sign On & added benefit of reducing spillover effects from improper access/actions.