srinathkrishna
Joined 12 years ago
Joined 12 years ago
As someone who moved 6 times in 8 years (admittedly, some of those were for work), and every time, I relied on moving things myself/with friends, I was just tired any more!
For the last move, I hired movers since I was already married by then and our stuff tripled (yes, mine was a very small portion).
The fact that I don't have to move for a while now gives me a lot of peace!
If not already, we will soon lose the ability to think if AI is helping humans (an overwhelming majority of them, not a handful), considering how we are steaming ahead in this path!
So cool to see that they've built something similar in their Portugal office.
I used to work at a Java shop a few years ago. Hated my time there since a. I was coming from a more pragmatic way of writing software in C and Java and its ecosystem made me pull my hair out and b. came across several very senior engineers who insisted on writing code with factories and builders and obscure design patterns which made no sense to me. They were all straight from praying at the altar of Design Patterns and always found a way to give comments about a future scenario where this would be refactored.
I was fairly convinced that design patterns in OOP languages were conceived by relatively senior folks as a form of gate keeping.
At least in the US, the cost of acquiring an EV is the major deterrent from what I can see. If you live in a city and you want to just get a cheap EV for under $25k for your typical commute, there's just no option in the US!
I have a Pixel and have owned Pixel phones for a while and it's a shame that Google is only just opening up HDMI external display on the Pixel 8!
It's a neat idea but I find it hard to succeed at scale.
Having led my fair share of migrations in the past and going through one right now, here are my tips.
- Understand your stakeholders and the teams that are impacted. Spend enough time understanding how the system is being used today. Proxying and abstractions are you friend here. Just get as much data as possible.
- Once you get enough data, make sure to crunch and very importantly, have a means to surface this to the users. More often than not, for systems that have organically grown, you'll be surprised that users themselves don't know how they use an API.
- As much as possible, try to move things seamlessly. You can always do some portion of the migration without users knowing it. This can be as simple as introducing a translation layer or even you making code changes for the users to review them.
- If you're working on a timeline here owing to external factors like vendor contracts, cert expiry dates etc., make sure to buffer in at least a quarter (or possibly more). There will be new discoveries along the way.
- There will always be teams/stakeholders who will oppose to you asking them to do this work. I can't stress this enough - make sure to get your leadership on board. If you have a Program Management Office, make them your best friends. For anything that escalates and gets political, you as an engineer are better served to get the job done and an aligned leadership that backs you will help you fight these stragglers.
- Ultimately, love what you're doing. There's a mistaken understanding that migration work is not as sexy as greenfield work. I truly believe greenfield work is manifold simpler than migration. A migration is more like changing the wheels and the engine of a car as its running. There will be a lot of tradeoffs that have to be made and this is where engineering skills come into the picture!
All the best! :)
PS: I work at Stripe but I don't really work on the PCI compliant part of the company.
I have a long commute (which is not very unreasonable). YouTube Premium also lets you download videos on your phone and have it background play. I usually record talks/lectures the previous night before my commute the following day. Has definitely help me keep my sanity!
My kid watches YouTube sometimes and I'm sure she'll appreciate getting this when she was younger so much so that she will naturally develop the aversion to ads when she grows up! :D