I do this as well and, anecdotally, I do get better results this way and better than my coworkers who are more terse and explicit. The conversations can become a bit sprawling though, so I also aggressively clear context
This statement is definitely just marketing hype, but if we're being pedantic there are tons of questions that are hard to answer but have easy to verify solutions, e.g. all NP-complete problems.
No. I also wouldn’t use a hammer to cut a board in half - I’d grab a saw. Knowing how to pick the right tool is a fundamental part of being a good engineer. Sometimes 70% is unacceptable, sometimes it’s exceptional. LLMs are incredible technology, but also just another tool in the toolbox. Use them where they fit, not where they don’t.
It might not fit your work, but there are tons of areas where “good enough” can still provide a lot of value. I’m sure you’d be thrilled with a tool that could correctly tell you if Apple’s stock was going up or down tomorrow 70% of the time.
While Australia does take things too far, I’m actually on their side here. Driving has been too normalized. You’re operating a 2 ton chunk of metal at 60+ mph inches away from other people. Australia has far fewer pedestrian deaths per capita than the US does, and enforcing a higher skill bar for more difficult situations must be part of that.
I wonder if there’s a combined metric that could be calculated. Depth of the line certainly would be impactful. A line that only works if you do 5 only moves is harder to find than a single move line. “Quiet” moves are probably harder to find than captures or direct attacks. Backwards moves are famously tricky to spot. Etc
Whatever you know best and can set up quickly and easily. It's very easy as an engineer to focus too much on the tech and not enough on the product. Don't agonize over postgres or Dyanamo DB, Django or Spring, just use what you know to get it set up and focus on product, market, customers, sales, etc. Those will be the hard part.
There's a version of the problem that tries to highlight this:
A runaway trolley is heading down the tracks toward five workers who will all be killed if the trolley proceeds on its present course. Next to you is a stranger who happens to be very large. The only way to save the lives of the five workers is to push this stranger onto the tracks where his large body will stop the trolley. The stranger will die if you do this, but the five workers will be saved.
Does the act of physically pushing a person onto the tracks make it different than pulling a lever?
Accessing public pages is exactly what weev was tried for. He found you could iterate the id argument on a public url to expose email addresses. He was sentenced to 41 months in federal prison
I've been taking some classes online through quarantine, and have really enjoyed taking notes with Obsidian.
As I review old notes, I often put parts of class notes into dedicated notes of their own, and the end result is a list of links to the topics covered, example problems worked out, and a bit of extra descriptive color relevant to that specific lecture.
90% of the time, Sheets's recommended graph is exactly what I wanted, and is in general a much cleaner and enjoyable experience than Excel. Pivot tables too are much more obvious and usable to non-power users in Sheets than Excel