EncodedInsight
1.2K posts
EncodedInsight
@EncodedInsight
Founder | Encoded Insight Offloading operational burden so owners can focus where they're most valuable.
Katılım Mart 2022
724 Takip Edilen329 Takipçiler
Atlassian is still undervalued.
Everyone thinks Jira and Confluence will get vibe-coded away. Instead, they'll build headless versions (API first, same product, no UI) for agents.
Agents need standardized project management just like humans do. Stock is underperforming because people misunderstand what's happening.
English
@drewfallon12 We are getting to the period where some people are going to push through.
They are going to ask Claude Code the "trough" questions and a select few will come out the other side.
English
Building out our Sales corporate training course now…
The only 2 tools you need:
- Claude Cowork
- n8n
The connectors you need:
- email
- calendar
- CRM
- enrichment platform
English
@emm0sh @gabednconfused You're getting paid to be in there. What more do you want?
English
@emm0sh @gabednconfused It would be great if you would just get back in the box
English
@gabednconfused yeah but the natural state of large organizations is it force them all out
English
@arvidkahl Makes sense. If you said proper TDD I was going to be curious how you understand the agents rate of compliance.
English
@EncodedInsight 🤣 first the latter, then, at some point, the former. Start by making sure things don't break, and then adopt a new process that goes test-first.
English
100%.
It is because of agentic code generation that I finally started testing. Without it, there'd be no guarantee a rogue subagent that does not have the full context of the codebase wouldn't nuke a perfectly working feature.
TDD is coming back, because we need it.
Santiago@svpino
Tests have nothing to do with whether you understand the code. They exist to prove the code does what it’s supposed to do. I don’t trust any code I haven’t tested. That’s true whether I wrote the code, you wrote it, or an AI wrote it.
English
@toddsaunders Thought about something like this before as well. The continual compounding of their insights combined with incrementally improving agent based frameworks and whatever comes next could be extremely powerful.
English
A Fortune 500 exec who runs one of the biggest blue collar companies in the country DM'd me yesterday.
Gave me an idea that I'm starting to get really excited about.
Build a version of YC for blue collar builders who use Claude Code.
Essentially an accelerator for blue collar founders building for trades, construction, fleet, field services, etc. Whatever their domain expertise is.
They offered to help fund the first batch, and we started to put together a list of incredible mentors.
It's crazy how fast the power dynamic in software has shifted.
But this could be very big.
English
Lately, whenever I open this app and see the latest tricks, and hacks, and notes, and workflows, and spec here and skill there, I can't help but think:
All of this will be washed away by the models. Every carefully crafted line of code that's precious to you right now will be gone.
Thorsten Ball@thorstenball
Lately, whenever I open this app and see the latest tricks, and hacks, and notes, and workflows, and spec here and skill there, I can't help but think: All of this will be washed away by the models. Every Markdown file that's precious to you right now will be gone.
English
@ibuildthecloud Which "vibe coding" are you referring to here? The one that has extensive planning and iterations or the true yolo or both?
English
There's so many things wrong with vibe coding. Learn the skill, there's advantages. But there are also huge disadvantages. I'm telling you, the future of coding is going to look very close to what we do now, just with some better tools and approaches. It's a step improvement that will have a compounding effect. Not a hard switch to an unrecognizable future.
English
@staysaasy We need you to follow the process but you can't follow it now.
English
When I was at BigTech, the thing that made me eventually quit was a debate about database usage.
I was writing an internal tool to do a bunch of database operations for SREs. They previously all had their own yolo scripts and one of them caused a major incident.
So I write this tool and am using our default database library and it just absolutely sucks. Is so slow. Cannot do things fast enough because it’s building queries so dumb.
So I open this super large PR and my VP personally reviews it and leaves about fifty comments. I won’t fix all of them but like two. I gotta ship this.
So my manager is like dude you can’t won’t fix ever comment from the VP. And notably we can’t go around the database library.
I’m like dude it’s dumb. It’s slow. It makes my code trash.
So my manager sits me down with our two most senior engineers and they’re like yeah dude you gotta use the database library. The answer is to use it and make it faster, not code around it.
And I quit like a month later.
Now, as I’ve gotten older I’ve realized two things.
First, they were totally right that I should have used the default library. Having sprawling one off code and not using standard patterns is a disaster for software organizations.
But, they should have just fixed it. They could have looked at the tooling, debugged the slowness, and had it fixed in a day. They took a ticket to fix it and it didn’t get done before I left.
Sometimes the org is right. Sometimes it’s wrong. Sometimes it’s both at the same time.
English
@shiftj Agreed.
The ease of data capture is inverse to the value of the data.
English
@EncodedInsight Even still, never been easier to compete. Also, that advantage may be also be at risk in the coming years as data becomes easier and easier to capture and migrate (this is already a growing trend)
English
Unpopular opinion: It’s the best time to start a company and the worst time to own one.
It’s never been easier to take down the incumbent.
Todd Saunders@toddsaunders
I heard an incredible analogy from a VC friend that I can’t stop thinking about. “The moat in software was the cost of building software. And Claude Code just mass produced a bridge.” It’s wild when you think about the impact of this. The SaaS boom produced a few dozen billionaires and a bunch of zero sum winners. But the AI SaaS era will mass produce millionaires. There will be fewer ServiceTitans hitting $5B valuations, and instead there will be 50,000 companies doing $500K-$5M each, run by 1-3 people with deep expertise and huge margins. To be clear, I believe that the total value of software goes up, and the number of companies created goes up exponentially. But the number of people who capture the value also goes up 100x. I don’t believe in the “SaaS is dying” headline, I think it’s missing the point. It’s simply that the power of SaaS is changing hands.
English
@Austen Me: can you write integration tests?
AI Agent: I mocked the entire backend and the tests are passing as expected
English
AI Agent: "We're all set and you're totally ready, the app is working and fully ready for production."
Me: "OK, what else do you think would make the app better?"
AI Agent: "Well, I completely faked the backend so no data will persist. Would you like me to build a backend?"
English
Where does the perspective live?
Armin Ronacher ⇌@mitsuhiko
The biggest issue for me with agents is that they are hard to resist. But then you can build yourself some shit into the codebase that you get to regret in record time. And no, I don't think you can vibe yourself back to sanity with better models.
English
we've lost things along the way
Steve Ruiz@steveruizok
It does bother me that it costs money to code now
English