Is my remote experiences strange or do other remote workers not have some sort of chat where people ask if you've got a minute and drop in a video conference link if they need a quick chat on something?
No idea, but yes, that's exactly how we do it. We've been full remote since COVID and honestly, I don't think any of us would want it any other way but we're a very small team so not representative of larger trends.
I've had to cook from scratch for many years because I've lived with people with various food restrictions and sometimes that's just the easiest way to do things.
That said, you really don't need to spend 1-2 hours a day on cooking. If you put a little time in and level up on some basic skills, you can make shockingly good meals in 10-20 minutes.
It's mostly a question of figuring out what you like and getting good at making those things, then generalizing the skills you have into making more things.
Comments are a gift to future you. When you pick up the code again after 6 months/years/however-long-in-the-future and it looks like something you've never seen before, the comments you left should be notes you need to build context around what's in the code and (sometimes more importantly) what's NOT in the code.
This is one side, and this is something that I had in mind. However, I found that there is another popular opinion (1): that in reality, commented code is harmless. The problem is that it's messy and makes it difficult to read, etc.
I have heard devs (typically on the greener side) make the argument that comments in code are bad because they need to be maintained along with the code they're commenting on. It's quite common for devs to neglect this, leading to comments that are no longer correct, and an incorrect comment is worse than no comment.
The argument touches on truths, but in my opinion pretty seriously overstates the problem. Good comments tell you things like why a design decision was made, what hidden assumptions the code is relying on, etc. Things that don't often change unless refactoring is happening. The benefit of good comments is so large that, in my opinion, they are well worth this cost.
The same devs are often also of the opinion that writing code in a self-documenting manner eliminates the need for comments. This is just incorrect. Good comments tell you what the code itself can't.
> writing code in a self-documenting manner eliminates the need for comments. This is just incorrect.
why do you think it is always incorrect? in my opinion "good comments" about design decisions, hidden assumptions the code is relying on, etc. should be included in documentation or surrounding .md files, but not in code sources. Sentences made of english words and sentences made of instructions for computer/interpreter are completely different constructions which imply separate language processing in programmer's brain. it is like mixing up english and french in a single book page -- one french sentence per 30 english is tolerable, while 30 french sentences mixed up with 30 english ones become much less informative than if they were seprarated into different pages.
Hmm...a lot? For a complex work, you'll sometimes do some number of sketches and studies and drawing and underpaintings...Lots of things get tried/discarded/modified before you land on a final painting.
Taoists discovered this phenomenon thousands of years ago and called it overdevelopment. And it's universal for all processes under the Sun. There simply isn't infinite progress in one direction, because it's a circle. The ideal way is to switch one circle for another at its peak development, but recognition of that point requires using the heart, not the brain.
This is a large part of the discussions in the first one or two interviews in Interviews with Francis Bacon by David Sylvester. Bacon talks about pushing to the limits of adding more to a work until it's good, and then if taken too far it ruins the work. And only very rarely can he pull it back around to good.
My wife is an oil painter, abstract expressionism, and she will constantly worry if something is done. And there have been glorious paintings ruined by one last thing.
The article seems to ignore the fact that many people use the shopping cart as a walker substitute. It's an accessibility aid and it's genuinely difficult for some folks to return the cart and walk back to their car.
Which still doesn’t make much sense because there are already some walkers which are designed to lock into most types of shopping carts. So you just bring the cart back to the stall, detach the walker from the cart, and use your walker to get back to your vehicle.
And your description also doesn’t explain how those who walked all the way over to the carts in the first place were unable to bring the carts back. Carts don’t magically appear beside vehicles. How are people who can make it to a cart be suddenly unable to bring by it back to that same spot? And with many stores, carts are picked up at the store front and returned much closer to the cars than the store front.
And finally, this doesn’t explain how so many carts are failed to be returned. Is 25+% of our population disabled?
I feel for anyone who is in pain and cannot walk far. But methinks you are making excuses for arseholes and selfish twats that vastly outnumber those who have genuine excuses.
I noticed that myself, and confirmed with a friend: when you begin to get some harsh backpain (before getting a surgery), you find it pleasant to go shopping and be the one using the shopping cart all the way through.
You could be right if people drove standing up. When seated, the pressure on the lower back (L3, L4, L5, S1 vertebrae) is reduced and you can drive perfectly.
I really only use lazy git to review my code before commit it and I inevitably his the wrong scroll key and split the windows in half when I didn't mean to and I have to quit and restart to fix it.
That said, you'll pry that app from my cold, dead fingers.
