Gergely Orosz

The Pragmatic Engineer [1] is the other main place I follow. They complement each other nicely. [1]: https://blog.pragmaticengineer.com/

The pragmatic engineer blog by Gergely Orosz is great, especially when it comes to topics that are career-related or about the tech industry in general. https://blog.pragmaticengineer.com/

Email Gergely Orosz at https://blog.pragmaticengineer.com/ He loves stuff like this.

I'm not affiliated with him in any way, but I quite like the tweets from http://twitter.com/GergelyOrosz He has a book that I've not read, but could be worth getting https://blog.pragmaticengineer.com/ FWIW I've worked at FAANG for 5+ years.

I wrote the tweet. Didn’t realize it’s would be posted here. I cannot edit tweets after it has replies (apparently by design). I added follow-up tweets, but seeing those are not read: I deleted the tweet. Here are numbers in context, not looking at stock-based comp: https://blog.pragmaticengineer.com/

I agree that the idea is cool, but from what I've heard from people in the role at most companies it's essentially a solutions architect role by another name. Funny enough, the Pragmatic Engineer (author of the post linked) had a follow up from about a year after the post above and he reports the same thing. https://blog.pragmaticengineer.com/the-pulse-forward-deployed-engineer…

I used the following sources to create an RFC template (and promote the document culture across the engineering documentation): - https://www.industrialempathy.com/posts/design-docs-at-google/ - https://github.com/rust-lang/rfcs - https://github.com/kubernetes/enhancements/blob/master/keps/sig-archit… - https://blog.pragmaticengineer.com/rfcs-and-design-docs/ Hint: tailor the process and template structure based on your org size/maturity and needs. Don’t try to blindly mimic/imitate.

According to multiple outlets including Gergely Orosz, this was incorrect reporting. https://blog.pragmaticengineer.com/builder-ai-did-not-fake-ai/ This has impact on those careers so it’s worth getting right.

IN RESPONSE TO: Just like AI seems like it's being used as a convenient scapegoat for the layoffs and trimming following the end of ZIRP there are like 4 factors besides ZIRP i've witnessed as a hiring manager - Layoff or dont hire locals in favor of H1b/H4 - Layoff or dont hire locals in favor of Nearshore and Offshore - Section 174 Tax code on software: https://blog.pragmaticengineer.com/section-174/ - More productivity via LLMs, Code Assist

A great, detailed explanation of what you are seeing: https://blog.pragmaticengineer.com/software-engineering-salaries-in-th… (and the other two parts of the series) The most important point is that your compensation is far more sensitive to getting onto the next curve up than it is tied to your experience or your work at your current company. This is why so many people say "Grind Leetcode, get into FAANG" as the goal in software engineering, because (at least until recently) being in FAANG even as a junior SWE pretty much guaranteed you were in the second or third curve, and once you were accepted into that curve you would generally find jobs in that same curve. With the way the software engineering job market has changed, I'm not sure that's true any more, but as recently as 2023 it was the rule of thumb.

I’ve had similar unexpected experiences recently while searching for a software developer role. I found this article very interesting in that regard: https://blog.pragmaticengineer.com/software-engineer-jobs-five-year-lo… It could just be a phase, especially with the potential rethinking of IT infrastructure and dependencies on US products in Europe. However, the recent economic uncertainty in the US doesn’t help either. That said, there are still plenty of digitization needs worldwide that will continue for a long time. In my opinion, it’s always best to apply to companies directly. Online maps have been a great and effective search tool for me. Wishing you all the best

Incorrectly top voted answers. "zeroes" is the plural form. The use of zero in "zero 3s" is not the number 0 but an adjective, synonym to "no" in that context. The correct answer is the third one: https://ell.stackexchange.com/a/352496 I guess this is one of the reasons for the failing popularity of the Stack Exchange sites, simply voted best answers that are incorrect. Similar to how you will find 30 incorrect upvoted seemingly correct-but-actually-incorrect answers to many reddit questions with the correct answer hidden deep down in the comments with no karma. Similar how HN is turning out lately, too. Related: https://blog.pragmaticengineer.com/are-llms-making-stackoverflow-irrel…

> In a large company, aren't workers incentived to please their immediate manager and whatever higher metrics/appearances they're exposed to. Your manager alone can’t promote you in BigTech. Your promotion has to be approved by a committee based on a promo doc. You can both make your manager happy by doing “glue work” that makes them look good and not have anything worthwhile to put on your promo doc that the committee will find suitable for a promotion. https://blog.pragmaticengineer.com/software-engineering-promotions/

No, I'm talking about the section 174 update. Great explanation here. https://blog.pragmaticengineer.com/section-174/

https://blog.pragmaticengineer.com/section-174/ is a good read on Section 174, for those who might be curious.

Check out section 174. Due to some GREAT legislation you can no longer write off engineers as an expense... it makes SWEs a tax liability instead of a write-off. https://blog.pragmaticengineer.com/section-174/

That's an intense story! Pragmatic engineer has a great article on where to find technical mentors, such as Coding Coach, Mentoring Club, Mentors in Tech. Would be curious to get people who used them. Link to the whole article: https://blog.pragmaticengineer.com/developers-mentoring-other-develope…

This is always a good read: https://blog.pragmaticengineer.com/project-management-at-big-tech/

Just be aware that by doing so you are ruling out a huge swathe of companies, typically the ones who pay much more than the rest [1]. It’s fine to do so, money isn’t everything, but I think it’s worth being aware of the trade off. FWIW I think any reasonably competent developer can master Leetcode to a good enough level in maybe a few months (outside of work)… The Manning Grokking Algorithms book is a nice simple intro. [1] https://blog.pragmaticengineer.com/software-engineering-salaries-in-th…

I mentioned £200k because it's near the top end for a senior engineer in London (although not the very top). FAANG, some Unicorns, trading firms will pay this to a senior engineer. Bear in mind this is total compensation, so part of that will be in stock or options. For engineers based in the UK that are shocked by this number I'd recommend reading this [0] article. It's about compensation in the Netherlands but the same principle holds for the UK. [0] https://blog.pragmaticengineer.com/software-engineering-salaries-in-th…

There's more than one AGILE methodology. SCRUM is only one of several. Probably if you're doing SCRUM you're using techniques from some of the others, so you might not see the distinction. Look 'em up. KANBAN, for example. A whole lot of organizations, particularly gelled teams at them, do some variation of "plan, iterate, ship": https://blog.pragmaticengineer.com/project-management-at-big-tech/ AGILE consultants did not invent iterative development, by the way. I have never seen any process actually followed that looks like the AGILE consultants' caricature of "waterfall". The more serious you get, though, about defining requirements up front and making sure you meet them, the more your process will look like traditional systems engineering and stage gates. This does not preclude iterative work - the buzzword decades ago was the "spiral model".

Scale and culture. For scale, see https://blog.pragmaticengineer.com/software-engineering-salaries-in-th… for more. There just isn't a lot of money in only a local market, and trying to accommodate a dozen countries worth of languages, culture and standards is far more difficult than one. For culture, a lot of European countries feel it is justified developers earn similar to other white collar jobs. It doesn't have the "heightened" status I often feel the US seems to give developers. Other white collar jobs don't really earn a lot either. Tech jobs kind of stop growing at senior, and require pivoting into management at least partially for higher income. Speaking of management, it is kind of unheard to earn more than your manager, unless you solidly outrank them in seniority. As a result, whatever the manager is paid, forms a tight glass ceiling for oneself.

Depending on what your current "level" is you might be interested in what https://blog.pragmaticengineer.com is saying (It's mostly aimed at Senior and above). He focuses on Europa in comparison to the usual US centric advice you'll find everywhere.

I found this article to be pretty enlightening about the nature of of the software engineering job market, which should help you figure out what companies can afford expensive developers. https://blog.pragmaticengineer.com/software-engineering-salaries-in-th… If you're okay with a little risk, it's probably easier to join a remote series S-ish startup where you get a solid base salary (130k-180k based on your experience) and where the stock could be worth anything from 0k/yr to $100k+ per year. I would highly recommend only joining these types of companies if they have technical founders who have worked in BigTech and understand the value of high quality engineers and maintaining a good engineering culture (aka blameless post mortems, predictable deadlines, no-overworking, etc.)

It is less technical and more leadership, strategy and soft skill side of engineering but https://blog.pragmaticengineer.com/ definitely deserves a mention.

Thanks for that. We're investing a lot in expansion in LatAm at my other company - and one thing I learned about Argetina's job market is that you have 2 tiers of developers: one working mainly for internal market and the other - for US customers. The salaries may differ by the factor of 3 or even more. Here is a great piece of research about similar situation in Europe: https://blog.pragmaticengineer.com/software-engineering-salaries-in-th… Actually, the idea of Greenlight has a lot to do with this salary gap phenomenon. I see this as a big potential for a win-win.

- https://textslashplain.com/ by Eric Lawrence of Fiddler fame, who's worked for last two decades on IE, then Chrome, then Fiddler, then Chromium-Edge. A mine of knowledge on browser internals, networking, web compat. - https://blog.pragmaticengineer.com/ by Gergely Orosz, on mobile dev & big tech from European point of view

Newsletters http://levelup.thekua.com/ https://softwareleadweekly.com/ http://www.techmanagerweekly.com/ https://wherewithall.com/ Blogs https://randsinrepose.com/ https://blog.pragmaticengineer.com/ https://www.theengineeringmanager.com/ https://www.askamanager.org/ https://increment.com/ https://devtomanager.com/ Conference https://theleaddeveloper.com/ Other Resources http://lenareinhard.com/engineering-management-reads/ https://github.com/LappleApple/awesome-leading-and-managing Previously: Best book / resources on leadership, especially for tech teams? https://news.ycombinator.com/item?id=21712194

Back in the day when you found a solution to your problem on Stackoverflow, you typically had to make some minor changes and perhaps engage in some critical thinking to integrate it into your code base. It was still worth looking for those answers, though, because it was much easier to complete the fix starting from something 90% working than 0%. The first few times in your career you found answers that solved your problem but needed non-trivial changes to apply it to your code, you might remember that it was a real struggle to complete the fix even starting from 90%. Maybe you thought that ultimately, that stackoverflow fix really was more trouble than it was worth. And then the next few times you went looking for answers on stackoverflow you were better at determining what answers were relevant to your problem/worth using, and better at going from 90% to 100% by applying their answers. Still, nobody really uses stackoverflow anymore: https://blog.pragmaticengineer.com/stack-overflow-is-almost-dead/ You and most of the rest of us are all actively learning how to use their replacement

> Is there more information on this somewhere. Yes, everywhere. You just need to look for it. See the following link, which has references to Apollo and MAWS. https://blog.pragmaticengineer.com/amazon-notable-systems/ > I thought this sounded crazy, and it would be interesting if Amazon themselves didn’t even have what was being asked of us. Amazon has multiple incantations of this. As legend would have it, AWS was an offshoot of Amazon's internal cloud infrastructure designed to monetize it to amortize their investment on bare metal infrastructure. They partitioned their networks for security reasons and for a few years their infrastructure evolved independently. Then AWS was a huge success and took a life of its own. Only relatively recently did Amazon started to push to drop their internal infrastructure to put all their eggs on AWS in general but serverless solutions in particular.