Interesting outcome of Saturday's game -- most of the Yankee's runs came as a result of their 9 homers, and they let up 9 runs -- which, defensively, is not great. The Brewers scored an average 4.78 runs per game in 2024.
Kinda suggests the Yankees aren't all great at playing baseball, except for hitting home runs, but that's all that really matters.
The defense in that game was pretty bad. Five of the nine Brewers runs scored due to errors, and it was five separate errors. The game yesterday went much better, defensively.
Since these guys are mostly targeting non-defense discretionary spending, cutting 15% of the federal budget means cutting literally everything.
I’d guess lots of people don’t actually want the entire government minus the military, social security, and medicaid eliminated, whether they admit it (or realize it) or not. Like the FDIC is pretty nice.
Also non-defense discretionary funding has not actually increased that much in recent years. There was a spike in 2020 due to COVID, but it has returned to pre-covid levels.
I don't know anything about the FDIC being eliminated. I see a lot of unnecessary overseas spending getting eliminated. I see a ton of real estate getting eliminated.
$130B added up real quick and it's only been a month. You can see the "Wall of Receipts" here, which is updated about every 2 weeks (in my personal experience) https://doge.gov/savings
Looking at next I have to think that something went horribly wrong with front end development. It adds so much complexity for things that provide such minimal value to most apps.
React added a lot of complexity to the front end, but, for an app with a lot of front end state, brought a ton of value.
Next brings us file based routing, which seems cool, until you get into any sort of mildly complex use case, and — if your careful and don’t fuck it up, server side rendering, which I guess is cool, if you’re building an e-commerce product and is maybe cool for maybe a few other verticals?
> React added a lot of complexity to the front end,
I keep hearing this but I disagree completely. Does no one remember Angular.js? Backbone? Ember.js? Even my favorite framework, Knockout, had lots of complexity.
SSR has been misused widely for years and we’re now starting to see the effects of that. But there ARE great use cases for SSR.
And frontend dev is the easiest it’s ever been. Run Vite Create and you have a fully working React SPA that can deployed in minutes on Render.com. No more messing with Webpack, or Bower, or Brocolli, or Gulp or Grunt or whatever madness came before. Frontend dev is in the best place it’s been in years.
> I keep hearing this but I disagree completely. Does no one remember Angular.js? Backbone? Ember.js? Even my favorite framework, Knockout, had lots of complexity.
You're using a different frame of reference. Those people you're referring to, including gp, probably mean that frameworks add complexity to the frontend. That would include all the ones you listed.
Okay, so go before that the jQuery (should win the Nobel Peace Prize) used with vanilla JS building absolutely bonkers custom scripts all over the place.
React was a paradigm shift towards more complex frontend apps, but there was still complexity. It replaced a bunch of .erb or mustache or whatever templating that then tried to be interactive with JS layered on.
What React replaced was not less complex overall, though technically I guess it moved more of the functionality to the frontend.
I don't think people like GP are arguing that there is no place for these frameworks. the argument is that there are too many people just using these frameworks in projects where it may not be needed and blindly running "npm create react-app" or whatever. Then you add something like NextJS on top which makes things even worse.
I would argue that majority of NextJS projects are not needed to be built in NextJS but could do with simpler front end JS.
And Next itself is abandoning all reason, like implementing redirects that break if you catch exceptions (because they're exceptions) and server actions that silently fail if a network issue occurs.
Hmm. I haven’t used Remix but I’ve avoided it for exactly the same reason, that I might become a victim of their latest business model.
They got their start way back with React-Router. At the time, their business was React Training. They’d train people how to use React. React Router had this curious tendency to change its API drastically with each release. Stuff you depended on would suddenly go away, and you’d be told “That’s not the right way to build apps anymore. This is the True Way.” It really sucked, but it seemed like a good way to drive demand for training.
Then they came up with Remix. Remix has been pretty stable, but when looking at React Router, I kept noticing there was stuff that felt more like an app framework than a router. It felt like it’s pulling me into Remix. Then last year they announced that they’re merging Remix and React Router. So if I was already dependent on React Router, I’d be fully committed to Remix, whether I wanted to be or not.
What new shiny thing or new business model will they be chasing next year? I’m not willing to risk finding out.
And do they only watch science shows teaching STEM subjects? Or do they get to watch shows that have some emotional lessons as well? If so, what shows?
I think people are reacting because Bill Nye is not even remotely in the same category. It has a different kind of value, and frankly it’s not as important as the kind of value kids get from Bluey.
It’s very nice if kids learn science. Great even. But the most important things kid can get from TV shows (if anything, it’s okay to watch things for fun as well) is to learn social skills. Bluey has a lot of that, and it does it without being annoying about it like Daniel Tiger. It’s a good balance
Yeah, in my experience, most companies who are going to 1) do business with early stage startups and 2) want SOC2 report, are going to be totally fine with writing “startup X will get their SOC2 type 1 in the next six months” into the contract and moving forward, so long as someone technical can get on the phone with their IT people convince them you are reasonably competent.
Counter point: I just spent $1 and 25 minutes to try and have Claude Code figure out why a relatively simple test was failing. It repeatedly told me incorrect things about the basic functioning of the code, and ended with "Try adding debug logging in your code to see what's happening in that specific check, or look at the exact error message from the failing test."
What’s that old (and in my experience pretty accurate) adage? The last 10% of a software project takes 90% of the time?
In my experience, AI is helpful for that first 90% — when the codebase is pretty simple, and all of the weird business logic edge cases haven’t crept in. In the last 10%(as well as most “legacy” codebases), it seems to have a lot trouble understanding enough to generate helpful output at more than a basic level.
Furthermore, if you’re not deliberate with your AI usage, it really gets you into “this code is too complicated for the AI to be much help with” territory a lot faster.
I’d imagine this is part of why we’re not seeing an explosion of software productivity.
This is my experience as well. There are a couple things I love using AI for, like learning new programming languages or technologies (I consider myself an expert in Java and NodeJS, and proficient in Python, but I recently took a job where I had to program in an unfamiliar language), and it's been great for programming up short little "apps" for me for things I want - I've built a slew of browser apps for myself that just save stuff to local storage so that I can easily put it up on GitHub pages (and then I create import and export functions if I switch browsers - export just opens a mailto link where the body just contains a link with the state as a param, so then I just save that email, open it up on a different device and click on the link).
But I've found that there are a lot of places where it kind of falls over. I recently had Cursor do a large "refactoring" for me, and I was impressed with the process it went through, but at the end of the day I still had to review it all, it missed a couple places, and worse, it undid a bug fix that I put in (the bug was previously created when I had AI write a short function for me).
The other thing the makes me really worried is that AI makes it easy to be lazy and add tons of boilerplate code, where in the old world if I had to do it all manually I would definitely have DRY-ed stuff up. So it makes my life immediately easier, but the next guy now is going to have a shit ton more code to look at when they try to understand the project in the first place. AI definitely can help with that understanding/summarization, but a lot of times I feel like code maintenance is a lot of finding that "needle in a haystack", and AI makes it easy to add a shit ton of hay without a second thought.
Yeah, I've been disappointed in a lot of code generation within my field of expertise. However, if I need to whip up some bash scripts, AI works very well. But if I want those bash scripts to be actually good, AI just can't get there. It certainly cannot "think outside the box" and deliver anything close to novel or even elegant (although it may give some tactical help writing boilerplate lightly adapted to your codebase). The analogy I use is that LLM AIs are like a new car mechanic tool that can generate any nut, bolt or gasket, for free and instantly (just add electricity!). It's great addition to the toolset for a seasoned mechanic, distracting for a junior, and is not even in the same universe required to fix an entire car, let alone design one.
Yesterday, Trump announced he was killing congestion pricing in New York City. A program set up by the state of New York, to help fund infrastructure in New York.
Seems like an issue that should be left to the state, and yet here they are asserting federal authority over it.
I’m not that familiar with US politics but I read that this was more a symbolic move and he actually can’t influence this law since as you pointed out it’s a matter of the New York state. He can announce things all day, which is exactly the strategy - do at least 5 ridiculous things every day and the media/people can’t react fast enough — bury them in shit
He is just a tell is how enablers made all these people sound innocent and their detractors crazy. At this point I believe it was often deliberate strategy. Plus crazy paranoid were actually 100% correct over years.
Like many things in US politics, “it’s complicated.” The program had to get approval from the federal government (which was granted by the Biden administration), it’s now up to the courts if Trump can rescind that approval.
The point is that saying power should go back to the states is really just a talking point conservatives use when it’s convenient for them, not actually a strongheld belief that guides their actions in any way.
One key thing that I found when learning to code mostly from actual books and online tutorials (well before AI), was to always re-type the code examples by hand instead of just reading them or copy-pasting them. If just reading the code is always miss a bunch of details, that id see when retyping.
I tend to do the same thing when using AI to explore something at edge of my knowledge, where I don’t know exactly what I just asked the AI to code. I ask it how to solve a general problem of the class I’m trying to solve, and the retype that code as I’m fitting it into my specific use case. I find that helps me much better understand what the AI generated code is doing, which comes in handy when it doesn’t work as described or goes wrong.
Kinda suggests the Yankees aren't all great at playing baseball, except for hitting home runs, but that's all that really matters.
reply