I believe that the standard word for this is "radical", but standard use is sloppy enough that it's reasonable to seek a clearer term. I also think that "knee-jerk" may capture the quick reflexive nature you're thinking of.
My preference is to use the build system to create built artifacts, and I consider the build/ directory to be a built artifact. Wrangling Git into doing the first fundamental build step is off, in my opinion.
However, if you disagree, my favorite "Git keep" filename is "README.md". Why is this otherwise empty directory here, how does it fit into my source tree, how is it populated, and so forth.
One of my pet peeves with the latest AI wave is the time we spend creating files to help AI coding agents, but don't give the same consideration to the humans who have to maintain and update our code.
It's just American custom to exclude some taxes from the posted price. Many countries include all taxes in the price, something I've always wished we would do in America. After that, I'd love to see the elimination of the custom of always ending fuel cost per gallon in 9/10 of a cent.
This seems oddly complex to me. We have a family domain that hosts our personal email addresses. In addition, we have a "family@" address that just forwards to my wife and me. Usage is obvious to everyone, no need to explain anything. Joint emails are obvious, replies work as expected, individual emails have obvious recipients.
If you have a problem that requires and hour or a day to compute, then spending fifteen minutes for data transfer up and down (particularly in the face of lowered costs) is often a profitable trade. Movie studio render farms are a classic example of such compute jobs. Weather or geological resource prediction could be another. There are many such high-compute jobs in practice.
To each their own, but to me the only key easier to hit than the Escape key is the space bar, and returning to the home row is like a 20ms move. On the other hand, if you're actually using control keys in the (now standard) lower left and lower positions, then we're just on different planets. :)
By performing computations directly inside memory cells, CRAM will dramatically reduce power demands for AI workloads. Scientists claim it's a solution to AI's huge energy consumption.
Seems like that would depend on your job. Are you a line cook? Actuary? Electrician, barber, power systems controls engineer, nurse, technical writer, programmer, financial advisor, program manager, creative director, level designer, wing systems engineer, welder, pilot, detective, bouncer, film editor, bartender, appliance line worker, landscaper, civil engineer, residential construction foreman, HVAC technician, … ?
One of the most significant aspects of this issue is too often ignored. Inevitably, people focus on the _location_ aspect of this topic, and its impacts. Equally significant in my experience is the fact that my workspace at home is significantly superior to the toy office at work. Work offices have been undergoing constant degradation for decades now. Today, an "office" is too frequently a randomly-assigned tiny surface with cheap-as-possible computer & peripherals, in a loud space, from which I interact with team members over video.
Imagine being a machinist where you get barely serviceable tools at work, versus a fully-equipped custom workshop at home. For me, this isn't about Covid and recent events — it's the end state of a work environment that has seen decades of dismantling.
Ugh. Went through the whole questionnaire, only to be told at the end that I could get the results only by giving them my email address. Coupled with my birthdate, gender and zip code.