bckr

The point isn’t that there are no good definitions. The point is that there are many definitions.

I also have a working definition of a microservice, which is that it is a functional part of a system which exposes its functionality to other parts of the system via HTTP. This works for my team.

In general, we shouldn’t fetishize any particular technology, idea, or phrase. If a term obfuscates more than it clarifies, it’s not very useful.

Anyone succeeding with agents in production? Other than cursor :)

This is fun. Some feedback:

- I didn’t notice that much difference between the levels of obnoxiousness. Essentially the higher levels seemed to be more confident but contain the same ideas.

- All of them are very short, which means there’s also not a lot of variety.

- it seems like the two topics in the generation prompt are “future riches” and “currently broke”. A greater diversity would be lovely. Spiritual BS, dating gurus, crypto, impossible startup ideas… these are a few obnoxious things I’d like to see.

Thanks and congrats on front page

I don’t write binaries, assembly, or C. If I don’t have to write an application, I’m okay with that.

I still have to write the requirements, design, and acceptance criteria.

I still have to gather the requirements from stakeholders, figure out why those will or will not work, provision infra, figure out how to glue said infra together, test and observe and debug the whole thing, get feedback from stakeholders…

I have plenty of other stuff to do.

And if you automate 99% of the above work?

Then the requirements are going to get 100Xed. Put all the bells and whistles in. Make it break the laws of physics. Make it never ever crash and always give incredibly detailed feedback to the end users. Make it beautiful and faster than thought itself.

I’m not worried about taking myself out of the loop.

Sure but is there an app I can talk to / work with? It seems they're a voice synthesis model company, not a chatbot app / tool company.

You would have to convince YouTube that 10 minute videos generate more revenue.

They’ve been tuning this beast for decades now.

Tabs are great for simple, project doc stuff like separating long running actions lists from meeting notes

Wikipedia says he’s a citizen.

I may give it a spin after finishing this project :)

Hmm, I want to add my own files. This is because in my workflow I often turn to the web UI in order to get a fresh context.

I do like the idea of letting the model ask for source code.

It’s all about attention / context.

I’ve almost finished an interactive file selector inspired by git add interactive, with the addition of a tree display.

I’m giving myself the option to output collated code to a file, or copy it to clipboard, or just hold onto it for the next prompt.

I know aider does this stuff, but because I’m automating my own workflow, it’s worth doing it myself.

I’ve been playing with it and I don’t like it that much? I’m not sure why. It feels a little buggy and like it’s doing too much.

Today I decided that what I need is:

- prompt from command line directly to Claude

- suggestions dumped into a file under ./tmp/ (ignored by git)

- iterate on those files

- shuttle test results over to Claude

Getting those files merged with the source files is also important, but I’m not confident in a better way than copy-pasting at this point.

If it were me, I would write the code, commit it, and open the PR Monday afternoon

Not today or tomorrow, but next month, when one of them has started a cool startup, another is VP at her friend’s company, and the rockstar made it into Big Co

Consider helping make such a thing!

Well, make them fire you, so that you get severance. And keep a papertrail documenting how you were told over and over to do things that made no sense to the company’s bottom line.

A good phrase to remember is “outcomes over outputs”

Is it a prompt trick?

Yes, but TFA starts with questioning whether women knew about insertion.

The point is there are multiple "natural prices" that the market price may gravitate around. If Adam Smith thinks there's only one "natural price", then he's wrong, and you probably want to read with that idea in mind.

You can find pretty much any dance event in the bay at 19hz.info

I mean "be known by people, specifically people who know you as trustworthy, likable, and intelligent, and who might be able to help you get a job".

If any students or aspiring career-switchers are paying attention, now is a great time to start 10Xing your networking game. Stand out by being known.

I don’t think this implies it can’t be the right tool for the job, even when everyone on the team is a good programmer.

I don’t think it implies that you can’t write good programs in it.

I wondered. How dark.

Oh, this is very sad. I was really inspired by his essays and stories when I was 17.

I wonder what was happening with him.

Is your working definition of a computer scientist similar to a civil or electrical engineer?

To me, a computer scientist is someone who studies computation. They probably have the skills to figure out the run times of algorithms, and probably develop algorithms for solving arbitrary problems.

A software engineer is what I would call someone who can estimate and deliver a large software application fit for purpose.

> and a service that can’t tolerate any downtime is (theoretically) a service that is worth a lot to a lot of people- which is perfect for monetizing.

The connection makes sense but one must not think in this order. One must think “people will pay for this” and then consider “does this need to be highly available?”

If you have more than one road to choose from, and one of them doesn’t require high availability, then give that one some bonus points for that.

Government is a good one. Healthcare is another. Anything geography-locked.

I’m not saying no one should create a highly available web service. I am saying that this is one of those things that techies assume, and shouldn’t, because it’s a huge plus to hiring, business and engineering simplification, and morale if you can define away non-business-hour problems.