9,141 karma · joined April 28, 2021
At the end of the day, if your writing is meant to be read by others then using an LLM is a violation of the social contract between you and your audience.
It really bothers me that people think it's ok to use AI as the starting point for writing. In my mind, it's the worst thing you can do. It poisons the entire effort, and frankly it's disrespectful to give it to anyone to read. Stop doing it!
Fundamental to exchanging ideas is discovering which ideas should be exchanged and how to express them. The process of writing itself is that exercise. If you use a tool to outsource the thinking then you're not thinking.
It only works by having more capital to begin with.
Otherwise you wouldn't see consolidation where it shouldn't exist.
The biggest moat is capital.
PE is buying up things like medical practices, law firms, vets, etc, where typically there would be an upwards path for one generation to hire new blood to cover their markets and then sell partnership stakes to them when they want to retire. But why should an owner of a practice sell to their junior staff when PE is there offering 2, 3, 5x as much?
Consolidation of these kinds of businesses at the hands of PE is endemic of systemic lack of capital acquisition of a generation of people, held down by debt and concerns about practical shit like healthcare.
PE is just a symptom of larger macro economic trends, namely the depletion of the next generation from free cash they could use to become business owners.
It doesn't fix the actual problems with C++, which is that it's significantly more difficult to get and use external dependencies because of the compilation and linkage model of C++ libraries.
If C++ were as easy to build and link as modern programming languages you'd see the same kinds of tools as cargo, and the same kinds of ecosystem evolution as rust, like tokio. But you don't, because C++ code sucks to build, package, distribute, update, and reuse.
(I'm aware/have used conan/meson/vcpkg/etc - doesn't change my opinion).
But honestly that's a mischaracterization of the situation in Rust. Tokio is popular for networked service backends. If that's the wheelhouse you're in then yea it might look "dominant."
It's worth pointing out though that just tracing function calls isn't good enough for the kinds of stackless coroutines that run in async Rust tasks. You need a way of mapping between the async tasks and the compiler emitted traces.
afaik, C/C++ have the same problem.
> the idea of a modern dumb TV is non-existent.
They're sold as commercial display panels/digital signage and because they're a business product that isn't subsidized by advertising/spyware they cost a good bit more. But the panels and controls are basically identical to high end TVs.
This is just noise generation. If anyone is meant to actually read the document it should be written by you.
The transition from absolute to relative pitch is like moving from basic arithmetic to algebra, once it clicks. Except that relative pitch is way easier to understand without notation, pick a reference and go from there.
Interestingly this is a strong thing to fight because there are pieces of music that are physically inaccessible to many players, particularly people with hands not wide enough for the intervals. No amount of practice or stretching can overcome it and you can't exactly travel with a piano or keyboard everywhere.
There some cool things like the Janko keyboard that seem strictly superior to the traditional 12 keys but it's kind of an uphill fight to build conversion kits cheap and light and good enough to travel and perform with.
Changing a segfault to a panic with a stack trace is an improvement in developer experience. It does not make better software. The advantage of automatic strategies to mitigate memory safety mistakes either by using GC to make the program sound or static analysis to prevent the mistake by construction is plainly better.
There is a direction in some systems programming circles away from this by eschewing "complexity" (in other words, fixing the damn problems) for programs that have better error messages when the programmer made a mistake. I don't see that as better software.
This is literally our job as software developers. If this expectation is unreasonable to you then you do not belong anywhere near software development.
Because I've lived in a few of the largest urban areas and the answer is "nowhere near the jobs."
It absolutely does not but people keep repeating this on social media