Tushar Nallan

5 questions in 4 minutes: 1. What does a senior software engineer do? 2. How do you motivate your team? 3. Individual Contributor or Engineering Manager? 4. How do you stand out in Big Tech? 5. Is ChatGPT affecting the job market? Hemant Pandey, senior software engineer at Meta, shares his thoughts. Let me know your thoughts in the comments. Cheers!

1.107

12 Kommentare

Incorrect Generalizations with Amitai: einfach = simple vielfach = complicated nullfach = impossible

9

1 Kommentar

✒ Want to Drive Progress? Start With a (Virtual) Pen and Paper. One of the most impactful things you can do to drive progress in product development is to establish a writing culture. Whether it's x-pagers or a PR FAQ (https://lnkd.in/dScDfJzg) based on Amazon’s working backwards methodology, or any structured narrative, writing drives progress. 💎 Benefits Writing down thoughts and discussions offers significant advantages. Here are the most important ones: 👉 Structure your thinking: Writing helps clarify your thoughts. It uncovers overlooked cases and increases overall clarity.     👉 Prevent misunderstandings: Discussions that happen only in meetings, as verbal comments during presentations (or even in Slack), are easily misunderstood. But not in a writing culture. Putting topics on (virtual) paper makes them less ambiguous and keeps discussions transparent for everyone.     👉 Drive progress: Concerns and discussions can easily be captured in writing, facilitated, and ultimately resolved. This maintains forward progress while documenting the reasoning behind decisions. Discussions in normal meetings are often forgotten quickly and next time you start discussing all over again.    ❓ How to Implement a Writing Culture There are a few key elements to successfully introduce a writing culture: 👉 Plan for reading time: At first, it felt odd to me, but here’s how Amazon and Zalando approach this: Meetings on bigger topics include a written narrative. The document can be shared before the meeting, but reading it in advance isn’t mandatory. Requesting this rarely works - someone inevitably won’t have read it. Instead, allocate time at the beginning of the meeting for collective, silent reading. It’s highly effective. During reading, people leave comments in the document. The discussion then starts based on these comments. The facilitator is responsible for following up to clarify, resolve, and close comments.     👉 Living documents: This approach emphasizes that narratives are living documents. They should evolve as the topic progresses. Comments get incorporated into the document when decisions are made.     👉 Writing is a hard soft skill: Many in tech struggle to write clearly and precisely. This is something to consider and address through education. Google offers a great course on technical writing: https://lnkd.in/dyMxMuYm. 📰 If you find this valuable and want more content like this, subscribe to my newsletter, "The Tech Impact Uplift": https://www.ttiu.de 👩‍👩‍👧‍👧 You can also join my workshop, "How to Build and Run a Successful Tech Organization," at the Digitale Leute Summit in November: https://lnkd.in/dXyFnvGi

20

14 Kommentare

2024 is nearly over. Did you already invest in yourself? Maybe you still have budget left for your personal development? If you want to build up your skills on product development, I have two great recommendations for you - both for product, design, and engineering people: 1️⃣ November 6+7 the Tech Leadership Summit will take place in Zurich, co-located with the renowned Product Management Festival. One ticket buys you access to both! My discount code "DiscountSpeakerTLS" will cut the price by 20% - but the value stays at 120%! 2️⃣ November 13+14 will see the Digitale Leute Summit in Cologne. You can learn from amazing talks, but also join full day content-packed workshops. My discount code "DLS24JAN20" will give you 20% off of tickets. Spoiler alert: 2025 will also bring its challenges. 😉 Set yourself up for success! The direct links are in the comments. Disclaimer: Okay, okay - I will also give talks at both, but you can easily go to the other talks instead. 😘

57

6 Kommentare

Nature is healing: https://lnkd.in/dztKzJw4

3

Anthrop\c Anthropic Claude for Android is here Today we’re announcing the Claude Android app. Now, you can use Claude anytime, anywhere on your Android device—for free across all plans including Pro and Teams. The app is designed with the following features:  Multi-platform support: Pick up and continue conversations with Claude across web, iOS, and Android apps  Vision capabilities: Take new pictures or upload files for real-time image analysis  Multilingual processing: Real-time language translation to help communicate or translate aspects of the world around you Advanced reasoning: Claude can help you tackle complex problems, like analyzing contracts while traveling or conducting market research to prepare for a meeting Among many other things, Claude can help you solve problems and make decisions in real time, provide creative inspiration and support productivity on the go. Whether you're drafting a business proposal between meetings, translating menus while traveling, brainstorming gift ideas while shopping, or composing a speech while waiting for a flight, Claude is ready to assist you. To download the Android app, find us on Google Play. Don’t have an Android device? Claude is also available on iOS through the App Store. —The Anthropic team

3

What makes a product go viral? In the case of ChatGPT, a great product + strong partnerships. The ChatGPT product team has certainly done a great job with the product. With its simple UI, it feels like magic is just a click away; there's no need for complicated coding, joining Discord channels, or anything else. Simply open a browser and explore it. Many people say this is the type of product that goes viral on its own. For the most part, I agree. OpenAI doesn't have a large marketing team, nor does it run major campaigns or demos to push the product to millions of users. OAI also leveraged a phenomenon I call FLG "Funding Led Growth". Akin to a prize fight, the larger the purse, the more people watch, the larger the purse becomes, and so on. The sheer size of the investment used to build OAI and ChatGPT created a gravitational force that tugged on users and media alike. But if you examine their growth, you'll notice a critical factor: their partnership strategy, especially with Microsoft. Here's what Microsoft brings to the table. → 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻 Microsoft's extensive enterprise connections and the vast network of companies using its Azure platform give OpenAI an advantage they wouldn't have otherwise. By integrating OpenAI into Azure, the platform becomes the easiest choice for developing custom AI models, exposing OpenAI to a massive customer base. Azure has penetration with ~ 95% of Fortune 500, has over 145M daily active users on Microsoft Teams, and over 250K companies using Microsoft Dynamics 365 and Microsoft Power Platform, according to Microsoft. That's a lot of B2B/enterprise customers that OpenAI has a head start with. → 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗘𝗳𝗳𝗲𝗰𝘁 The growth of AI relies on network effects, but not in the traditional way seen with technologies like telephones where more users directly mean more connections. Here, the more users that engage, the more data is available to train the AI, making it smarter and more attractive to new users. (this is potentially a drawback or cause for concern for enterprise users which OAI needs to overcome) When we first tested ChatGPT, its responses were impressively human-like. However, it was restricted to data up to 2021 —making it outdated for recent inquiries. OpenAI's partnership with Microsoft provides a method to improve that. User interactions on Bing serve as both a testing ground and a source of real-time data, allowing ChatGPT to constantly evolve and enhance its capabilities. So the takeaway is simple: create a great product first, use this product as a wedge to attract customers and forge strong partnerships, leverage this partnership to bring more customers on a large scale (AND improve the product). Both things are important but need to be in order. Below is an image from Jaryd Hermann's article, "How OpenAI Grows." In the bottom left, you can see how Microsoft's distribution and resources have been pivotal in fueling ChatGPT's growth. Thoughts?

72

24 Kommentare

📣 speak with your customers. Have your developers speak and assist your customers. I had the misfortune of having to spend a couple hours waiting inside a bank branch in Portugal. But it provided a lot of insights. People would arrive and immediately have their expectations broken: their fiscal number had to be introduced to have a ticket to be served. They all went "huh? what?". Anyway, all fine, most could move beyond it with the help from other customers - yes, no employee helped - it was wild. Then, one person got to the machine, and they went: "This machine is asking me for a cell phone number but I don't have one." "humm" "I'll try with my home number." "Doesn't work, has to be a cell number." Asked for help from an employee, only to be told it *had* to be a cell number. And yeah, the person had to leave without the transfer they wanted to make and without any other information beyond the "you need a cell number". I love computers and automation but it's weird and wild to me to think that people aren't being helped or not understanding how to sort out their financial lives. We have to build better systems. We have to do a lot better than this. If you're reading this and you're a software engineer building software for bank branches where the end customer has to interact with it, please beg your manager to let you spend a morning at a branch.

20

Why asking your customers what they want doesn't work: 𝗛𝗲𝗿𝗲’𝘀 𝗮 𝗰𝗹𝗮𝘀𝘀𝗶𝗰 𝗲𝘅𝗮𝗺𝗽𝗹𝗲 𝗼𝗳 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼 𝗴𝗶𝘃𝗲 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝘄𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝘄𝗮𝗻𝘁, from Intuit (the $170B financial giant): With the well-intended effort of giving customers what they ask for, Cook [Intuit’s CEO] recalls, Intuit’s development teams would extensively survey customers about what new features they’d like to see in Intuit products. And customers had a lot to say. 𝗧𝗵𝗲𝘆’𝗱 𝗿𝗮𝘁𝘁𝗹𝗲 𝗼𝗳𝗳 𝗮𝗻 𝗲𝘅𝗽𝗮𝗻𝘀𝗶𝘃𝗲 𝘄𝗶𝘀𝗵 𝗹𝗶𝘀𝘁. “They’d ask for 150 features,” Cook says. So the team jumped on that feedback. Development teams would spend weeks arguing and debating which of the list of potential new features were most important to provide. Everybody, Cook says, was guided by what he or she thought was right for the customer. But in reality, it offered no guidance at all. “We got into feature chase,” Cook says. “Too often we’d go look at what customers were asking for and build it.” But absent a clear understanding of 𝘁𝗵𝗲 𝗷𝗼𝗯 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿𝘀 𝘄𝗲𝗿𝗲 𝗵𝗶𝗿𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘁𝗼 𝗱𝗼, “there was simply no way to differentiate which features were the right ones. It’s like navigating without a compass.” ----------------------------------------------- The story is from Clay Christensen's "𝘾𝙤𝙢𝙥𝙚𝙩𝙞𝙣𝙜 𝘼𝙜𝙖𝙞𝙣𝙨𝙩 𝙇𝙪𝙘𝙠: 𝙏𝙝𝙚 𝙎𝙩𝙤𝙧𝙮 𝙤𝙛 𝙄𝙣𝙣𝙤𝙫𝙖𝙩𝙞𝙤𝙣 𝙖𝙣𝙙 𝘾𝙪𝙨𝙩𝙤𝙢𝙚𝙧 𝘾𝙝𝙤𝙞𝙘𝙚". If you want to know the solution, read the book :) Or check out the article (and find out how milkshakes are related to this!): https://lnkd.in/d9NuXMcx I'll wrap up with this great quote by W. Edwards Deming: (thanks Paulo for the reference!) “𝘐𝘧 𝘺𝘰𝘶 𝘥𝘰 𝘯𝘰𝘵 𝘬𝘯𝘰𝘸 𝘩𝘰𝘸 𝘵𝘰 𝘢𝘴𝘬 𝘵𝘩𝘦 𝘳𝘪𝘨𝘩𝘵 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯, 𝘺𝘰𝘶 𝘥𝘪𝘴𝘤𝘰𝘷𝘦𝘳 𝘯𝘰𝘵𝘩𝘪𝘯𝘨. 𝘈𝘧𝘵𝘦𝘳 𝘥𝘦𝘤𝘢𝘥𝘦𝘴 𝘰𝘧 𝘸𝘢𝘵𝘤𝘩𝘪𝘯𝘨 𝘨𝘳𝘦𝘢𝘵 𝘤𝘰𝘮𝘱𝘢𝘯𝘪𝘦𝘴 𝘧𝘢𝘪𝘭 𝘳𝘦𝘱𝘦𝘢𝘵𝘦𝘥𝘭𝘺, 𝘐’𝘷𝘦 𝘤𝘰𝘯𝘤𝘭𝘶𝘥𝘦𝘥 𝘵𝘩𝘢𝘵 𝘵𝘩𝘦𝘳𝘦 𝘪𝘴, 𝘪𝘯𝘥𝘦𝘦𝘥, 𝘢 𝘣𝘦𝘵𝘵𝘦𝘳 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯 𝘵𝘰 𝘢𝘴𝘬: 𝘞𝘩𝘢𝘵 𝘫𝘰𝘣 𝘥𝘪𝘥 𝘺𝘰𝘶 𝘩𝘪𝘳𝘦 𝘵𝘩𝘢𝘵 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘵𝘰 𝘥𝘰?"

9

4 Kommentare

NEW episode in the System Design Series is ready! Title: Database-like Memory, Cache-like Recall https://lnkd.in/d2REEUFT Let me know your thoughts in the comments. And if you like it, share it with your friends :D Also, we are running a 𝐁𝐋𝐀𝐂𝐊𝐅𝐑𝐈𝐃𝐀𝐘 sale at InterviewReady. If you are looking to improve your system design skills, this is a great time. #SystemDesignSeries #NewEpisode

96

2 Kommentare

🧜 Who are these mythical Product Engineers? The Product Engineer is a relatively new role, but they are changing the dynamics of how software is built. With the landscape of software engineering changing, they are getting a fresh spotlight within organizations. Product Engineers ⮑ bridge between product and engineering teams ⮑ refine "What" the team builds to address customer needs ⮑ promote a culture of product-focused development The first in a series of articles that uncovers the discipline of Product Engineering: #productengineer #softwareengineer #softwaredevelopment #productmanagement

14

1 Kommentar

What’s Missing in 12-Factor Apps? In this post, I make the case for why the API-first factor is vital for Cloud-Native SaaS applications. (2 minutes read) https://lnkd.in/dbt3vqFu #12FactorApp #SoftwareEngineering #SystemDesign

9

Unpopular opinion - Engineering teams often forget the mission of our company We go from sprint to sprint like clueless sleepwalkers Without ever connecting to a higher purpose -> i.e. the outcomes & impact of our work As an engineer, I fell into this same trap myself And continued after I started leading engineering teams To overcome this vicious cycle, I used 4 practices: → Share end-user analytics and metrics of how they are using our product To a granular level of which features we built recently are getting adoption and which ones are not Stretch goal: Can we connect our work to revenue? → Set specific & fun themes per sprint/quarter And the themes themselves were aligned  with the company goals, vision and mission → A monthly company-wide showcase of top 5 things we built These sessions quickly became more popular.. than our mandatory all-hands! → Innovation and Patents I hosted bi-annual hackathons  that drove innovation and patentable inventions, And led to market differentiation Do you believe engineering teams should connect to outcomes & impact?

65

19 Kommentare

At the risk of starting a flame war: what's the benefit of using Gradle over Maven? Almost every Gradle project I've downloaded fails to start without tinkering, whereas Maven projects generally just work. Gradle also doesn't seem to support the latest Java. What am I missing?

27

11 Kommentare

As a hands-on seasoned CTO and technology expert, I've helped build tech for brands like Uber, Koo, Cover fox, Citrus and many more. I'm excited to collaborate with growing startups (Series A and beyond) as a Strategic Technology Consultant / Fractional CTO. Here are some key areas where we can collaborate: Technical Architecture Review: Comprehensive review of your technical architecture, identifying areas for improvement and driving practical plans for implementation. Technical Design and Development: Leading technical design of critical product components, ensuring scalability, reliability, and maintainability. Code Review and Optimization: Thorough review of critical product components, identifying opportunities for improvement and optimizing code for better performance. Technical Talent Acquisition and Development: Assisting with technical interviews, strategizing for sourcing top talent, and mentoring teams to enhance technical skills. Microservices Architecture Optimization:  Reviewing microservices architecture, identifying opportunities to reduce complexity and infrastructure costs. SDLC Process Improvement: Reviewing and enhancing SDLC processes to improve team efficiency, quality, and speed to delivery. Some of key results for this collaboration: - Enhance technical excellence and innovation. - Improve team efficiency and productivity. - Reduce technical debt and infrastructure costs. - Attract and retain top technical talent. Let's discuss how we can collaborate to drive technical excellence and growth in your young startup!

119

1 Kommentar

𝗧𝗼𝗽 𝟯𝟬 𝗻𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗰𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗲𝘃𝗲𝗿𝘆 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝘀𝗵𝗼𝘂𝗹𝗱 𝗸𝗻𝗼𝘄 📌 As a software engineer working on product development, I once believed that networking was not a crucial part of my role. That was until the day we had to deploy our product at a customer location. They asked a seemingly simple question: How will we route the traffic from the DMZ? It was a wake-up call that not knowing about networking can lead to not-so-easy situations in the real world. Understanding networking is not just a theoretical exercise. It's a practical necessity when you're developing a product. Knowing how to configure and make it work under various networking architectures can save you from potential deployment headaches. If you need help understanding these, you will have a hard time. Below, you'll find a comprehensive list of the top 30 networking concepts that every software engineer should be familiar with. ⭕ 𝗧𝗿𝗮𝗰𝗲𝗿𝗼𝘂𝘁𝗲: A network diagnostic tool that maps the path between a source and destination, showing hops and latency. ⭕ 𝗘𝗴𝗿𝗲𝘀𝘀 & 𝗜𝗻𝗴𝗿𝗲𝘀𝘀: Manage outbound and inbound traffic from and to a network ⭕ 𝗕𝗚𝗣 (Border Gateway Protocol): A routing protocol for exchanging routing information between autonomous systems (AS) online. ⭕ 𝗩𝗟𝗔𝗡 (Virtual Local Area Network): Logical grouping of devices on a network, segmented for security, management, and scalability. ⭕ 𝗧𝘂𝗻𝗻𝗲𝗹𝗶𝗻𝗴: Encapsulating data within another protocol to transmit across networks securely. ⭕ 𝗖𝗜𝗗𝗥 (Classless Inter-Domain Routing): A method for allocating IP addresses and routing Internet Protocol packets. ⭕ 𝗣𝗮𝗰𝗸𝗲𝘁 𝗦𝗻𝗶𝗳𝗳𝗶𝗻𝗴: Capturing and analyzing network packets to monitor and troubleshoot network activity. ⭕ 𝗗𝗛𝗖𝗣 (Dynamic Host Configuration Protocol): Automatically assigns IP addresses and network settings to devices. ⭕ 𝗔𝗖𝗟 (Access Control List): A set of rules defining permissions for accessing network resources. ⭕ 𝗩𝗟𝗔𝗡 (Virtual Local Area Network): Logical grouping of devices on a network, segmented for security, management, and scalability. ⭕ 𝗣𝗿𝗼𝘅𝗶𝗲𝘀: Intermediary servers between clients and destinations, masking client information. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: Rules and standards for securing network communication. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: Rules governing data exchange between devices on a network. ⭕ 𝗠𝗔𝗖 (Media Access Control) Address: A unique identifier assigned to network devices for communication at the data link layer. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗧𝗼𝗽𝗼𝗹𝗼𝗴𝘆: The physical and logical arrangement of devices and connections within a network. ⭕ 𝗪𝗔𝗙 (Web Application Firewall): A security layer protecting web applications from cyber threats and attacks. What are your favorite ones? #network #technology #softwareengineering

244

28 Kommentare

𝗧𝗼𝗽 𝟯𝟬 𝗻𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗰𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗲𝘃𝗲𝗿𝘆 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝘀𝗵𝗼𝘂𝗹𝗱 𝗸𝗻𝗼𝘄 📌 As a software engineer working on product development, I once believed that networking was not a crucial part of my role. That was until the day we had to deploy our product at a customer location. They asked a seemingly simple question: How will we route the traffic from the DMZ? It was a wake-up call that not knowing about networking can lead to not-so-easy situations in the real world. Understanding networking is not just a theoretical exercise. It's a practical necessity when you're developing a product. Knowing how to configure and make it work under various networking architectures can save you from potential deployment headaches. If you need help understanding these, you will have a hard time. Below, you'll find a comprehensive list of the top 30 networking concepts that every software engineer should be familiar with. ⭕ 𝗧𝗿𝗮𝗰𝗲𝗿𝗼𝘂𝘁𝗲: A network diagnostic tool that maps the path between a source and destination, showing hops and latency. ⭕ 𝗘𝗴𝗿𝗲𝘀𝘀 & 𝗜𝗻𝗴𝗿𝗲𝘀𝘀: Manage outbound and inbound traffic from and to a network ⭕ 𝗕𝗚𝗣 (Border Gateway Protocol): A routing protocol for exchanging routing information between autonomous systems (AS) online. ⭕ 𝗩𝗟𝗔𝗡 (Virtual Local Area Network): Logical grouping of devices on a network, segmented for security, management, and scalability. ⭕ 𝗧𝘂𝗻𝗻𝗲𝗹𝗶𝗻𝗴: Encapsulating data within another protocol to transmit across networks securely. ⭕ 𝗖𝗜𝗗𝗥 (Classless Inter-Domain Routing): A method for allocating IP addresses and routing Internet Protocol packets. ⭕ 𝗣𝗮𝗰𝗸𝗲𝘁 𝗦𝗻𝗶𝗳𝗳𝗶𝗻𝗴: Capturing and analyzing network packets to monitor and troubleshoot network activity. ⭕ 𝗗𝗛𝗖𝗣 (Dynamic Host Configuration Protocol): Automatically assigns IP addresses and network settings to devices. ⭕ 𝗔𝗖𝗟 (Access Control List): A set of rules defining permissions for accessing network resources. ⭕ 𝗩𝗟𝗔𝗡 (Virtual Local Area Network): Logical grouping of devices on a network, segmented for security, management, and scalability. ⭕ 𝗣𝗿𝗼𝘅𝗶𝗲𝘀: Intermediary servers between clients and destinations, masking client information. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: Rules and standards for securing network communication. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: Rules governing data exchange between devices on a network. ⭕ 𝗠𝗔𝗖 (Media Access Control) Address: A unique identifier assigned to network devices for communication at the data link layer. ⭕ 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗧𝗼𝗽𝗼𝗹𝗼𝗴𝘆: The physical and logical arrangement of devices and connections within a network. ⭕ 𝗪𝗔𝗙 (Web Application Firewall): A security layer protecting web applications from cyber threats and attacks. What are your favorite ones? #network #technology #softwareengineering

414

30 Kommentare