abakker

All the proposals I’ve seen would set the marginal tax rate on the 120 so high that his earnings would end up more like 40k from the 120k job and then he gets his 60. So, still some benefit to working, but a very progressive tax rate on higher earnings. Not sure I agree with this, but that is what I’ve seen.

But, have you any code that has been vetted and verified to see if this approach works? This whole Agentic code quality claim is an assertion, but where is the literal proof?

It registered in the low 40s for me, while my watch was saying 72-75. I guess YMMV

If you add baking powder and butter, that dark breakfast recipe is very close to crepes.

My crepe recipe - cook on medium heat pan:

Blend on low: 4 eggs- 3/4 cup whole milk, 1/2 stick of melted butter, and 1/4cup to 1/2 cup plain flower, 1 heaped tbsp of baking powder, 1/2 tsp salt, vanilla optional and to taste

And bought a house from Epstein for $10

Great to see your name here, Zack. I think the problem with low-code is that its a catch all that spans between primarily data-storage-and-use work (Airtable, quick base, Filemaker, etc), the primarily app-alternative platforms (retool, Mendix, etc, and the ETL tools.

To me, AI changes the inflection points of build vs buy a bit for app platforms, but not as much for the other two. Ultimately, AI becomes a huge consumer of the data coming from impromptu databases, and becomes useful when it connects to other platforms (I think this is why there is so much excitement around n8n, but also why Salesforce bought informatica).

Maybe low-code as a category dies, but just because it is easier for LLMs to produce working code, doesn't make me any more willing to set up a runtime, environment, or other details of actually getting that code to run. I think there's still a big opportunity to make running the code nice and easy, and that opportunity gets bigger if the barriers to writing code come down.

People don't respect the salary premium software developers have received and expect relative to other creative, human endeavors.

You lay it out perfectly in your answer, and I'll add that the entire non-tech world generally feels that if tech jobs lose their shine due to AI, its actually a welcome reversion to the mean. Software has likely depressed wage growth in many other jobs.

That perfectly ties with my experience. Just direct prompts, with limited setup and limited context seem to work better or just as well as complex custom GPTs. There are not just diminishing, but inverting returns to complexity in GPTs

Graphically, I really like the way autodesk makes sketches in fusion 360 blue until they are fully constrained, and then they are black. My intuition here is that you could color code “degrees of freedom” and “locked” states so that it was more intuitive.

and, its so cheap. there are alternatives for individual components, but nothing that comes close to being this low cost. And, the ultimate value is that if you buy a niche tool (like notion) then only people with licenses can use it. Everybody at the company has office, so it's easy to share/collaborate. You have to really commit to avoiding office at all if you're going to replace parts of it.

0% NET accretive profit - the OP was saying that the invest/return wash doesn't affect prior profitability, just revenue. Obviously, the new profitability inclusive of the new revenue will actually by lower because of the zero margin wash trade.

I think he was getting at the fact that the Truth is not good news to everyone.

Welll, if you were good at drywall already, drywall patches would be faster and better. But if you are good at printing and scanning, and you enjoy that process, then it’s fine.

The challenge with the example is that “success” is personal preference. With plenty of examples, the success criteria are external.

My only addition to this discussion is that the Dirty Labs dish soap has been legitimately better for our baby stuff and other plastic stuff that sometimes gets oily. I recommend it.

And, for a refrigerator and a lot of loads, being down for 2 days straight is way worse than a few hours a year. losing 48 hours of supply a year if broken into 2 hour chunks is not nearly as bad as losing 48 consecutive hours.

I mean, even back in the OnStar days, you could "opt out" and cancel the service and it would track you anyway. With BYD or any other car maker, I'd be worried the SIM was a placebo.

and then the code to give it context. AFAIU, there is a lot of post training "setup" in the context and variables to get the trained model to "behave as we instruct it to"

Am I wrong about this?

my intuition is that over smoothish, but hilly terrain, mountain bikes fare very well, too, since you get to go downhill for free. once you end up in a talus field, I think it becomes clear that "efficiency" is gone for basically any creature on land.

I'll say, I recommend my Honeywell sync earmuffs for the workshop. They block more noise, have a physical volume knob and accessible buttons, and best of all, the microphone is also noise cancelling directly, meaning you can usually have a conversation with someone while using a power tool or mowing the lawn without much issue. APP2 or 3 for me has never been able to displace these.

I’ll just say that most of the core issues with heat pumps seems to resolved with monoblock designs. Specifically, by moving the refrigerant cycle outdoors, install can be cheaper, and capacity can be more variable than when you are relying on sizing to the phase change occurring in each indoor unit.

I have no basis for this, but I think this is also based on personal genetics or similar. Most of the bites I get seem to create no bumps or itchiness at all. When i was a kid, that wasn't the same, but now in my late 30s it seems to no phase me.

A shortage exists at a point in time, propensity to pay to make the asset may react to the demand for the asset, but there is no guarantee that supply of labor and capital meet at an efficient point. (art is a great example where the overlap between supply and demand may have no overlap at all for certain pieces).

Lack of demand for labor and skill can produce an asset shortage, but in an economy where supply and demand float, the theory is that shortages reflect supply-demand failures, and the degree to which supply of labor is invoked to solve shortages for goods depends on the elasticity of demand and the elasticity of supply.

I don't think this is correct. The reasons economists separate capital and labor is that they do have different characteristics. Labor has skill, capital can have technology. Assets exist regardless of utilization, labor cannot be stored up in an inventory since labor is time which flows inexorably onwards.

A shortage of an asset is a reflection of inventory levels. A shortage of labor reflects a lack of skill or time OR a lack of willingness to pay for that skill and time.

They're different for good reasons.

15min is certainly needed for some shapes in Boulder, even the loss of a few degrees seems to matter a lot.

I agree...but I also think it's a slow path to monetize OpenAI if they don't support some kind of channel to get paid by the sell-side. At least they offer a subscription and didn't jump to this as the only option. I'm optimistic that a premium tier can exist that avoids this, but we'll see. The reality is that they need the money.

As an aside, I think you could get a smart plug that would support a 15 amp load that could give you a notification if the load went away. Might not be perfect, but just reading about having a relationship with a washing machine in a theoretical, second-party kind of sense makes me angry :)

I think the idea is that explicit protections might encourage whistle-blowing. Especially since the domain is nascent enough that it's not clear what you'd blow the whistle on that might be unique to the companies that make foundation models. In many cases, there will be whistleblowers who both disclose what is being fed into models, but also details in aggregate about what users of models can do.

It's a great point. If you are interested, the book "why we make things, and why it matters" really resonated with me for this exact reason.

it is very difficult to determine this. Companies that do h1Bs are all multinational, so they can locate dev offshore and just say they did it internally. There's also the reality that even if you go out and try to evaluate the revenue that comes from IT, you basically can't get clean attribution even if you want to. many H1Bs are not working on customer facing product, but internal projects and that makes treating things like application maintenance or service desk pretty difficult to calculate for ultimate revenue outcome.

Usually only the selling part. At which they have historically excelled.