

Everything Everything
They’ve written some of my favourite albums over the past decade or so
Everything Everything
They’ve written some of my favourite albums over the past decade or so
A tariff is a tax
This is the update that’ll break sync, right?
Sad times, but I guess I’m gonna be deciding between boost and infinity tomorrow
Also, whilst we’re on the subject, cement lube is not safe for cement toys
Is it just me that sees double strikethroughs on the dollar symbol hilariously childish?
I really should go and get checked, eh?
This is the first time I’ve realised these comics are actually from the 50s and not just modern ones stylised to look like it
I kinda feel like heat would be wasted energy that could be used to grow
Big thanks for providing this extra context, that made it a lot clearer for me
Yes, silly engineers that don’t like being held to unrealistic estimates and deadlines; typically the ones that arise at the start of a project where there are still who-knows-how-many unknowns to find.
Waterfall is the most effective tool for software engineering in a world where the whole world stops once you’ve planned and only starts again once the project has finished—i.e. a fictional world that doesn’t exist. Literally every waterfall project I worked on back in the old days was derailed because something happened that wasn’t planned for—because planning for everything up front is impossible and planning for anything more than a handful of eventualities is impractical.
Agile and subsequent methodology comes from realising that requirements will change and that you are better off accepting that fact at the time than having to face it once you’re at the end of the current road.
Agile does not mean engineers talking continuously to the users, engineers are hired to do what they’re good at: engineering. Understanding user requirements and turning that into a plan has always been product’s job regardless of methodology, in agile and similar it’s just spread out over the duration of the project, not front loaded. Agile isn’t “make the engineers do every proficiency”.
They did those starter sku users dirty
But yeah this was Microsoft’s strategy for a while (and may still be): they attempted to push small business users to their server products for running servers by limiting the ram and core counts on the non-server skus.
A software engineer was not involved in this if waterfall is painted positively.
I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.
You get used to it, I don’t even see the code—I just see: group… pattern… read-ahead…
It’s funny, I got into my current relationship around the time the apps started coming out so I’ve never really used them, but I remember people were praising it as a lot safer for everyone involved.
And tbh I can see that being the case compared to the older school approach of nightclubs being majority populated with people actively trying to find someone to sleep with
I’ve not really touched radio stuff in a long while now but here’s my attempt.
Single sideband (SSB) is a radio transmission technique for sending audio (often voice, but many data modes use SSB too) whilst being pretty efficient with the use of radio spectrum. Think like FM and AM modes on a consumer radio, except those approaches take up a bit more bandwidth compared to SSB, so you can’t pack as many stations into a radio band without interference.
And this is where I might be completely off the mark, but this novel approach is interesting compared to the more conventional approaches due to the reduction in the complexity of the components needed to do this and a reduction of waste power. As the other approaches involved essentially generating a double sideband signal (I can’t remember what the technical term is, but part of me thinks this might be standard AM) and filtering out the (typically) lower mirror band.
Not really in a situation where I can watch a video without potentially annoying someone right now, but
A municipal mesh network isn’t a bad idea, but I worry about what security measures are in place, effectively securing a wireless network with hundreds of independent stations feels like it wouldn’t be trivial.
And surely this will need a WAN gateway to the internet somewhere, so it’ll only be as reliable as the route to that uplink.
This might have all been addressed in the video though, I’ll see if I can find an article about it.
Was just thinking this
A single LiDAR sensor prevents this kind of issue