People often need a little nudge not to be on the defensive. I usually try to find a point that I agree with and let them know “that’s a good point”. It takes some listening and a lot of patience, but folks tend to reciprocate. It takes two to tango.
> because just like in actual fracking, it is immensely harmful to the long-term health and sustainability of anything it is applied to
An otherwise good article, but weakened by this bit. Fracking and the use of natural gas is actually pretty great ecologically compared to the other ways we get and use fossil fuels. It got a bad rap because it probably really stunted US adoption of renewable resources… and it’s my theory the coal industry was behind the public damnation.
That sounds legitimately hard and I don’t envy you. Hopefully (to carry your analogy) you can find punctual sports fans who freely share their holiday plans.
> Whenever you try to vent how you don't fit into the culture people point out that it's your fault you're the weirdo.
Surely it’s pretty self evident why this is the case.
There’s a natural desire for people to want to make things. Most of the time it’s physical: homes, crafts, woodworking. But for a few of us it’s ok for it to be non physical. Actually, that’s part of the allure of programming: you don’t need much more than a computer and some thinking to build incredibly intricate… things. AI is like a brand new power tool. It’s fun to use because you can build faster. I felt a sense of giddiness the first time I used a table saw after using a push saw my whole life.
This is pretty textbook antisocial behavior. Also, every one of those points is a normal way to deal with someone you don’t like or want to distance yourself from.
I don’t think UI’s natural interface is visual. I think the natural interface is a state machine.
The most reliable and performant UI code I’ve written usually tackles this head on by thinking through all the possibilities of different states the application can be in and how the transition of each state should look. This can very quickly get mind boggling complex.
Systems programming languages seem like they model their problems better because it’s less common to ask a systems programmer for a like button that shows bubbles when you press it. If you model your UI explicitly like a state machine, you can say “no” to the bubbles like every systems programmer says “no” to most features, because you realize the explosion of state will be unmanageable. Or you can use a JavaScript framework and download a bubbles package and wonder why your app is buggy, but have job security.
I bought one for coding. I no longer can read text for an extended period with lower DPI monitors.
There’s a few reasons why.
1. Non integer scaling sucks on Linux. It sucks on all OSs, but it’s just unusable on Linux IMO.
2. Text antialiasing sucks for most OSs except Microsoft ClearType, but I hate Windows.
I currently use an old LG UltraFine 5k. It’s physically cracking / falling apart and has atrocious burn in. I tried replacing it with a Dell 32” 6k monitor. The stupid matte coating on it and seemingly all other high DPI screens is so, so bad.
I just want glossy 5k at 120Hz with decent build quality and color accuracy.
I don’t even like the fact it’s mini LED. Blooming is pretty awful on those things. I hope there’s a way to turn it off.
So yes, I bought a $3,500 monitor to read text because no one else can seem to do it even remotely acceptably.
> this generated function is not understood completely
I think this kind of stuff is OK for the most part. I think it's a thrilling part of computer science: building systems so complex they're just on the brink of what can be fully understood by a single person. It's what sets software engineering apart from other engineering fields where it's unacceptable not to fully understand the engineering, say, for factories, buildings, bridges, ships and infrastructure and such.
Aim to make the road laminar. Every time you hard brake, you're causing the milk jug to glug, making a ripple of entropy as momentum turns to heat from your brakes and those behind you, sometimes in perpetuity. I learned this while doing a 1.5hr daily commute in a Subaru with a clapped out manual transmission. I wanted to conserve energy shifting, but realized I was now participating in large choreographed dance of "smooth" with other drivers who already knew this. There are many of us. And we all glare at the driver blinking their red lights on the interstate indicating that they're loud and proud of introducing turbulence to an otherwise peaceful system.
I recently installed a mini split heat pump in a detached accessory building. The installer upsold me on a more expensive unit because I’d get federal refunds due to its higher SEER rating. Ok, sure: higher efficiency, same price.
In fact, efficiency was the main reason I wanted a mini split in the first place. It just bugged me to _not_ pump the heat entirely outside the structure. And I paid a bit more for that versus just using a window unit or “portable” AC. All we’re talking here is the location of the condenser coil: inside versus outside. It just makes sense to put it outside, with just a small penetration in the building.
Well, during electrical inspection apparently I paid too much. After paying more than a certain threshold for converting an unconditioned space to a conditioned space, I now need to insulate the accessory structure to a certain degree in order to pass code.
The kicker is, the only way I can insulate the space to meet code is to insulate with polyiso (aka styrofoam) because the structure is so small. So, I guess in an effort to be “green” according to local government, I need to rip out the mineral wool insulation, dump it and replace it with styrofoam. Or put the mini split in the dump and buy a cheaper less efficient unit like a window unit.
I’d save approximately $0.30 a year on energy costs to insulate to code versus what I have now with the mini split.
This whole industry is stupid and that’s because it’s regulated by idiots.
Yes, exactly. The demo of Gemini's Diffusion model [0] was really eye-opening to me in this regard. Since then, I've been convinced the future of lots of software engineering is basically UX and SQA: describe the desired states, have an LLM fill in the gaps based on its understanding of human intent, and unit test it to verify. Like most engineering fields, we'll have an empirical understanding of systems as opposed to the analytical understanding of code we have today. I'd argue most complex software is already only approximately understood even before LLMs. I doubt the quality of software will go up (in fact the opposite), but I think this work will scale much better and be much, much more boring.
> In fact, we didn’t found Tailscale to be a networking company. Networking didn’t come into it much at all at first.
I always just assumed they were building some kind of logging software (“tail”scale), used Wireguard to connect hosts, and just kind of stopped there. Don’t get me wrong, Tailscale is a nice way to connect machines. It’s nice because Wireguard is nice.