I'm similarly unpredictable in my home. Add to that the others in my house, and it's impossible to even guess what everyone's intentions are at any given time.
Sometimes I daydream about a "solo mode" where the timings on lights are tighter and my music can follow me around the house when I'm up at night and nobody else is. But most times I'm trying to find the get-out-of-way averages that keep everyone happy.
Some things work great: Automated lights everywhere. Automated dimming of lights at night or sunset or whatever. Notifications when the laundry is done, or the cat litter is ready to be changed, or someone is at the door, or the garage door has been left open - all great. What music to play in what room at any time? Always changes. When to "dim all the lights" because Plex started a movie? But my son is building Legos in the dining room, and my wife is knitting and needs the couch light on. Sometimes I want it, but not every time.
For those things having a single button press is still a huge win over opening multiple apps and getting the right things set the right way for each participant.
I feel like dealing with robo-calls for the past couple years had led me to this conclusion a bit before this boom in ai-generated text. When I answer my phone, if I hear a recording or a bot of some sorts, I hang up immediately with the thought "if it were important, a human would have called". I've adjusted this slightly for my kid's school's automated notifications, but otherwise, I don't have the time to listen to robots.
Robocalls nowadays tend to wait for you to break dead air before they start playing the recording (I don't know why.) So I've recently started not speaking immediately when someone calls me, and if after 10 seconds the counterparty hasn't said something I hang up.
I have the same issue. Even when I ask it to do code-reviews and very explicitly tell it not to change files, it will occasionally just start "fixing" things.
I find Copilot leans the other way. It'll myopically focus its work in the exact function I point it at, even when it's clear that adding a new helper would be a logical abstraction to share behaviour with the function right beside it.
Overall, I think it's probably better that it stay focused, and allow me to prompt it with "hey, go ahead and refactor these two functions" rather than the other way around. At the same time, really the ideal would be to have it proactively ask, or even pitch the refactor as a colleague would, like "based on what I see of this function, it would make most sense to XYZ, do you think that makes sense? <sure go ahead> <no just keep it a minimal change>"
Or perhaps even better, simply pursue both changes in parallel and present them as A/B options for the human reviewer to select between.
I will never understand why we fill our walls with mechanical and electrical infrastructure and then wrap them in a paper and plaster, which then needs to be torn, broken, and repaired in order to maintain said infrastructure.
Pipes will fail. Wires will fail. Ducts will fail. Maybe not in 5 years, but over the span of 20, they will. Why make them so frustratingly inaccessible?
Drywall is trivial to remove and repair, I have no issue cutting walls with a circular saw or vibrating cutter to get access then patching it.
I have seen another method for making walls that were accessible though, from a homesteader/ hand tool woodworker and carpenter. His walls were 24” thick with huge areas for piping and electrical and had 4x4’ removable wood panels.
I wouldn't call it trivial. First you have to determine where to cut it; if you cut the wrong area you have to cut again. All the steps in repairing it either take time, are messy, or require some skill, and the time adds up (e.g. waiting for the patch to dry before you can sand; waiting for the primer to dry before you can paint; etc.).
And then you have to match the surrounding paint, which is all but impossible since even if you have the same color, the original will have likely faded over the years, making your newly applied coat a mismatch, so now you have to paint the entire wall (no fun when it's a big wall). And if you had wallpaper instead of paint, good luck to you unless you saved some extra scraps.
All in all, an access panel would make the job much simpler.
Ok, I glossed over color matching the wall patch. Fair.
But there really aren’t many walls you need to open in a house. There is probably 2-3 wet walls, so unless you need to retrofit some ducting why are you opening a wall? Code says there are no hidden wire junctions, so you’ve just got continuous runs of romex that are secured before they terminate… what do you open a wall for?
Most of the drywall repair is just physical damage to the drywall itself.
In theory, I'd rather get at something through an access panel than via cutting and patching drywall, but practically speaking, you're right: it's rare to have to open a wall, and an access panel that isn't specifically for something you need to access regularly is just a nice-to-have, and not even necessarily all that useful unless it provides the access you actually need at the time.
The thing is you might not need to access your electric or plumbing for like 100 years. You do get a panel where access is presumably on a more regular schedule: usually the shower hookups are accessible from a closet.
I watched a video recently, which I can't find, where an architect set up a beautiful wooden baseboard around the entirety of their property, and that baseboard held all mechanicals and was perfectly clean and easy to get into as needed.
Drywall is manageable and cheap, I agree. But it's more painful than it should be for something that _will_ require maintenance.
I've seen videos where people will put in removable drywall panels that can just be lifted out for access.
There are a lot of downsides though. You lose airsealing, if you don't have an airtight building envelope on the outside of the drywall. You lose fire resistance. You often lose aesthetics, although I've seen this done extremely tastefully. You lose childproofing, and run the risk of a kid electrocuting themselves or destroying your plumbing or dropping stuff in the wall. You impose constraints on what can go on the walls and where your furniture can go.
Given that drywall is pretty easy to cut and replace, most people figure it's just not worth the costs for something you do infrequently.
This sounds great but violates all the building codes for a variety of reasons: eddy currents, risk of electrocution if there’s a short somewhere, noise in telecom cables, etc.
You can absolutely put NM cable, etc, under a cover. It's just more trouble than it is worth. You still need the required setbacks from the wall, etc, and .. there's reasons why bored holes very low on the wall (like for a baseboard cover) could be problematic.
And for telecom / low voltage, you have a lot of freedom of how you do it.
Mass production should be able to make this standard. Walls don't vary that much.
Personally I've been printing snap in access panels whenever I have to get into a wall these days - in white PETG they pretty much disappear into the wall for me.
If we ever build another house, it's going to be attic-free with exposed conduits + hvac ducts / pipes on the ceiling. Every electrical box is going to have a 2" conduit (embedded in the wall) running up to a conduit that runs on the ceiling (if there's a basement, then down to the basement ceiling).
This would let us avoid stapling electrical lines + network cables to studs inside walls. Fixing shorts, adding circuits and upgrading network lines would be trivial.
We'd have to buy what, 1000' of conduit? There's no way that's a sufficient fraction of the cost of a house.
In Chicago, code requires EMT for all electrical, which can be annoying for adding a new run, but at the very least it makes it less likely for rodents to chew through or other interference.
After wiring my whole house with Ethernet and ceiling speakers, and now dealing with a couple leaky pipes and several problems from previous owners, I'm considering ways to make these things easily accessible/replaceable while keeping an eye toward aesthetics.
For nearly a decade, Chicago does allow MC cable in a number of circumstances, basically up to 25 feet branches where you don’t want to open up a wall.
Rarely do pipes, wires, or ducts just outright fail even in 50 years. Usual case for tearing out drywall is for voluntary renovations. Shit behind the wall just doesn't "fail" if it is left undisturbed or you were unlucky like those that got defective PEX or similar installed.
Wires not really but copper and iron pipes and ducts can and do corrode away. Ive seen hvac ducts that were more hole than anything but nobody noticed under the floor or above the ceiling.
My house is 150 years old, but it's also been rebuilt several times in that time. My neighbors' houses are less than a decade old. We have all swapped stories about replacing things behind drywall. Leaks. Electrical issues. Ducts. Everything. Consider yourself lucky if you have not. 50 years is not the number you should bet upon.
So outside of a few notable examples, the materials rarely fail, galvanized duct work should easily last half a century in a properly installed and maintained system, properly installed copper pipe or PEX and even (C)PVC, properly installed NM or wiring in conduit where code requires, where people get into trouble is with shoddy builders and the housing market often causes those to forgo proper inspections and it is ultimately a “market for lemons”. But blaming drywall seems a bit misplaced, since shoddy building in targeting cost only, they’re going to be the last ones replacing drywall with something fancy and expensive.
About 15 years ago I installed a new kitchen faucet for my grandmother, whose kitchen had been renovated in the early/mid 90s. Right near the end of the time when PB was inexplicably popular. I have to say, I spent several hours cursing whoever decided to use PB, and in this particular case whoever decided that the pipes should connect directly to the faucet rather than terminate at a bog standard quarter turn valve. Lots and lots of cursing.
As I recall, wasn't PB basically a single vendor, too? Finding PB-to-anything-else adapters at Home Depot was like going on a treasure hunt. Sizing is different, so you really need something actually built for PB. And probably end up with sharkbites. If I were shopping for a house right now and found it had been plumbed with PB, I'd just turn around and walk away.
The paper is a critical technological innovation. It shrinks upon drying, turning the sheet into a prestressed panel. Predecessor manufactured wall materials like Beaverboard are much flimsier because they lack a taught skin that enhances rigidity.
I wouldn't call it easy, but it's conceptually simple to cut a square hole in some drywall to access behind it, and then pop the piece back in with screws, mud, and tape, then paint.
For sure. I've wired my old house with speakers in every ceiling, and cat-6 in every room. I've had a small pipe burst and a couple leaks behind a bathroom.
I've patched quite a bit of drywall, and I'm about mediocre at it. But it seems so silly and unnecessary to me.
Everything else in this world that requires maintenance comes with access panels and other means of easy access. In our living spaces, some of which should ideally last tens of years (mine is from the 1890s), we seal it all away.
I'm with you. I can read a post like OP and appreciate that drywall is a lot better than what came before, but I find it difficult to understand how we haven't come up with something better.
Something less heavy, easier to fix without expertise, doesn't require applying some surface pattern to hide imperfections when used on a ceiling.
I guess something conceptually like a drop-ceiling (which has a "finished" look, but is very accessible for maintenance), except for walls. That's what we need.
Because drywall is cheap, incredibly tolerant of movement and irregularities. It's also super easy to repair. It can also act as an air barrier for energy efficiency. A drop ceiling is terrible for that and is ugly AND expensive.
If I ever have a house built to my own specs, I want to get the best of both worlds by using drywall, but with most/all of the interior walls being maintenance corridors accessible via concealed doorways. A modern version of the way the dormitory in Real Genius was constructed.
Just make the house itself ~10% larger than it would be otherwise, so the usable floorspace is the same.
Adding/repairing wiring and plumbing would be easy. Every wall could have two layers of thermal/sound insulation. And who doesn't love secret passages?
And do what? Leave the ducting, pipes, and electrical lines exposed for the one time in 20 years you need to do something with them?
In addition to being much more attractive than exposed infrastructure, drywall and the insulation that gets put behind it help make your house much more energy efficient.
People prefer how it looks and it's also more convenient to have a square room and no irregular protrusions stopping you pushing furniture up against the wall.
In the UK it used to be common for pipework to be exposed and painted. Electrical conduit is pretty common in "industrial" places like garages but the number of sockets people expect now would mean you'd barely have a flat wall anywhere.
The current preference is definitely for clean looking, square rooms. When pipes don't fit in the walls themselves, like soil pipes or around boilers, they are boxed in or hidden away in a cupboard.
Generally things that are illegal are illegal because enough people have maimed or killed themselves with it in ways that are not “common sense”. For example, you can’t simply have electrical wire stapled to the bottom of the joists in the basement because people might try to hang clothes off of them.
It's legal and done quite often in industrial installations - look around the next time the lights are up at your favorite restaurant, for example.
It is more expensive, by more than you'd think, and so it's rarely done.
It also allows all of the trades save the drywaller/painter to be rough and tumble with what they're doing; it doesn't have to look nice behind the walls.
I can only wear tall-size clothing, and generally I've found that none of my t-shirts shrink "in", but they _all_ shrink "up". I can make them last longer washing them delicate and "air-drying" (in the dryer, light or no heat), but eventually they all get shorter. I have to replace most of my undershirts annually, and I rarely bother with t-shirts anymore.
I haven't used cursor, so I'm not sure I can be much help there. I've been mostly using claude code and IntelliJ IDEs for code-reviews when necessary. Over the past year I've moved to almost entirely coding via agent. Maybe my input will be helpful.
One very important thing to keep in mind is context management. Every time your agent reads a file, searches documentation, answers a question, writes a file, or otherwise iterates on a problem, the context will grow. The larger the context gets, the dumber the responses. It will basically start forgetting earlier parts of the conversation. To be explicit about this, I've disabled "auto-compact" in claude code and when I see a warning that it's getting too big, I cut things off, maybe ask the agent to commit, or write a summary, and then /compact or /clear. It's important to figure out the context limits of the model you're using and stay comfortably within them.
Next, I generally treat the agent like a mid-level engineer who answers to me. That is to say, I do not try to convince it to code like I do, instead I treat it like a member on my team. When I'm on a team, we stick to standards and use tools like prettier, etc to keep the code in shape. My personal preferences go out the window, unless there's solid technical reason for others to follow them.
With that out of the way, the general loop is to plan with the agent, spec the work to be done, let the agent do the work, review, and repeat. To start, I converse with the agent directly. I'm not writing a spec, I'm discussing the problem with the agent and asking the agent to write the spec. We review, and discuss, and once our decisions are aligned and documented, I'll ask it to break down how it would implement the plan we've agreed upon.
From there I'll keep the context size in mind. If implementation is a multi-hour endeavor, I'll work with the agent to break down the problem into pieces that should ideally fit into the context window. Otherwise, by this point the agent will have asked me "would you like me to go ahead and get started?" and I'll let it get started
Once it's done, I'll ask it to run lint, typechecks, automated testing, do a code review of what's in the current git workspace, compare the changes to the spec, do my own code reviews, run it myself, whatever is needed to make sure what was written solves the problem.
In general, I'd say it's a bad idea to just let the agent go off on its own with a giant task. It should be iterative and communicative. If the task is too big, it WILL take shortcuts. You can probably get an agent to rewrite your whole codebase with a big fancy prompt and a few markdown files. But if you're not part of the process, there's a good chance it'll create a serious mess.
For what you're doing, I would likely like ask the agent to read the mega python file and explain it to me. Then I would discuss what it missed or got wrong and add additional context and explain what needs to be done. Then I would ask it if it has any suggestions for how we should break it into submodules. If the plan looks good, run with it. If not, explain what you're going for and then ask how it would go about extracting the first submodule. If the plan looks good, ask it to write tests, let it extract the submodule, let it run the tests, review the results, do your own code review, tweak the formatting, Goto 10.
> Next, I generally treat the agent like a mid-level engineer who answers to me. That is to say, I do not try to convince it to code like I do, instead I treat it like a member on my team. When I'm on a team, we stick to standards and use tools like prettier, etc to keep the code in shape. My personal preferences go out the window, unless there's solid technical reason for others to follow them.
Do you suppose it would work to prompt a separate agent to infer coding style preferences from your commits and then refactor the first agent's work to bring it in line?
I had this exact same experience in ravenswood this weekend. I was walking to breakfast and one of these bots was blocking the entirety of the shoveled part of the sidewalk. I had to make may way into the snow to inch around the bot just so I could continue to use the sidewalk.
I had guessed it was stopped because it came to an unshoveled portion of the sidewalk. If it can't traverse that, it's not made for this city
I'm not fundamentally mad as these bots. But if they don't figure out how to make them work with other pedestrians, then I'm going to start cheering on any vandalism delivered upon them.
> I had guessed it was stopped because it came to an unshoveled portion of the sidewalk. If it can't traverse that, it's not made for this city
Have them partner with the city and collect evidence of unshoveled sidewalks. Automatically issue fines based off the collected video evidence.
This is one of those things where if these bots cannot traverse a section of sidewalk, many with mobility issues cannot either. And it's endemic to the city.
In my neighborhood there are $5m+ houses that literally never shovel their sidewalk the entire year, as well as a few businesses on "main drag" retail corridors. Fines for this have become exceptionally rare to non existent.
I wholeheartedly agree that it's significantly worse than single-payer, but to say it hurt young people simply doesn't match reality as I saw it play out.
The ACA allowed me to get insurance for the first time since I'd left home several years before. I knew lots of other freelancers at the time who were in the same boat.
Of course in the following years, insurers found plenty of loopholes to increase prices significantly year over year - and this is why leaving the middlemen in the middle was a TERRIBLE choice - but at the very least the quality of those plans still has a reasonable low bar.
I still find myself on the ACA from time to time. I can't afford it. But the plans are still significantly better and thus more affordable than what was available before.
Sometimes I daydream about a "solo mode" where the timings on lights are tighter and my music can follow me around the house when I'm up at night and nobody else is. But most times I'm trying to find the get-out-of-way averages that keep everyone happy.
Some things work great: Automated lights everywhere. Automated dimming of lights at night or sunset or whatever. Notifications when the laundry is done, or the cat litter is ready to be changed, or someone is at the door, or the garage door has been left open - all great. What music to play in what room at any time? Always changes. When to "dim all the lights" because Plex started a movie? But my son is building Legos in the dining room, and my wife is knitting and needs the couch light on. Sometimes I want it, but not every time.
For those things having a single button press is still a huge win over opening multiple apps and getting the right things set the right way for each participant.
reply