nosefurhairdo

It's not good, they hide the model (their whole thing is hidden model routing to keep costs low, but predictably yields bad results), there are no novel integrations not available in any other harness, it's closed source, and bobcoin is worthless because it's only usable with Bob.

Official policy is to only use Bob. All of the best people I work with are using other tools because Bob is trash.

Seems unlikely. We're already seeing specialized hardware optimized for LLM performance (taalas, groq, cerebras), and simple economies of scale result in these sorts of products being a better value when rented from a server vs purchased/managed/upgraded for the typical the user.

Frontier models will continue to be either exclusively available from servers or significantly more affordable from servers vs local alternatives for the foreseeable future.

I dealt with eye strain that would bother me for hours after I stopped working. Improving the lighting around my desk basically solved it for me.

I give my agents read permissions to all repos related to a given repo. Add a bit of context to AGENTS.md or equivalent and they do just fine with understanding service boundaries.

Another concept I like is that we should optimize for next year's AI. Don't migrate to a monorepo if your only motivation is the performance of today's agents, because a year from now this may be a non-issue. Of course other motivations may still be valid.

React + ReactDOM adds ~50kb to a production bundle, not even close to a couple of mbs. React with any popular routing library also makes it trivial to lazy load js per route, so even with a huge application your initial js payload stays small. I ship React apps with a total prod bundle size of ~5mb, but on initial load only require ~100kb.

The idea that React is inherently slow is totally ignorant. I'm sympathetic to the argument that many apps built with React are slow (though I've not seen data to back this up), or that you as a developer don't enjoy writing React, but it's a perfectly fine choice for writing performant web UI if you're even remotely competent at frontend development.

AI is great at any styling solution via system prompt + established patterns in codebase. Tailwind is just slightly more convenient since it's consistent and very popular.

Arthritis is a general term; need narrow down for useful advice on managing symptoms.

Two most common types are osteoarthritis (wear-and-tear associated with aging and/or injuries) and rheumatoid arthritis (autoimmune).

I only know about age-related knee osteoarthritis to try to help my mom manage her symptoms, so I'll share my understanding of treating that.

High ROI, low cost: - weight management. Extra lbs are extra stress on the knees, plus I suspect chronic inflammation associated with being overweight can exacerbate arthritis independent of mechanical stress. - exercise, specifically low impact cardio and any pain-free strength/hypertrophy work targeting the musculature around the knees (mainly quads).

Variable ROI, low cost: - NSAIDs, specifically topical to focus on treatment area and reduce impact on GI system/kidneys. - curcumin, mixed evidence but some people report benefits.

Variable ROI, high cost: - PRP injections. Apparently the quality on these varies dramatically by provider. Would recommend doing research and comparing multiple providers if possible. - Knee replacement. Far from a panacea; you'll lose range of motion forever, plus plenty of other trade-offs. Most people recommend putting this off for as long as possible.

Also interesting is low dose radiation treatment for knee OA. More affordable than other procedures and has some promising research.

Not much else on the novel treatment front that I've found. Curious if anyone thinks I've missed anything worthwhile.

I did not mean to suggest that our motives were purely humanitarian. As I understand it there are numerous geopolitical implications with Venezuela, from China's loans-for-oil relationship to the Iran assisted drone manufacturing facilities. And of course we'd like some of that oil, too.

I'm just not convinced that removing Maduro is some horrible violation of international law. As I said in my original comment, I'd be more sympathetic to the argument that the US has a horrible track record with regime change.

Regardless, given the geopolitical significance of Venezuela's relationships with China and Iran it is ignorant to suggest that "[only Venezuelans have] a standing in the matter." And the illegitimacy of Maduro's election is not a topic of serious debate as your phraseology might suggest. He stole the election, he's bad for Venezuelans, and he's good for our geopolitical rivals. It is yet to be revealed whether our intervention will be a net positive.

My read of your argument: international law says don't intervene in foreign government, and by intervening we legitimize future violence.

I'm not sure this argument makes sense. Maduro stole an election to force his way to dictatorship, is widely blamed for running the country into mass poverty, and continues to hold onto power through threat of violence. The Venezuelan people don't have any recourse here.

Also, in your example of Ukraine you indicate that Russia frames the uprising as a "US coup", suggesting that the reality of whether there even was external involvement isn't so important.

Even so, if some nation tried to use this strike on Venezuela as further justification for violence wouldn't they be violating the same international law you cite anyway?

Obviously the US has a rough track record of replacing foreign governments (a much stronger argument against this kind of act IMO), but so far this mission has looked pretty ideal (rapid capture of Maduro, minimal casualties, US forces instead of funding some rebel group). There is opportunity for a good ending if we can steward a legitimate election for Venezuela, assist with restoration of key institutions (legal, police, oil), and we avoid any deals regarding oil that are viewed as unfair by the Venezuelans.

I'm with a company that was acquired by IBM ~2.5 years ago. The internal systems are definitely rough, but for the most part it's business as usual.

I've heard chatter from our engineering leadership that IBM is trying to push some silly initiatives, but we've been able to prioritize the right work so far.

I also get more equity (one time award + employee stock purchase plan) than I did previously, and with how IBM stock has been performing lately this has been a net positive for me.

FWIW I have heard that IBM used to force their management style on acquisitions in years past, so perhaps this is a fairly recent shift towards a less hands-on approach.

"When a measure becomes a target, it ceases to be a good measure."

You are free to interpret the score within the broader context of your own experience, the problem domain your code addresses, time constraints, etc.

That's fine, but it shouldn't be enforced on all contributors. What matters is that failures don't get merged, not that they don't get committed.