Markdown is phenomenal. It gives end users simple and easy to remember ways to perform the most common formatting operations but leaves the text in a state that it was be parsed by humans without an actual markdown renderer.
200 karma · joined October 27, 2019
https://jaylittle.com
Markdown is phenomenal. It gives end users simple and easy to remember ways to perform the most common formatting operations but leaves the text in a state that it was be parsed by humans without an actual markdown renderer.
/shrug
I liking having my own space where I can say what I want. There is also real value in me going back and reading what I said a year, five years or even ten years back. My blog posts have proven to be a useful way of reminding future Jay of what past Jay was going through as I have a tendency to look at the past through rose tinted glasses.
This morning's blog post is no different, though more self-deprecating than most of the things I have written.
https://jaylittle.com/post/view/2023/7/i-am-on-the-mcnulty-s...
I dare to dream of a world where I can reread that years later and say, "It's okay past Jay - it's all going to work out for the best, just stay the course"
My current gig is basically the first one. Nobody has the big picture. Nobody wants to discuss the big picture. They are only interested in checking off the boxes associated with the task they currently have assigned. Everything is due yesterday because there is no actual priority list and our priorities shift on a daily basis. It's utter chaos.
We are writing an ERP system. It is slowly shaping up to be a complete disaster. I have spent the last eight months trying to change this approach and attempting to lead by example.
It's not working. I will be moving on soon.
TLDR: Just because somebody can afford to hire a software engineer, doesn't mean they should hire a software engineer.
If I couldn't get a truly repairable phone, then at least I could buy the one that would likely last the longest given the wide availability of official repair outlets (e.g. Apple Stores) and the history of solid software support for at least five years.
So that's where I am at. Thankfully things are looking a bit better on the laptop side of the repairability fence. I have every intention of pre-ordering a Framework 16 the second pre-orders open.
Edit: All gone, thanks for playing!
Screw you IBM... and the creepy Linux kids coattails that ya rode in on.
I apologize for the implication, it was not on purpose.
I was sorry to learn that this feature request hasn't seen much traction. However @ksec gave me an idea by linking me to an earlier thread on this very same topic in which somebody suggested that we just create a patch for the existing news.css file.
Not sure why this thread got flagged, but I took it upon myself to create a patch for the existing news.css file as well as producing a new news.css file with dark mode support:
Patch: https://pastebin.com/Gwq5WSwX
Full File Pre-Patched: https://pastebin.com/Nd7JDLLT
Again, all thoughts and criticisms of this work will be welcomed.
Please help those of us with a dark mode preference enjoy this website more by implementing these changes (after a proper code review of course, as I would expect nothing less from fellow hackers)
I'm going to work on implementing the CSS changes when I get bored. If that's the only thing standing between a bunch of hackers and dark mode on the hacker news website, I'm going to be very disappointed ;)
Goddamit MS.
The moral of the story: Your workflow is not sacred. Even the way your brain "works" is not sacred. Learn to adapt or be prepared to die. If your workflow isn't changing or at least being tweaked from time to time, the odds favor the idea that you have grown stagnant. That's not to say that change for the sake of change is the preferred alternative however. I'm only saying that treating your workflow as sacred and hence immutable is a dangerous trap to fall into.
What a crock of shit.
So long Firefox and thanks for all the fish!
Regarding the 502s: I was attempting to enable IPV6 and HTTP/2 for my website per a request I received from a fellow nerd over email. After two hours of pulling my hair out over intermittent non-availability, I just reverted back to my good ole trusty IPV4 non-HTTP/2 config and all is well again. Except for that guy. Sorry dude, maybe some other time.
Anyway, I would encourage everybody to read all three parts. Barring that, just read part 2 as it covers what my anonymous in-the-know source shared with me and my attempts to verify their claims with publicly available information. That's the real meat of the piece (at least it should be as I spent hours researching and cross checking data for it).
Thanks again for the support!
Well the answer to that question turns out to be: I just spent the last few hours of my life dealing with intermittent website availability issues on nginx after attempting to configure ipv6. I have now reverted everything and we are back online.
Sorry :(