Stratos Pavlakis (@th3hunt) profile picture

CTO @theblueground | Building @clam_ai

Athens
Joined November 2009
Stratos Pavlakis retweeted
Weekend project alert! I built bull-cli, a terminal dashboard for BullMQ. This little tool already caters a need in my own workflow, I wanted to manage queues all from the keyboard without visiting a browser. Try it: npx @angelkar/bull-cli ang3lkar.github.io/bull-cli/
2
1
7
390
Stratos Pavlakis retweeted
Today, we're releasing shadcn/cli v4. It packs a ton of features: shadcn/skills, presets, dry-run, monorepo and more. If you're using shadcn/ui with coding agents or need better control over the defaults, this is for you. Here's everything new:
188
522
103
6,704
557,133
Stratos Pavlakis retweeted
Anyone who still thinks of Cursor as a VS Code fork needs to update. Cursor cloud agents are quickly becoming my default way of shipping new code.
We're introducing Cursor Automations to build always-on agents.
3
4
1
50
10,572
🤯Mind. Blown. @resolveai Alert at 18:10 → resolution by 18:11 We had in minutes what would’ve dragged across sprints.
2
4
19
939
Stratos Pavlakis retweeted
When you look at most CTOs and engineering executives at most tech companies: their engineering background is more often than not backend engineering. Worth considering what this means esp if they lead a co where the main product *is* mobile, web - or to delight customers!
29
72
7
1,165
123,228
Stratos Pavlakis retweeted
The essence of why a startup exists is to solve real problems and provide value to customers. I am grateful for the partnership with the @theblueground team. They have been a design partner since day 1. And I am happy to see them getting value. Below is a blog post about how they use Resolve AI Stratos, Geo, Andreas, Pavlos-Petros 🙌
How @theblueground is revolutionizing their on-call ops with @resolveai Their team manages 15K+ furnished apartments across 46 cities. But scaling operations was keeping engineers up at night—literally. Here's how AI changed the game: •10-15 mins saved per alert •Instant context in Slack •Fewer 3am laptop checks •Happier and less stressed engineering team As their Eng Director says: "If it's non-critical, I can go back to sleep. Complete game-changer for peace of mind." Read the full story in the comments:
1
2
10
945
Stratos Pavlakis retweeted
Any time someone speculates RoR not being built for scale, there's Shopify setting records every single year in payments & shipments processed. And the market-leading version control site is on it as well. (RoR IS delightful to use - I realize every time I try it out again!)
9
13
145
11,603
In a few months, at @theblueground we’ve gone from experimenting with @resolveai to making it our go-to. There’s no going back now — on-call and time-sensitive troubleshooting will forever be AI-first.
7
6
3
23
3,778
Piece of advice on adding AI tools like @resolveai to your alert management stack: Don’t cut back on observability—double down on it. Now you have even more reason to As with all Gen-AI, better ‘input’ means better ‘output,’ and in my experience, that's a 10x return.
1
5
226
With solid logs, instrumentation, alerts, and service-dedicated dashboards, this isn’t just hype — it’s measurable, serious help. Pro tip: Prioritize anomaly-detection alerts on business metrics over absolute error rates.
5
168
Stratos Pavlakis retweeted
A common mistake: "Let's abstract this in case we want to replace it later." Examples: 🚫 "Let's abstract React in case we switch JS frameworks." 🚫 "Let's abstract Tailwind in case we switch CSS approaches." 🚫 "Let's abstract Mongo in case we switch Databases". This is typically a waste of time, and often hinders current use too. Why? Because to effectively abstract something, we need to know the API we're abstracting. But we have no idea what a new technology's API will be. Thus, we have no idea whether our abstraction will work with the new technology. In summary, abstraction can be useful. But avoid abstracting merely to support changing to some unknown future technology.
125
110
30
1,100
329,361
Stratos Pavlakis retweeted
Hola good people! A new @GreeceJS season is starting and we're looking for #speakers to share their knowledge and experience with the community. If you're interested in speaking, submit your proposal here: forms.gle/cwNUeCMBDR482j… #GreeceJS #meetup #tech #community
2
10
12
1,191
Stratos Pavlakis retweeted
So many of the great software engineers I consider fantastic "software architects" share this one thing: They build (throwaway) prototypes to prove their point / showcase their ideas. A lot! So much easier to reason about concrete code than abstract ideas.
61
283
57
3,107
512,863
Stratos Pavlakis retweeted
Or, if you prefer, "I am a full product engineer." And this ^^^ is what we should all be trending towards. The days when you could put up your hands and protest, "I'm just a backend engineer. Get someone else to write those five lines of javascript" -- are ending.
17
75
37
602
152,426
Stratos Pavlakis retweeted
We've put all out webinars on YouTube! Document QA, Agents, Prompt Injection... watch them as many times as your heart desires ❤️ youtube.com/channel/UCC-lyoT…
12
60
8
332
54,256
Stratos Pavlakis retweeted
Such a big difference between devs who are capable and willing to learn new things when they need to (eg new languages, frameworks) & have a "sure I will sit down and figure this out the next few days" attitude, versus people who are used to given formal training to do the same.
52
176
24
2,191
382,021
Stratos Pavlakis retweeted
colleges prioritized making people feel perfectly safe over everything else and produced a generation afraid to fail, and thus afraid to take risk, and thus on pace to accomplish extremely little
1,267
2,710
1,122
20,642
13,376,998
Stratos Pavlakis retweeted
The best suggestion I have for software engineers with some experience is to learn a "different stack": dip your toes at least. If you're doing backend: do some frontend or mobile. Or the other way around. You'll learn a ton and appreciate how challenges are different there.
29
47
7
790