
CTO @theblueground | Building @clam_ai
Athens
Joined November 2009
- Tweets1.3K
- Following853
- Followers704
- Likes4.2K
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/
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:
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.
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!
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:
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!)
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.
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
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.
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.
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…
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.
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
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.
Stratos Pavlakis retweeted
Hola good people!
A new @GreeceJS season is just around the corner 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/cwNUeCMBDR482jbRA
#GreeceJS #meetup #tech #community
Stratos Pavlakis retweeted
Thank you @KotlinWeekly for featuring our library! 🙏
github.com/bluegroundltd/fix…
Stratos Pavlakis retweeted
Yesterday we released a fork of Trendyol/jest-testcontainers through the Blueground NPM organization. It updates testcontainers-node to the latest version, which also inlcudes support for arm64 architecture! Feedback is welcome npmjs.com/package/@bluegroun… #javascrpt #testcontainers
Stratos Pavlakis retweeted
If you are a staff+ engineer, your bandwidth should be primarily spent on simplifying systems & processes and guiding teams how to simplify.
Stratos Pavlakis retweeted
My view is the best way to get into machine learning, "web3" or other "hot" areas *as a dev* is to become a solid sw engineer first.
Here's a good example of why.
Say you want to work on crypto at Robinhood. Let's see what you need to know: Python, SQL & "web2" engineering:

ALT Initial efforts Our crypto backend is built on the Django framework with PostgreSQL databases. With the increased traffic, we noticed that the primary database and its read replica became the performance bottlenecks. The surge of database CPU usage and replication lag at times poses high risk of degradation of product experience. To better scale our systems, our infrastructure and product teams got together and decided to make these optimizations: reduce database loads, conduct load tests and size the demand and prioritize critical flows.

















