mckn1ght

Not a fan of touchscreen on inclined surfaces, personally. I think the ergonomics of this will be bad for shoulders/elbows.

Like the iPad when it’s docked to its smart keyboard, I don’t like touching it at the point, it’s better to use the trackpad that’s laying flat.

It also wobbles when you do touch it. The macbook may not do the wobble, but it will constantly push further open and this may weaken the hinge mechanism over time.

> it's so much harder to sift through what isn't worth paying attention to. I wonder if this speaks more culturally to how we consume

I think it’s culturally how lots of people treat many things in their lives.

People always want the best X, whether it’s a place to eat, or hike, or vacation, or get a selfie. It leads to pathological situations where the neat little backstreet spots become overrun, popular hikes get trashed, and people sit around mulling which restaurant to go to for so long that they go way too late or just give up.

People are afraid of a diversity of experience. I understand that time is limited and the desire to not waste it. But, many times the experience is what you make of it, and there’s some good to find most places, not just those with 4.98+ stars.

I hear what you’re saying but let me offer an alternative perspective. Before I started professionally programming I worked in kitchens.

I see way more happy, healthy, financially secure folks past middle age in software than I did in restaurants. I sometimes miss the fun but it’s mostly grueling.

Also, watching what working in the trades did to family and friends.

Take up a physical hobby to stay in balance, and/or learn a musical instrument, if you are able. Hope you hang in there.

And on topic, for some light viewing material for young children, go right now and download all the Mr. Rogers episodes you can get your hands on, while we still can.

I have fond memories of Disney but as an adult there’s not much I appreciate. The oldest stuff is gauche and a lot of the newest stuff is cracked out. There are just a handful I think are really appropriate for my kids, and I’ve retained digital backups of those.

And I spend a lot of time reading to the kids. They constantly beg me for it. It’s hard to do at times but harder to disappoint them.

By that point there will be enough digitized entertainment already produced to last a lifetime. We’re just on the long tail of diminishing returns now.

There’ll always be community theater!

Haha, I thought a well meant free water, until a pinhole developed on the pipe right above the pump, about 250’ below ground.

And like you said, hard to get anyone out to even fix it. We had to wait 6 months for the snowpack to thaw and scheduling to line up. So that meant an extra thousand or so bucks just to build a workaround system in the meantime.

Same boat here. I installed my own ground mounted array at double the capacity for half the quoted price from the local installer, even with an electrician coming in to do last mile hookup. Learned a ton. Got a couple fun new tools. Already have my next spot picked out.

Is it though? Markets may be perfect, but humans are not. There’s plenty of laziness, incompetence and corruption, even in capitalism.

I guess it’s the least worst option we’ve found. That doesn’t mean it doesn’t need any guardrails at all though.

I came here to say something similar. We won’t need to understand the implementation. But we will need to understand the requirements. The tests, or some higher level DSL they’re (deterministically! not via LLMs) generated from, will still need to be human verified.

Personally I don’t like using nil to represent specific states in my domain. I try to only judiciously use it to represent the lack of knowledge about some state, like if I need to reach out to some external service I don’t control, that may or may not give me an answer for my query (and conversely, I don’t like putting “unknown” cases into my enums).

I’d say don’t bother trying to parse it alone. Have a meeting where the person that created it presents it, and drill into anything weird.

If you can back them into a corner and force them to admit they don’t even understand something they supposedly wrote, use that as an opportunity to remind people it’s not acceptable to generate design documents that you don’t understand and then push them off onto other people.

That’s possible to do without also sending all the captured data to police.

Using LLMs is basically rolling a huge number of weighted dice.

I’ve been debating a lot of people on that last point.

A lot of anti slop professors want to bring the debate back around to the mechanical process of coding. I think that’s misguided.

To me, building software is about understanding the users’ needs, knowing what UI patterns work well, how to integrate into the larger platform ecosystem, and ultimately, solving the problems the users have.

Making it about debugging arcane, temporary idiosyncrasies in the platform, 3rd party tools etc is like telling writers they should typeset their own book on a printing press.