I did this for the buttons on my standing desk, but the adhesive wasn’t that good and they fell off after not too long. In the end, I wound up leaving the desk in standing mode most of the time so I haven’t needed to figure out a more permanent solution anyway.
Trying out ordering non-brand name items from Aliexpress, since I figure I may as well cut out the middleman (Amazon) that’s not actually providing any value.
We have the strangest bug. We’re showing some Icelandic text on a web page and despite it being correct in the DOM (according to Safari and Chrome’s web inspectors), the lower case Icelandic “eth” character (ð) is being rendered in uppercase (Ð). Can’t see anything in the applied CSS which might be fiddling with it. But no matter how we specify it (ð or ð or ð), it’s rendered in uppercase. Webpack, Typescript, Vue, Tailwind.
All the recent Git Discourse is really highlighting for me that my general level of comfort with Git is facilitated in large part by Magit, which is probably the best application ever written in emacs lisp. When I want to do something with the git command line I am often reasoning by analogy to a magit UI element that I know will do the right thing, so if I fumble with commands a bit it's just a question of finding the right one, not struggling to understand if what I want is possible
@glyph I don’t use magit (or emacs), but that’s pretty close to how I feel about manipulating git. I have a sense for what I want the result to be, and the hard part is finding the right commands to get from where I currently am to where I want to be.
I think most people don’t really have a solid idea of the latter expressed in a model that is git-sensible? I.e., they’re thinking mostly in files and branches as opposed to commits, maybe?
I'm waking up to a lot of Discourse on here about Git so of course here's my take:
I am increasingly uninterested in saying that tools are "good" or "bad”. It's all just so contextual.
But I can't think of a tool that I've used as long (over 10 years I think?) and as frequently (daily), that frustrates me this much and that I make bad mistakes with this regularly (monthly at least). Something about Git just DOES NOT fit my brain. (This is not an invitation to explain git to me!!)
@glyph But also, this is also pretty much me - I very rarely make mistakes with it and am usually the git guru on my teams, and basically am able to make git do what I want since I do have a pretty good mental model of what I can do with the abstractions. Though that being said, I don’t think my criticisms of git are that it’s simplistic or limiting, but more around the UX and mental model being divergent. Also that people often actually have a fairly reasonable model of the commit graph (modulo usually thinking of commits as diffs, but eh, that’s generally fine) but are lacking a good mental model of refs and HEAD and the index.
@nat I love Doing the Work, but unfortunately, I think part of that includes “day two” type operations, which made me pretty unhappy with a bunch of what I saw at Labs. I’ve pretty much stopped caring about ladders at this point, but I also don’t mind (and somewhat expect) to be getting my skill improvements outside of work.
@ratkins@nat Yup, that’s one part of it, though IMO the benefits you get from blue-green deploys aren’t actually that important, but you may as well do it since usually the cost is quite low. (I think most companies don’t actually need zero-downtime or instant rollbacks as long as deploys are fast enough.)
But there’s also that a lot of the process is built around the assumption that you can change course before having committed too many resources, when that just wasn’t happening due to not being in front of users.
I think also an over-reliance on interview-style UX and the idea “saving development time with UX” as opposed to metrics exacerbated this, and we sorely neglected the option of making it cheaper to just build the damn thing instead of testing idealized prototypes.
@nat@ratkins Ha, that in particular is a huge pet peeve of mine that I probably mentioned in all my interviews when asked about what I was looking for in team culture. I hate telephone and having people in the middle just passing messages back and forth while losing fidelity on both sides the whole time.
@nat I somewhat unseriously but also sort of actually believe that people at that level (of wealth/privilege/power/etc) just aren’t really… real people, if that makes sense? They’re just so far removed that even if they wanted to and could actually know, they can’t.
I'd like to give a conference talk about what infosec can learn about risk from outdoor recreation — kayaking, backcountry skiing, climbing, mountaineering, etc.
A focus in these communities is “safety culture": finding ways to pursue inherently dangerous activities more safely. Lots of it translates to infosec!
If you think this would be a good fit for your con, reach out! I'm not looking for special treatment, happy to put a proposal into a CFP, just not sure who might be interested.
@jacob Even though I don’t do much outdoor climbing anymore, every few years, I read the latest Accidents in North American Mountaineering as a reminder to not be complacent. I suppose the equivalent for developers is reading incident reports? Unfortunately there aren’t many that are on the same scale as ANAM, which doesn’t just cover major incidents.
@jacob I appreciate that it covers the gamut for consequences from death to “almost got bit by an animal in a hold”, and that you generally want to use the same precautions regardless since you can’t predict whether the consequence will be, well, inconsequential or not.
What’s the consumer product rating site people have mentioned here a few times recently? Not Wirecutter, not Consumer Reports, it might have even been European?
I've been playing around with setting up OpenSearch because I'm not really happy with how annoying it is to actually search my logs with Loki (fundamentally, I just want a Datadog- or OS-style dashboard), and… it's rough.
Setting up OpenSearch is difficult as the docs are definitely aimed at large clusters with minimal support for standing up a simple instance. But then we get to Data Prepper and… yeesh. It works, but it feels very, very rough.
