Gergely Orosz Profile picture
Feb 3 5 tweets 2 min read Read on X
Unpopular opinion:

Developers are some of the most demanding customers to please with developer tools, and are one of the hardest business to make a profit in.

When we feel something is a ripoff... we'll build ourselves/migrate/adopt a new tool.

Often out of spite!
Can't really point to another business where customers will sometimes leave a vendor even if it costs them a *lot more* to migrate off, or build a tool.

Unsaid is how it's professionally satisfying to prove that we can build a complex tool, plus it's often rewarded by leadership as well!
"Our equity platform doubled pricing? No clue what they do, why do you ask me"

"Our feature flagging vendor wants to push us into a higher tier to keep SSO and would cost us an additional $3,000 per year (10% increase)?

I'll build a new FF system in a week, saving us $10K**

** not counting development, migration, maintenance and opportunity cost. But seriously how hard can it be to build feature flags: I'll show them!
Huge respect for anyone being able to build and run a successful and profitable dev tools startup or company

Cannot think of many more challenging things. And must be SO satisfying if you manage! This is the founder of @raygunio

Even more respect to dev tools companies that "give back" in some way to the broader ecosystem (it could be open source, could be other ways.)

After a while you realize great dev tools/dev ecosystems are rare, and as devs we DO need to appreciate them & the people who make them

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Gergely Orosz

Gergely Orosz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @GergelyOrosz

Feb 7
Building a profitable company as a commercial open source one with a permissive license feels more challenging these days.

The company needs to make money: which it usually does by selling a managed version of the software.

But here’s the catch: (cont’d)
1. If the open source version of the software is standout and easy to operate: users have little to no incentive to choose the managed version

2. If the license is restrictive, competitors can simply undercut pricing. They don’t need to invest in development of the software much
Open source is a wonderful distribution method. Devs jump on permissive open source projects because… well, permissive license!

It also means that in case of a restrictive relicensing: a permissive fork can be born (see eg Elastisearch vs OpenSearch; Redis vs ValKey)
Read 7 tweets
Jan 24
The more I use GenAI coding tools, the more I am convinced keeping to "traditional" software engineering practices is what works most productive here. As in 10x more productive. E.g.

- Small changes
- Test that the change works before moving on
- (unit) tests wherever you can
Amusing how error-prone all of these models are

I catch how often it generates buggy code thanks to testing and adding unit tests (I have it usually generate tests and then I tweak for my test cases)

Don't know how people are productive who let it run loose tbh
All those non-devs parroting how GenAI is the end of software development don't do actual development. And esp not wit these tools.

I am pretty confident Meta will have no "AI engineer that will start contributing increasing amounts of code" beyond being a companion like today
Read 8 tweets
Jan 24
One interesting I’m seeing with GenAI coding tools:

The MASSIVELY help technical founders at small and mid-sized startups prototype, challenge dev team, and ship products faster.

A recent example I’ve seen (cont’d):
Founder: “here’s a product idea we should do.”

Dev team: “Ok. We’ll build a prototype. It will be ~2 weeks.” 1 month later there’s a prototype. Another 2 months to ship to customers.

Now: founder builds prototype in ~4 hours, shows to dev team. Team builds a more prod ready one in a week and ships to customers!
I have only seen this work with *technical* founders. Ones who used to live and breathe code and built the first version of product themselves. But as team grew to 10-50+ ppl this was no longer an option.

GenAI is revitalising them - and the product iteration shows it!!
Read 5 tweets
Jan 20
YouTube helpfully shows what other videos people watch who stop by at The Pragmatic Engineer Podcast YouTube channel

This is either a bug, or @ThePrimeagen managed to hack YouTube (not implausible) or he went back in time to upload a video in 1970

Or.... OH WAIT I KNOW Image
If you know why this says 55 years ago don't say a thing!!

(if you know you know)
Can't believe no one bothered to fix this at YouTube

(I refuse to believe no one noticed it FWIW)
Read 6 tweets
Jan 15
Interesting:

Meta created React Native. It’s used (with components at least) in their flagship apps: Facebook (iOS, Android), Instagram (Meta Quest), Messenger (desktop).

Google created Flutter. And yet none of their flagship apps use it (Gmail, YouTube, Maps, Calendar).
The only flagship Meta app not using React Native is WhatsApp.

Google does build a lot of smaller apps with Flutter.

Just odd that Flutter can be used as modules (for a few screens) but Google, for some reason, doesn’t do with major apps.

Food for thought.
Flutter powers more apps than React Native: but more iOS apps are RN than Flutter.

Large-scale case studies published are mostly RN. Flutter case studies are usually smaller apps.

More details on each technology, and other Flutter and RN alternatives:

newsletter.pragmaticengineer.com/p/cross-platfo…
Read 9 tweets
Jan 14
Record revenue (on track for $156B), record profits (on track for $55B), fresh enough memories from firing 25% of staff... and Meta is at it, again.

Ruthless business rationale, as the goal is not cost savings, but firing the old, hiring the new.

Good luck to everyone at Meta. Image
Source:

Hard to believe that ~2 years ago, Meta had not done any mass layoffs throughout its entire history (2004-2022)

Now it looks to become an annual tradition. What a change.bloomberg.com/news/articles/…
To be fair, Meta is doing what Amazon has always done. The target for Amazon is 6%, and it's an open secret.

The new Meta culture in this sense could well become what the existing Amazon one is like.

From @Pragmatic_Eng at newsletter.pragmaticengineer.com/p/amazonImage
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(