lazy_afternoons

I have a separate repo which has to be pulled locally and the skills and agents are sym linked to projects.

I know it isn't the original flow state but I get lost in conversations with Claude even when slow.

I have a couple of terminals open and work on at max 3 things.

A main task, an exploration task and another prompt/skill improvement or documenting an issue (or a proposal)

A non technical domain expert might usually lack thought clarity. They might know what is right once they see it but they seldom know how to reach there, even with AI. They will write themselves into slop in 3 days.

The real moat I believe is the ability to hold the the problem in the head, isolate it and mentally design a way to structurally solve it iteratively.

Very few people have it. Much less common with domain experts.

I would rather bet on educating domain to the engineer than teaching a domain expert to architect software.

I once worked for a unicorn (1B valuation) company where there were there were <35 engineers and all of them reported to the technical founder.

No mangers, no product managers, no appraisal (30% hike or out)

The rule was "I will treat you like an adult and you have to act like one"

Easily the best company I worked for and best Colleuges.

But I have seen this model hiccup once it reached ~70 engineers.

May be because of the structure or may be it's difficult to hire more such engineers India. Might scale better in SF.

Surprised to see HN being bearish on this.

I have 10 years of experience. I am a reasonable engineer. I can tell you that about half of the hype on twitter is real. It is a real blessing for small teams.

We have 100k DAU for a consumer crud app. We built and maintain everything in-house with 3 engineers. This would have taken atleast 10 engineers 3-4 years back.

We don't have a bug list. We are not "vibe coding" , 2 of us understand almost all of the codebase. We have processes to make sure the core integrity of codebase doesn't go for a toss.

None has touched the editor in months.

Even the product folks can raise a PR for small config changes from slack.

Velocity is through the roof and code quality is as good if not better than when we write by hand.

We refactor almost A LOT more than before because we can afford to.

I love it.

If true, this is the funniest thing I have seen an LLM generate.

Wait until he discovers vercel and nextjs.

I am reasonably confident that Smart Phones will take the route of cigarettes.

Restricted to adults over 21 years of age.

IIRC from the red wild boar book, JSONs biggest win is that it got the adoption.

Getting everyone to agree on a standard was/is/will be the tougher part.

Completely Agree.

Both Romans and Mongols have lost/retreated many battles. They just had to regroup and raise another army over and over again. Some of their opponents could not even afford the war even after winning over them multiple times.

The other sides simply were more fragile, where you were defending and once your city falls, you are done.

Avoid risk of ruin. Keep the ability of taking multiple shots with upside in your favor.

There is a 5000 years old epic called Ramayana which dedicates a significant part of it to a conversation between the protagonist Ram and his guru, agastya.

The summary of that entire conversation is this:

If you ever feel demotivated, defeated or dull just pray to the sun or go into the sunlight.

This message was repeated dozens of times over and over with various metaphors.

I think they were trying to hammer the point that sunlight solves a lot of issues.

Seriously, what is the advantage of tools at all. Why not implement custom string based triggers.

First of all, the call accuracy is much higher.

Second, you get more consistent results across models.

I built exactly this in 2016. I realised that Bluetooth requirement from both parties is too much friction.

It worked way better with a QR code.

That way there is proof of presence and the recieving person need not have the app installed.

This is pretty interesting.

I wonder why in my 30 years of lived experience (in India), I never met or heard of anyone being autistic or needing meds for mental health, even amongst the software engineers. But this seems to be fairly prevalent in the US.

It might be under diagnosis but medical services and pharma are extremely cheap and fairly competent, at least for the engineers.

May be they don't openly talk about it due to stigma.

I can't imagine what they would go through here, it's a extremely social culture where you are socially forced into group festivals, gatherings and frequent visits from relatives.

We use it for lead quality assessment, detecting bad language, scoring language on subtle skills etc

Pretty much 5-6 niche classification use cases.

Loved it. Will remember this everytime I add "rounded" in tailwind. :)

what about systems like game engines and softwares like figma. People still use cpp there. Do you see go or go-like languages taking more in this space ?

I don't see how a famine due to bad policy is relavant here.

There has not been a single country so far whose GDP and overall wellness decreased with increase in population.

> I think it can be very difficult to be a 10x engineer because you have to be in an org that has the right type of work, be on a team that's involved in that work, and be in a role in which you're given that work.

Agreed. I noticed that 10x engineers are a product of 10x workplaces. Orgs have insane ability to take the most skilled engineers and make them unproductive.

Honestly, it was just an observation.

IMO, the street fighting skill is a bit less known. I worked for a unicorn which had ZERO managers and ZERO Product managers. The engineers had to speak to the users, write the roadmaps, build stuff and report to the founder. I realised this skill was rare among engineers and less talked about. Initially, I titled this "Street fighting engineers", it eventually evolved into this.