Personally I still find it really helpful to have a proven framework to rely on so that I can be confident I'll have a reasonably consistent looking UI across a range of browsers, browser versions, screen sizes, and OS even versions.
Bootstrap was/is popular for the same reason. One framework and your site looks decent on almost any device. The downside is a bit like LLM work in that it all ends up looking like a Bootstrap site unless you’re a good designer.
Pre-taking medication, here's what my personal experience trying to focusing looks like:
I have some really interesting, but lengthy text that's really important for me to read for class. No cell phone, cleaned my room, put on specialized focus music, jot down all my random thoughts on a notepad, got myself a cup of coffee and made sure I eliminated all distractions.
I then proceed to read the first two or three sentences before I realized I have been mindlessly scanning the text with my eyes like I'm reading, but instead I am doing the equivalent of watching a movie. I'm 100% zoned out and in la la land.
I realize this, so I stop, refocus, repeat. I realize I did it again, stop, refocus and try reading out loud. I'm annoyed because I'm saying the words out loud but not comprehending it.
I meditate for 30 seconds to calm my mind, try to refocus and repeat. I finally get through it after about 30 minutes.
Here's how my personal experience looks with medication:
I pick up the damn paper, read it and summarize it with notes in 5 minutes.
Your comment reminded me of a funny interaction I had a week or so ago.
I got a call that started with the usual automated message, "This call is being recorded." After the person joined, I pushed the record button on my iPhone, "This call is being recorded."
They were surprised and asked why I'm recording.
I said, "You're recording, so I'm recording too."
The rep insisted that the company doesn't like this but that they will continue with the call anyway.
Anyway, I wish people took this stuff much more seriously. It always seems to boil down to, "I don't have anything to hide" type of conversations and I've never managed to convince anyone that privacy as a concept isn't about having something to hide.
What is actually perfect, when the automated voice declares the call is being recorded, you don't have to do it again. You're legally allowed to record, because both parties were informed already and agree to it.
The operators of the phone system are consenting to the call being recorded by informing you that the call is being recorded. You are consenting to the call being recorded by continuing with the call.
I mixed it up and GP is right. But you are also right (which illustrates the point GGP was making)
If you and I are in a phone call (the target of the phone call located in a one-party consent jurisdiction), I can record it or you can record it without telling the other: that's one-party consent, because one of the parties of the call consents to it
At first glance that may sound pointless, but it means a third party outside the call (e.g. phone company) could not record it without one of us consenting
By notifying that the call is being recorded, that now can create two-party consent because you are still on the line (and thus implicitly agree to the recording, but as you and GGP point out that's not always considered consent enough) -- one-party consent would have been if the company on the other side of the line simply recorded the call without telling you
"I have nothing to hide" -> "Ok take off your cloth". Privacy is a useful social construct not some abstract mathematical concept. Everyone has stuff to hide and that's ok.
I didn’t see it in the article, but I wonder if this is still the case if people who properly vent before turning on their gas stoves and continue to vent for a minute after cooking is finished.
Almost no residential units have good venting. Even the better ones are good for the back burners, but the offgassing from the front ones is mostly uncaught.
> "could argue that it has been harmed by the diversion of the funds to a different field. But that argument would likely take so long to sort out in court that all the money would have been spent by then."
So if I steal from someone and spend it fast enough, I wouldn't be responsible anymore and can get away with it? That's how that sounded to me.
Just thinking about how this could be useful and it could serve as an interesting counter example. So if you have an idea and you find it on this graveyard, it's probably something not to do or it might be worth thinking on a little longer before proceeding.
I spun up an old laptop the other day and it has Windows 10 on it. I can't believe how snappy and fast that old laptop felt in comparison to what I've been experiencing on Windows 11.
Especially when you consider that the old laptop has inferior hardware to my newer one with twice the RAM.
I will say, I love the idea of re-thinking PR's in the age of AI. I think it will be needed and I don't see GitHub pulling it off. I think they will just double down on trying to get AI to review it for us.
I haven't signed up, but I'm not convinced the stacked PR's is a good route. This is mostly because I'm thinking about it in terms of how I work now, so maybe after a trial run I would see it differently. My experience with launching software is people don't want to change their workflows.
So the way I imagine how this would get used by real accounts is they will still review individual PR's and merge them in like normal and avoid doing stacked PR's because a lot of us mostly care about the final result and less about the how you got there.
That is until we need to understand the how lol So being able to visualize this is probably a very useful tool for retroactive inspection over being part of the PR review workflow.
I hope the author doesn't feel like I'm dunking on them, I really love the idea of re-thinking PR.
It doesn't work if you're treating it like a peer engineer. It only works if you treat it like you're a customer with no concern with how it works behind the scenes.
That's what's being asked of me in my last two jobs. Vibe code it, if it's bad just throw it away and regenerate it because it's "cheap". The only thing that matters is that you can quickly generate visible changes and ship it to market.
Out of frustration I asked upper management (in my current job), if you want me to use AI like that then I'll do it. But when it inevitably fails, who is responsible? If there's no risk to me, I will AI generate everything starting today, but if I have to take on the risk I won't be able to do this.
Their response was that AI generates the code, I'm responsible for reviewing it and making sure it's risk free. I can see that they're already looking for contractors (with no skin in the game) that are more than willing to run the AI agents and ship vibe code, so I'm at a loss on what to do.
reply