AI is cool. AI research is valuable. AI has the power to be a transformative technology.

Corporate AI hype for tech fueled neofeudalism is not cool. Commodification of AI is not valuable. LLMs will never substantively change the world.

If your love letter isn’t given in the form of highly obfuscated C, is it really a love letter? I don’t know, but what I do know is that I love you! <3

This whole message reads like “we don’t actually care but we have to say that we do 😉🙂‍↕️”

Replace cops with tweens

Vector embeddings with ChromaDB. Basically you pre compute the word embeddings of every row / table / whatever granularity you want and then stick that into a vector DB. Then you do an embedding computation of your query and compare similarity. You can either return the table / row / whatever you want that’s most similar (“semantic search”) or you use that as context for an LLM (“RAG”)

You can write anything in anything. The downsides have to be outweighed by the positives and OP is suggesting there isn’t enough positive.

That’s too bad, I feel like mastering C is the key to having a super solid foundation for all things how computers work. (Not blaming you, most courses just blast through C without exploring the what and whys). There is something to be said for just getting people productive and for that Python is excellent and immediately engaging. Python is probably my best and favorite language, but I think from a wholistic understanding point of view its hard to beat a solid C foundation to build out from.

My opinion, hopefully I don’t get downvoted into oblivion lol: Rust is great for lots of things and its to be commended for forward thinking on so many neglected areas of software development from the last 20 years. I use it almost every day for hobby stuff and have used it from time to time professionally (among Java, python, typescript, c++).

That being said amongst many of its users it has an almost cult like belief in its supremacy and imho attracts some bad people (not all). Because of how much it protects you, many bad developers find it and fall it love with it because it forces them to code correctly and then they can’t imagine that anybody else doesn’t need the guard rails they do. They also see that some of the smartest and best developments in software engineering happen in this space and want to attach themselves to it, and then use it as a bludgeon against others. Lots of very important software was written in languages that are not rust and they work just fine, were able to meet deadlines / be profitable Etc etc. but there is this attitude from many that if you aren’t picking Rust these days what are you even doing???

Rust is great but it’s sometimes messy and not the right tool for the job. The whole “slower to develop but faster to correct” (which I’d say needs some real data to prove out, but for the sake of argument let’s say is true) is a trade off, not something that automatically makes it better. Sometimes due to circumstances way beyond your own control as a developer, you won’t know what the right answer is until halfway into development and there are languages that accommodate that scenario much better (imo). This is one of many of rust’s short comings. For a website, it’s just an unusual tool that even if equally useful from a language standpoint doesn’t have as much tooling and community support around it as other web languages. But I’d say it’s not equal even from a baseline level (again, my opinion. I’ve used rust plenty but I’ve never used it for web dev so I’m talking out my butt). Philosophically, does it make sense to over engineer a super powerful Ferrari of a website when a Toyota Camry will do? Especially when the Camry is tried and true and will likely let you be more agile.

You can do anything in any language, but should you?

Did they test the sea floor? Some of it sinks. The concern isn’t radioactive seawater, it’s seabed accumulation working its way into the food chain

I don’t really know what to make of this article.

1. Bosses != executives / people in charge of making return to work decisions. Is there remorse from the people who were actually responsible for the return to work decision-making? or is it middle management who didn’t really want to come back either expressing their lack of satisfaction how “corporate” executed?
2. If it really is an ineffective policy It’s never too late to admit your mistake and pivot. If you aren’t doing that, then what is this besides lip service?

I don’t know if this is really the case but it comes across a little as “ah shucks sorry we didn’t do so great with all that… oh well too late now, bygones and whatnot, get back to work.” You aren’t absolved lol every day the policy continues its an endorsement that its what you continue to want

The real prions were the cognito hazards we fell into along the way

My hot take is that unmaintainable monoliths result from poor system design / too strong coupling. If you can’t cleave off portions of your monolith without breaking it you built it wrong in the first place, and the choice between monolith and microservice isn’t going to save you. Perhaps starting with a microservice forces people to make (or at least consider) better design choices from the beginning but 1. there is no reason you can’t make those same architectural decisions with a monolith and 2. you can still strongly couple microservices with poor design.

Getting back to basics of “what makes for good application development” using good abstractions, Go4 patterns, SOLID / KISS / DRY / etc, means that whether your threads are running colocated vs on another VM vs on another box vs in another datacenter vs in another continent shouldn’t affect you much. If your app breaks in ways beyond “I wonder if moving this job to another system means we’ll suffer from memory nonlocality or sync latency” the walls are already closing in lol.

Never seen so much truth in one article. 90% of applications would be fine as small VMs running monoliths. Dev time is an expensive resource compared to VMs and the simplicity promised just isn’t there. And having tech companies that run the major cloud platforms also be the software evangelists that herald “the new best way” of doing development was always a conflict of interest.

That being said, FaaS is nonetheless a useful tool in the toolbelt for the odd app that does actually need crazy scale to 1000000 scale back to 0, or for certain kinds of simple apps. Traditional app development still rules the middle space when it comes to team productivity.

The changes:

Intel® APX doubles the number of general-purpose registers (GPRs) from 16 to 32. This allows the compiler to keep more values in registers; as a result, APX-compiled code contains 10% fewer loads and more than 20% fewer stores than the same code compiled for an Intel® 64 baseline.2 Register accesses are not only faster, but they also consume significantly less dynamic power than complex load and store operations.

Intel® APX adds conditional forms of load, store, and compare/test instructions, and it also adds an option for the compiler to suppress the status flags writes of common instructions. These enhancements expand the applicability of if-conversion to much larger code regions, cutting down on the number of branches that may incur misprediction penalties. All these conditional ISA improvements are implemented via EVEX prefix extensions of existing legacy instructions.

1. Primaries
2. Politicians don’t care because the general population doesn’t care. Guarantee if it was on the top of the list of peoples concerns even the corporate shills of the main parties would give it more than just lip service. but climate change didn’t even crack the top 10 voter issue concerns in 2022 midterms (it was 14th)

It’s possible to both think those companies should be regulated and that people are doing almost nothing personally to help, including electing people to enact those policies. For most people I talk to the “but 100 corps” is a total deflection of personal responsibility. This crisis will not be solved without a good heaping helping of both personal responsibility and aggressive government regulation. If nothing else because that aggressive regulation will never pass into law unless people acknowledge their personal responsibility and are willing to accept the sacrifices that will come with it.

This is why I wasn’t too critical of Java. Java is verbose by convention and other languages are more terse by convention. You could just as easily write some nasty ‘snake_cased_object_abstract_factory_adapter_facade_broker_manager’ in python or any other language. There are a few things syntax wise working against it but you can still write (overly) terse Java and it’s just as annoying to read as in any other language. IMO it’s convention and style not the language itself. You can also say some mean things about languages with less verbosity but more operators and keywords like C++/rust. It’s a funny meme tho lol anyone who has worked in Java knows there’s at least a bit of truth to it

The joke is Java is verbose. It takes many characters to accomplish simple routines. Depending on your view that could either be good or bad for reading the code later.

oops

Not that I necessarily endorse it but from what I understand it’s low bandwidth mesh network so that Ring doorbells and such can piggy back on a neighbor if they have connection issues, not like how xfinity decides Your Wi-Fi is Our Wi-Fi