Markdown needs to stay human readable and "simple." Yes, I like some of the bolt on capabilities but I also want a document format that can be read using the simplest interfaces like text editors and os utilities like cat. That's THE reason it is our standard for documentation. I can make it pretty with a nice renderer but also read it, version it, consume it in a ton of tools (like AI Agents) using simple tools.
My advice: Start your own cybersecurity company. No one will hire you for any IT position. So you need to create your own. A niche that isn't being addressed is cybersecurity offerings targeted to small nonprofits. You'd make a killing.
As a tech person, I am treated like a machine, one that should be in a closet -- not seen or heard, they just want work output and they don't want my opinion about whether what they propose is a good idea or bad one (spoiler, most of them are astoundingly bad since non-tech managers are usually as dumb as a box of rocks). I hate my job and increasingly my whole life. It would be great to work for people who know the value of what you do, and the tremendous effort required to do things right, and to just ask the question asked here (with an obvious interest in a real answer and a compassionate ear to hear it).
I agree with gcatalfamo, while infinite scrolling websites seem like, "hey that's cool, I want to be with the in design crowd" they are actually pretty heinous for all the reasons mentioned above. I want a scroll bar that reflects were I actually stand with info contained on the page, not the content that is currently on that page. Refreshs and navigation don't bring you back to where you were. I just think they are obnoxious. I'd rather page through results and be able to predictably get the results from those operations that I expect. Just say NO to infinite scroll!
This was a great article. I've spent the last year filling in gaps in my own CS background including CL, Scheme, Racket, CISP, HtDP, etc. This is the first time I've seen good solid reasoning about Scheme using Assembly and it makes things really clear. I wish the author would have taken a little more time reasoning to the correctness of recursion using the y combinator. That's what he ended up with but it would have been helpful to break that down a bit more. Also, he mentioned that his next article in that series would have covered continuations (specifically call-with-current-continuation) and I REALLY would have enjoyed that since I find continuations a little hard to grasp.
I'd make my resignation letter quite minimal. It will likely go in a file that will outlast the context of your time at the company and reason for leaving. Thus whatever you say there will have an increasing chance of coming back to bite you later.
Your exit interview may or may not become part of your permanent record but you can convey better context in the interview. I'd still be careful to think about how your statements would be viewed in 1 to 5 years after they are given.
I think it's better to err on the side of discretion.
Risk has its rewards.... but also its disasters, which is why it's called "risk." Before taking it you have to consider the cost of failure. If you can't afford the failure, don't take the risk. That being said, you're in a tough place and hopefully zedshaw actually has a list and not a bunch of hot air. I'd take him up on it and get something to provide income. BTW, while failing seems to be harder on us men, failing doesn't mean your not a man, but failing to take responsibility does speak to your manhood. So get up and get going.