2,119 karma · joined December 13, 2010
My main concern is that I don't want to weld too much of my design to any one service provider, so I've got to be careful about taking too much advantage of their feature set and API so that it won't be a pain if they go away or it becomes necessary to migrate to something else.
I feel like I'm supposed to impart some wisdom, so I guess I'd add.. once I got out of high school, none of it mattered. Don't let it get you down.
I've got a soft spot for it as well because I actually used it. At work. On a PC. In the 90s. My assignment was to figure out how to get data into it, for which I ended up writing a routine that operated on floating point numbers as vectors of 1s and 0s and swapped the bits around to convert from Microsoft to IEEE format. While wearing an onion on my belt, of course.
I have non-data-driven (but informed) opinions on how to pick up coding as a new skill. I think it helps to find a hobby space you're interested in that will motivate you to push through when you get stuck on something. There are some great platforms for live-tinkering with electronics, CircuitPython for example. Or web stuff, if there's a way to get into it in 2024 without being overwhelmed by frameworks and complexity.
I'm going through this now as I decided to spend some time today learning the Drizzle ORM. The first things I found were all "here are half a dozen examples of queries", and I started getting frustrated: why are you using that syntax and not something else? What are the other options? I closed those and I'm much happier doing it my way: reading every page of the documentation before doing anything else.
I have, however, wondered whether an expensive screwdriver is worth its price, but I have not collected the data to support my Wiha habit.
I'm hoping at some point someone will comment or message me to say they've built one. I just added the parts list and CAD models to https://github.com/masto/LED-Marquee/tree/main/hardware, and in the next video I'll explain how to build the software.
The first video is here: https://youtu.be/W0_3rzvq9Ks (the second is coming out tomorrow)
And it's on GitHub here: https://github.com/masto/LED-Marquee
I also recently left the Big Tech world after 11 years at Google, so I'm trying to figure out what comes next. (I don't think I can make professional YouTuber pay the bills). If it's not inappropriate to mention here, my resume is at https://hire.masto.me/
My OP-1 battery also needed replacement after sitting unused for a long time. Fortunately (not for my wallet) I was still able to get one at the time.
https://www.youtube.com/playlist?list=PLQvwVDViTLXu4usHto8PH...
I wonder what reversal of technological progress made it possible to run a web server on a tiny computer that only uses 2.5 watts of power, and how that "small, off-grid solar PV system" was built out of low-tech components.
https://looptube.io/?videoId=W5Z-d1Zx02o&start=77.1286764705...
These folks have a stellar reputation, and I'll be buying this app on that (and the I-was-expecting-more-digits price) alone, but I would have enjoyed seeing some kind of short film "shot on Kino". If only to see some professional work.
> Sure, you could push your glasses up your nose and say, “Well actually, no file is ever really deleted until it’s overwritten...” And while that is true, a reasonable customer would expect that when Apple says a deleted file is permanently deleted, this sort of thing shouldn’t even be possible.
You could stereotype it as well-actuallying, sure, but the reality is that "deleted files aren't actually deleted" has been the way computer storage has worked and still works, in the majority of cases, for a very, very long time. I don't disagree that a reasonable customer would expect that when they delete a file on their hard drive, it's gone forever. But if I were a writer for a tech publication, I don't think I could credibly write an article indignantly demanding an explanation for an undelete utility.
I am not in the finance department, but in software engineering and operations, two-party controls are everywhere. I can't check in code without reviews. I can't access production systems or make changes without approval from another team member. I would think that similar processes could be put into place for transferring tens of millions of dollars.
In other words, there are ways to deal with this that don't come down to "mistrust all technology and revert to face-to-face meetings and handing cash to each other".
We were not a board game family, apart from the occasional attempt to get through Monopoly without my little sister flinging it onto the floor. My partner, however is from board game people. When we're with her family, there are dice and cards and tokens, words and numbers fly through the air, and I am utterly lost. I played Scrabble with her once. I used to think I was smart.
To be fair, that's not unique to Jira, and I certainly can't say I haven't put my own fingers in that pie.
1. Presumably you've written the doc to be read by other people. What's obvious to you might not be obvious to them.
2. If you have no "alternatives considered", it's an indicator that you didn't consider any alternatives. I can think of times when "this is obvious and it's the way we've always done it" sent me down the wrong path. Spending just a couple of minutes considering whether obvious == correct, and writing down why, is not a bad investment in the long term.
3. I can only speak for myself, but I don't enjoy being criticized and I don't enjoy being wrong. "Alternatives Considered" is often at the end of the doc and I'm tempted to avoid it because there's a very real possibility that I will find the process of explaining why we don't just do option B instead leads to a realization that option B is a better alternative than the plan I just spent all that time on.
9/10 times it's short and easy, but it's still a worthwhile exercise for the reasons above. Explaining the "don't do anything" alternative is a good way to reinforce the cost/benefit of what you're proposing, and it's usually pretty easy to put yourself in someone else's shoes for a second and think of the first "but why don't you just" that will probably pop into their head. Write down "because it won't scale" and you've saved yourself that conversation. (joking. maybe.)
The one time I used AI meeting notes, some important details were wrong. And beyond that, the notes were just terrible. A literal transcription can be useful. A summary of the substance of the meeting can be useful. This was neither. A human would know that a tangent talking about the weather is not important, but AI notes are just as likely to fill the document with "Chris mentioned it had rained yesterday but he was hoping to cook hamburgers when the sun comes out. Alice and Bob expressed opinions about side dishes, with the consensus being that fries are more appropriate than potato salad." as it was to miss a nuanced point that a human would have recorded because they understood the purpose of the meeting. And then it'd give me an action item to buy corn.
The main issue I've run into is that I have no idea how to hook into and modify the behavior of fancy modern web sites with all of their React and Angular and Snorfleflox. I was kind of hoping this was for that. Is there some sort of framework that makes that stuff easier, or failing that, a really good tutorial for an experienced but a little out of date web developer to get up to speed?