Twitter | Pretraživanje | |
Gergely Orosz
Engineering lead . , & alumni. I tweet about software development, high-performing teams & distributed systems.
1.379
Tweetovi
487
Pratim
9.723
Osobe koje vas prate
Tweetovi
Gergely Orosz 1. velj
With so many companies focusing on "good-enough" and cheaper cross-platform technologies - think Flutter, RN - there's an opportunity in delivering best-in-class experiences with those same products. This is what so few companies/teams do, and it _is_ a competitive advantage.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 31. sij
Odgovor korisniku/ci @jstanier
Congrats!!
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 31. sij
Odgovor korisniku/ci @albertodebo
Yeah you should come! Tough decision, I know, as this year I’m not speaking - it’ll still be great! ()
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 31. sij
Odgovor korisniku/ci @albertodebo
The question is when you're coming to Amsterdam to up the iOS game at :)
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 31. sij
A hard thing of building a new platform - framework, service, or a combination - is balancing patching the existing solution, over investing forward. When the new platform goes live, it will have some issues the old solution didn' have. You need to deal with those issues, fast.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz proslijedio/la je tweet
Zsombor Erdődy-Nagy 30. sij
Odgovor korisniku/ci @drincruz @GergelyOrosz
To give you other concrete examples we're doing iOS Buck -> Bazel migration to unlock remote build execution right next to the current laptop upgrade eval. Improving internal dev NPS score is what we're about.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 30. sij
Odgovor korisniku/ci @drincruz
Yes, it’s been ongoing for 3+ years now. The MacBook replacement (and replacing existing 4-core 16GB machines for mobile devs to 6-core ones) is something that catches everyone’s eye. This team also ported buck to Swift (and contributed back) and built SQ:
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 30. sij
Some context: 1. We have an internal program to reduce blockers on dev productivity. 2. Projects include faster builds (local/CI), less manual steps to deploy to prod, more/easier automated tests. 3. Measuring efficiency by upgrading to the latest hw is one of many projects.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 30. sij
Odgovor korisniku/ci @tugkankibar
Damn no tweet editing! 6-core :)
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 30. sij
At Uber, our developer platform team benchmarked build time differences on different machines. Mobile builds, despite optimisations like using buck, were still slow. The result: all mobile devs got upgraded to 6-core MacBook pros across the company. Based on measurements & data.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz proslijedio/la je tweet
James Stanier 29. sij
🗣️ If you've bought the beta release of Become an Effective Software Engineering Manager, then two new chapters have just been released. 📧 There should be an email in your inbox shortly. 📗If you haven't got it yet, what are you waiting for? 😉
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 29. sij
I read Refactoring Typescript by (the e-book) and liked it. I found it a nice refresher, a quick and easy read, and learned a few new ideas for refactoring, most notably CQRS. My slightly longer review:
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz proslijedio/la je tweet
Gergely Orosz 29. sij
How to ship software quickly, but reliably: be aware if the change you are about to make is a “one way door” (very hard&expensive to revert) or a “two way door” (easily reversible). Be super careful stepping through one-way doors. Run as fast as you can through two-way doors.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 29. sij
Odgovor korisniku/ci @GergelyOrosz
One-way doors: things that could result in data loss, making promises to customers, or launching new products/features people rely on. Two-way doors: changes with limited impact even if they go wrong. UX changes, experiments, shadow rollouts, feature flagged & granular releases.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 29. sij
How to ship software quickly, but reliably: be aware if the change you are about to make is a “one way door” (very hard&expensive to revert) or a “two way door” (easily reversible). Be super careful stepping through one-way doors. Run as fast as you can through two-way doors.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz proslijedio/la je tweet
Gergely Orosz 13. sij
After thousands of shares for the project lead expectations for software engineers doc I've written, I've finally put some context around it with a blog post (and the link to the project leads document):
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 29. sij
Odgovor korisniku/ci @enginoid
Surely that will be a Sci-Fi follow up novel?
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 28. sij
Odgovor korisniku/ci @adrukh
Oh yes. Old client versions - especially with local data storage! - can really tie a dev team’s hands. Both on mobile, as well as the backend team needing to support old endpoints and data models.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 28. sij
Odgovor korisniku/ci @adrukh
Yes and no. When a distributed system blows up, all consumers can be affected, there can be data loss etc. When an old client version stops acting wacky, a smaller % of customers are impacted. It's also tough to detect this, and many teams don't even notice.
Reply Retweet Označi sa "sviđa mi se"
Gergely Orosz 28. sij
Recurring struggle for the past year: explaining to distributed systems devs why and how building mobile apps at scale is just as challenging as building those large-scale backend systems. Similar concerns, different tooling. I'm halfway writing up recurring talking points.
Reply Retweet Označi sa "sviđa mi se"