You are exactly right. You are most likely not getting a pay cut just because your raise doesn't match inflation. It totally depends on how much of your money you are spending and what you are spending it on.
> According to a 2017 study, approximately 38% of all children will be investigated by CPS by the time they are 18.
This seems outrageously high. The study says it is an "estimate". I'm willing to be their methods or assumption are seriously flawed. Would be curious if someone has looked into it.
I'm also curious what it really means to have CPS called on you. People talk about it like it's a foregone conclusion that they'll take your kids away. I just can't believe they would do so lightly. Now of course even having to interact with them must be extremely stressful.
> People gatekeep actual work and save it for political favorites and everyone else on the outside is stuck cooking up bullshit projects. If you do manage to find work on your own, people will immediately start scheming to steal it
So this applies to even, say, mid-level developers? Wouldn't you get work assigned to you after you're hired, or do you actually have to hunt for your own projects, like you might in some consulting firms?
> or do you actually have to hunt for your own projects, like you might in some consulting firms?
This is how the company works on a fundamental level.
On healthy teams, having something assigned to you (for levels under staff/6) is normal. On unhealthy teams, you're just a sitting duck and it's better to find your own work. Or else you'll be forced to work on bullshit projects with no upside.
Side note: the "they" who does the assigning is not a manager, it's another IC. The ones that go out and find their own work. That could be at any level technically, but usually staff+ because they form little political mafias.
There's a lot of good ideas in Spring and there have been some outstanding engineers working on that framework over the past ~25 years. But it has accumulated so much baggage and relies on and perpetuates so many patterns that simply don't make sense anymore... I would love to see what the team would do with a fresh start. I wonder if they have or are considering doing a complete rewrite or starting something totally new for the next generation that will take us through the next 25 years of Java.
> Last weekend I tried building an iOS app for pet feeding reminders from scratch.
Just start smaller. I'm not sure why people try to jump immediately to creating an entire app when they haven't even gotten any net-positive results at all yet. Just start using it for small time saving activities and then you will naturally figure out how to gradually expand the scope of what you can use it for.
Regarding the window manager and Finder; I had a better experience with the Windows equivalents way back on Windows 2k or even Windows 98 more than quarter century ago. Truly baffling.
Yes, even the Windows 98 Explorer with IE integration (let's load a JPG of clouds to the left of the file detail pane) was better than modern equivalents. In Windows 10 (or was it 7?) they introduced a stupid column view in detail view that became focused with tab, so you couldn't just tab between the 3 places of directory list, file pane, address bar.
They also added stupid "quick launch" areas with places nobody went, like "3D Objects", and reduced the menu area to a "grope and find a button" ribbon.
The older Explorers were usable like File Manager on Windows 3.11 was: address bars that were usable from the keyboard and mouse (no subdivision buttons for parts of the path), acceptable launch speed, and no extra "features" that were unnecessary (like it ignoring "use same view for all folders" when your directory happens to have MP3s in it - it'll switch to showing rating / bitrate etc.)
I believe all developers should use older versions of the software to see how usable they were in comparison to the modern "improvement".
> Quantum computing-enhanced NMR could become a powerful tool in drug discovery, helping determine how potential medicines bind to their targets, or in materials science for characterizing the molecular structure of new materials like polymers, battery components or even the materials that comprise our quantum bits (qubits)
There is a section in the article about future real world application, but I feel like these articles about quantum "breakthroughs" are almost always deliberately packed with abstruse language. As a result I have no sense about whether these suggested real world applications are a few years away or 50+ years away. Does anyone?
> As a result I have no sense about whether these suggested real world applications are a few years away or 50+ years away. Does anyone?
not really. but that doesn't mean it's not worth striving for. Breakthrough to commercial application are notoriously hard to predict. The only way to find out is to keep pushing at the frontier.
> Can you imagine trying to talk to someone face to face, but they are giving you a blank stare as random notifications and tiktok videos are being beamed inbetween their eyeballs and you.
It would be just like in the Dungeon Crawler Carl books (and probably other scifi/fantasy books)
Agree... this is an important blog. People need to press pause on MCP in terms of adoption...it was simply not designed with a solid enough technical foundation that would make it suitable to be an industry standard. People are hyped about it, kind of like they were for LangChain and many other projects, but people are going to gradually (after diving into implementations) that it's not actually what they were looking for..It's basically a hack thrown together by a few people and there are tons of questionable decisions, with websockets being just one example of a big miss.
The Langchain repo is actually hilariously bad if you ever go read the source. I can't believe they raised money with that crap. Right place right time I guess.
Yeah agree. I spent a few hours looking at the langchain repo when it first hit the scene and could not for the life of me understand what value it actually provided. It (at least at the time) was just a series of wrappers and a few poorly thought through data structures. I could find almost no actual business logic.
I made an error trying with aws bedrock where I used "bedrock" instead of "bedrock-runtime".
The native library will give you an error back.
Langchain didn't try and do anything, just kept parsing the json and gave me a KeyError.
I was able to get a small fix, but was surprised they have no error like ConfigurationError that goes across all their backends at all.
The best I could get them to add was ValueError and worked with the devs to make the text somewhat useful.
But was pretty surprised, I'd expect a badly configured endpoint to be the kind of thing that happens when setting stuff up for the first time, relatively often.
reply