Because if you’re working on anything of note, you will need to sustain, scale, and operate that software while hopefully designing for it at a high level. LLMs are not suited for those problems, at least not anytime soon
I’m looking forward to when the job market recovers, but I’m not looking forward to the prospect of a significant amount of future demand being in the realm of having to scale and maintain the AI slop code that’s being generated now.
It sounds like a pretty lucrative retirement plan, no matter how boring and frustrating the actual work would be.
Sadly, I don't think companies are going to hire graybeards to maintain AI slop code. They're just going to release low-quality garbage, and the bar for what counts as good software will get lower and lower.
The "world" can just as easily be conceived of as being composed of discrete immutable facts rather than global mutable state. Either way, I kind of don't think that unfalsifiable ontological premises should be an important factor in system design.
While the world can tentatively be conceived to be like that, it is not nearly "just as easily". Lots of those "immutable facts" can't be realistically discovered: e.g. good luck recovering "this blackboard had a drawing of a cat and a bird until five minutes ago when it was cleared with a wet sponge" if you weren't there in time. The approach with mutable state fosters this destructible nature of many things upon you and makes you cope with it, somehow.
Ok, but why should I even care about what was on this hypothetical blackboard? Do you have any real world examples with business or technical significance where this "cope with it, somehow" approach to mutability is a clear win?
You've just stated it, no? If you only care what is on that blackboard right now, not what was there — why even bother storing knowledge about its previous states?
Ruby has RBS and sorbet to support using type annotations. They are each relatively new and aren’t as clean and well integrated as Python’s implementation, but it’s not as if type annotations in Ruby don’t exist.
It does exist but they are not embraced by the majority of the Ruby community.
Unless type annotations are treated like first class citizen in the language, it won't be good enough. My theory is that those in the community wanting static types went to Go or Rust.
Of course anything can be done with RBS, but I think it came wayyy too late. Python type system is already given time to evolve and survive in the wild.
A second point is IDE support. It is so hard to get started with ruby auto-format, code completion, ctrl-click to follow code and debug. Python is readily usable in pycharm community edition.
You're treating feminism as a simplistic monolith rather than a multifaceted movement across different cultural groups and sects. There are plenty of differing opinions and trends within the umbrella of feminism that don't always agree with one another, often the divisions seem to fall across generational and national boundaries. It seems to me though that feminists, and the left in general, in the US are very much in favor of the decriminalization of sex work.
The 'Start your free quiz' button currently is not working. Seems like there may have been an event handler at one point that is no longer functioning.
The majority of coins on Coinbase are in cold-storage and crypto on Coinbase is insured against this type of breach. I personally wouldn't panic to get my coins out.
I totally do this. I also occasionally will have something breaking and soon realize I typed 'git' randomly in the middle of a file instead of in my terminal...
I do stuff like because I alt-tab a lot and have so many similar-looking windows open. It's not just me either, I have seen stuff like "git pull" posted in chat rooms followed by "oops wrong window".
Using used parts might be twice as much labor for one thing, you have to remove the part carefully from one phone and then install it into another one. Another is that you can't always guarantee the repair is done well if it's done with used parts as you can't really be certain what kind of conditions they were subjected to over time. Also, as you have to charge less for used parts, you might not have as good of a margin on the repair. I don't work in phone repair, but I used to work as a bicycle mechanic, and sourcing used parts for repairs was generally not considered worthwhile in most shops I've worked in.
