Aminul Haq

𝗙𝗼𝗿𝗴𝗲𝘁 𝟭𝟬𝘅 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲𝗿𝘀. 𝟭,𝟬𝟬𝟬𝘅 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗲𝗿𝘀 𝗮𝗿𝗲 𝗿𝗲𝗮𝗹. Naval Ravikant (via Erik Jorgenson) sums it up perfectly: "𝘈 𝘨𝘰𝘰𝘥 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳, 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵 𝘭𝘪𝘵𝘵𝘭𝘦 𝘱𝘪𝘦𝘤𝘦 𝘰𝘧 𝘤𝘰𝘥𝘦 𝘰𝘳 𝘢𝘱𝘱, 𝘤𝘢𝘯 𝘤𝘳𝘦𝘢𝘵𝘦 𝘩𝘢𝘭𝘧 𝘢 𝘣𝘪𝘭𝘭𝘪𝘰𝘯 𝘥𝘰𝘭𝘭𝘢𝘳𝘴 𝘰𝘧 𝘷𝘢𝘭𝘶𝘦. 𝘉𝘶𝘵 𝘵𝘦𝘯 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘴, 𝘸𝘰𝘳𝘬𝘪𝘯𝘨 𝘵𝘦𝘯 𝘵𝘪𝘮𝘦𝘴 𝘢𝘴 𝘩𝘢𝘳𝘥 𝘰𝘯 𝘵𝘩𝘦 𝘸𝘳𝘰𝘯𝘨 𝘮𝘰𝘥𝘦𝘭 𝘰𝘳 𝘱𝘳𝘰𝘥𝘶𝘤𝘵, 𝘮𝘢𝘺 𝘸𝘢𝘴𝘵𝘦 𝘵𝘩𝘦𝘪𝘳 𝘵𝘪𝘮𝘦." It’s a reminder that leverage matters more than brute force. The right idea, the right execution, and the right person can redefine what’s possible. Do you agree that inputs don’t match outputs in software? Have you ever met or worked with a “10x engineer”?

3

1 Comment

100% agree with this: If tech workers are doing measurable work, they're doing easy work. They're doing repetitious work. This work isn't the most valuable work, and you should minimize it when possible. If tech workers are adding huge value, such as inventing new things their company (or the world) hasn't seen, then their work is hard/impossible to measure. They can swag (guess), but not accurately predict their work.

9

2 Comments

Ever wonder why some companies can ship software at lightning speeds while others seem stuck in the mud? 🚀⏳ . . . . . . . . . Daksh Gupta of Greptile collected real-world insights from engineers at many of the world's largest tech companies, unpacking the intricacies that either propel or impede the speed of shipping code. The big reveal? Older and larger companies tend to move more slowly because the costs of missteps become greater. In some cases, those costs are fairly non-negotiable (e.g. ensuring software for customers in production remains secure) while in other cases, the costs are more optional and cultural (e.g. wanting a lot of accurate estimates, forcing a manager's vs. maker's schedule, etc). #SoftwareEngineering #Tech #DevelopmentVelocity #Innovation #Productivity

1

I am excited to share the latest blog, co-authored by myself, Junhwi Kim and Vyas Sekar, detailing how we managed to successfully localized and improved LLM by combining Fine-Tuning and RAG. https://lnkd.in/gKDkgGPq

70

3 Comments

Part of effective leadership is nurturing talent and developing future leaders. At every stage of my career, from Apple to Google, I've empowered my team with autonomy and trusted them to take ownership. By creating strategic plans for self-sufficiency, we ensure teams can thrive even in our absence. This not only builds strong teams but also prepares them for future challenges. How do you support the growth of future leaders in your organization? #Mentorship #LeadershipDevelopment #TransformingTeams #CultivatingLeaders 

38

1 Comment

How good are Trainium and Inference clusters for online serving of production traffic? Check this blog from Trishul Chilimbi on how Rufus responses are powered with high throughput and resiliency. #Trainium #Neuron #AWS Amazon Web Services (AWS)

6

Since CloudAhoy started, I have made new friends: customers, partners, teammates, media. We have shared many cherished moments. It was a fantastic journey. –– A pilot never forgets the first solo flight. Mine was in 2007, the same year the first iPhone came out. In 2008, I bought an iPhone 3, wrote a post-flight debriefing app for myself, and named it CloudAhoy. I added a flight analyzer and a web viewer. Back in the day most pilots were using flip phones, so I handed several iPhones to CFIs I knew at KBED, to try CloudAhoy. For me, a computer geek, the ability to debrief my flights using actual data was a must. CloudAhoy combined my passion for aviation with my passion for technology. I registered CloudAhoy Inc. in 2010, the same year the first iPad came out. The CloudAhoy iPad app was showcased in Apple’s Tim Cook 2013 keynote address. https://lnkd.in/ecYRyjTh Then Tani Shavit joined: how fortunate can a man be? Together we formed a vision and led its execution. The mom-and-pop company grew. We created a close-knit community of power users; Tani and I continually incorporated their inputs. We added scoring, and extended the analysis precision. Our customers, then and now, include weekend warriors like myself, major flight universities, jet charter operators, and the US military. Each with their specific flight analysis and safety challenges. As diverse as the pilot community is, we all care deeply about safety. You see, when reaching rotation speed and pitching the nose up, no matter how many times you’ve done it before, your heart is filled with the same indescribable joy it felt on your first solo, and your brain works in turbo mode on safety, just like it did back then. Aviation safety is the reason we were burning the midnight oil. In March 2023 we released P-FOQA 1.0 (later renamed FDA), the first pilot-centric FOQA with a focus on safety for GA pilots https://lnkd.in/eyx_mS7f . Most of our large customers are using it now - OPAs, flight schools, and charter operators. Pilots receive an automatic safety report each time they land. So do safety officers after a safety event. I think it’s a big deal for pilots, and for their organizations. In March 2023, less than a  month after P-FOQA’s release, we became part of ForeFlight, a Boeing company https://lnkd.in/ejz2GMBm .  I, and the entire CloudAhoy team, moved to ForeFlight. ForeFlight is a company which I always admired. I have been an enthusiastic customer since 2010. Now it’s time for me to move on.  I remain on the frequency.

74

11 Comments

/*********Mentorship**************/ I was watching today Andy Jassy's video (https://lnkd.in/gRV2mGPr) on career advice. He shared one of the very important thing on Mentor's. Mentor's overall objective is too help you grow. They let you do things which you even think you can not do and then give support if needed. They give honest feedback on areas of growth.

1

Now we have two first class data catalogs integrated with MS Fabric now available in Azure. Of course DataBricks is the heavy heavy favorite in the enterprise lakehouses as well as AI (as of the conference that just finished 🤓)

6

1 Comment

I am writing this just before we start the second of three days where my fellow Principal Engineers in Amazon's People eXperience and Technology organization have come together to discuss strategic technical challenges and how we can leverage our collective skills, talents, knowledge, strengths, and collaborative power to inform solutions to these challenges while delivering real incremental value. Remember my post about the people I work with a couple of weeks ago? This is precisely what I meant. I feel so energized and motivated, ready to take on even the most difficult of situations with the support of my peers - an incredible group of crazy smart and kind people with diverse backgrounds who really care about doing good for our customers (current, future, and former Amazonians) and one another, and from whom I learn a great deal every time we meet. ... which reminds me, we are hiring Principal Engineers in People eXperience and Technology! If you are an experienced software engineering individual contributor leader and if improving the lives of one of the largest, most varied, and complex global populations as part of an amazing community like the one I described speaks to you, please message me to learn more! #amazon #softwareengineering #community #hiring

81

The fast way to impress your boss, or get fired fast: use these words in your emails or meetings :-) : h/t T.K. Rengarajan https://lnkd.in/gJWMSG6Z

26

2 Comments

Yesterday, I visited the Corcovado Train in Rio, Brazil, and saw how poor communication can really mess things up at work. Leaders made sudden decisions without telling anyone, which left everyone confused. Different team members had different information, causing chaos. New policies were created randomly, and managers gave orders without explaining them, leading to blind compliance and confusion among tourists. It's shocking how bad communication can disrupt everything. I'm considering writing about it! #WorkplaceCommunication #Leadership #Teamwork

10

🚨 I took down a major piece of infrastructure as a tech lead at Yahoo! and didn’t get fired…. I think this is the nightmare scenario for engineers - to not only break your own product, but to do broader carnage to systems at the company. I think we all fear what the repercussions are if we do this. However, when intent is good, recovery is swift and learnings documented, these things are actually quite formative. When it happened, I was able to remain calm and walk through a rollback in 2 minutes, which allowed the downstream infrastructure to recover in about 10 minutes. This was also the start to my reputation as a level-headed technical leader. Good relationships with my peers in the infrastructure team allowed us to quickly diagnose that my code push was the cause of the incident and take action. I was leading a team building a very powerful piece of software. We had a client library that was installed on every server and allowed us to push out front-end code to every web property simultaneously. Code changes would propagate in about 2 minutes from push. It allowed us to provide a consistent branding, search and navigation system.  Because we understood the power of the system, we also had plans in place if something went wrong and had practiced rollback and forwards. Typically, when things went wrong, they were minor UX bugs in the interface. Medium problems cost us some dollars in search revenues. However, this time, my change had a massive impact downstream. I had added a new polling feature that worked against the caching strategy of the platform I was calling. Within 2 minutes of diagnosis I executed the rollback strategy. The bad news was the product manager had to wait a few more days for the new feature to roll again respecting the caching strategy of the platform. The good news is that we recovered quickly. I learned a few lessons from this outage: 🚨 Outages happen all the time and you will likely not lose your job if you cause one. 📝 Your team should have plans should an outage happen how you will approach debugging and recovery. ⏰ Practice for urgent situations before they occur. 🏋‍♀️ Building and maintaining strong connections with leads of systems where you have dependency is key. 🧞‍♀️ I have a special ability to appear completely calm while feeling absolute panic inside, which is a good capability to have. 

60

10 Comments

"Over 25% of all new code at Google is now generated by AI", according to CEO Sundar Pichai in today's earnings call. But is this shift aimed at speeding up the development of complex software, or simply cutting engineering costs? One potential indicator will be if Google reduces headcount by 25% while boosting revenue per employee. Here are some details behind this productivity metric in Google's own research page . Majority of this '25% code' is in the area of code completion, not in code creation. "LLM-based inline code completion is the most popular application of AI applied to software development..." Watch the video to understand further on this metric.

16

3 Comments

While there are certainly individual variations in skill and experience when discussing modern software development the story is much more nuanced than pure individual effort.  * software development is a team sport -- individual performance is heavily impacted by the system in which they are asked to operate in.  * we pair skill and experience to this model of understanding performance by expecting people to be able to influence and adapt in direct proportion to their seniority, aka the more senior you are the more responsible you are for the outcomes of your work, the less senior you are the more your manager and management chain are responsible.  * humans want to succeed, we're social animals who derive purpose from demonstrating skill, and working collectively. All of which is to say there is no way you have over 1000 people underperforming at your company without senior leadership deeply implicated in.  If nearly 10% of your company is failing, versus just having the market move against you, you need to fire the CEO.

150

9 Comments

🚀 How to Approach a System Design Interview: Amazon Prime Video Example When tackling a system design problem, especially for a complex platform like Amazon Prime Video, it's crucial to approach it strategically. Here's how I break it down: Get clarity on the requirements, both functional and non-functional. Focus on the user flows, define the scale, detail out the components, improve scalability, and wrap up confidently. Pro Tip for Interviews: Don’t rush into drawing diagrams! Ask clarifying questions, understand the problem fully, and then build the system piece by piece. Communicate your thought process clearly, and focus on scalability, reliability, and cost-efficiency. Remember, the trick is to think aloud—explain why you're making certain decisions. The interviewer wants to understand your reasoning as much as the final solution! Good luck to all those preparing for system design interviews! You've got this!💪 Want to master system design interviews and land those $500k+ TPM roles? Make sure you're fully prepared with the Kracd.com interview prep course. Sign up today and transform your career in just 30 days. #SystemDesign #AmazonPrimeVideo #TechInterview #InterviewTips #Scalability #CDN #TechCareers #SoftwareEngineering #Microservices #TechLeadership

9

It is remarkable to observe another real-world example of how S3 Express One Zone is assisting customers in achieving their performance and cost objectives across diverse segments.

31

1 Comment