Sharing Engineering Knowledge with the Public

🔍 Top Engineers Aren’t Applying for Jobs. They’re Getting DMs Some of the best engineers I know haven’t touched a job board in years. They’re not lucky. They’re just visible. Most people play the default game: • Collect credentials • Polish a resume • Apply everywhere • Cross fingers But the reality is that the most exciting roles are filled before they’re posted. Why? Because someone already knew how that engineer thinks. The engineers who get noticed do one thing differently 💡 They make their thinking public 💡They don’t wait to be discovered. They create conversations around how they solve problems. Here’s what that looks like: 🛠️ Sharing how they debugged a messy outage 🧱 Explaining why they chose X over Y in a system design 📚 Writing about things they’re still figuring out 🧠 Posting takeaways from technical docs or trade-offs It’s not about showing off. It’s about showing how you think. Visibility in tech isn’t one-dimensional 🧠 Credentials — everyone has them 🧠 Connections — helpful but limited 🧠 Thinking — rare and magnetic The third one is where career growth compounds. You don’t need to be an expert In fact, the most valuable posts I see come from people sharing what they’re learning in real time. Hiring managers are not just looking for perfect skills. They want people who can reason through problems and learn fast. Real talk The market is noisy. But signal cuts through. You can hope someone picks your resume from a pile or you can start showing how you think and let opportunities find you. Start small: ✅ One lesson from today’s debugging ✅ One insight from a recent decision ✅ One technical rabbit hole you’re exploring Do it consistently. Not to go viral. To be discoverable #TechCareers #EngineeringLeadership #SoftwareEngineering #CareerGrowth #DevCommunity #SignalOverNoise

"We just found out the infrastructure team is building the exact same notification system we've been working on for the past three months. How did nobody know about this?" 🤦♂️ This scenario plays out in companies every day. When you have 20 people, everyone knows what everyone else is doing. Once you hit 200 or 2,000, it's an entirely different game. Small organizations can move quickly because they're naturally aligned. Information flows freely. Decisions are visible. Then growth happens, and suddenly people are building solutions in parallel without knowing it. Teams optimize for their own metrics at the expense of broader company goals or what is going on around them. Knowledge becomes a form of power rather than a shared resource. James Clear captures this perfectly: "You do not rise to the level of your goals. You fall to the level of your systems." So what's the antidote? Working in public. This means: 📣 Sharing ideas when they're half-baked, not just when they're polished 👀 Making strategic discussions visible beyond the "necessary" participants ✍️ Documenting decisions and their context so others can follow the thread 🔍 Actively seeking input from those with relevant expertise, not just those with relevant titles When teams feel pressure to move quickly and make as much impact as possible, they can choose to run them as closed, executive projects. But the most successful ones create visibility into their thinking from the beginning. Yes, this invites complexity. Yes, it surfaces objections. But it also uncovers important insights that would become expensive roadblocks (and rewrites) if discovered later. The pushback I often hear is: 🐢 "This will slow us down." 🧑🍳 "Too many cooks in the kitchen." 🚫 "People will criticize before the idea is ready." The reality is that while working in public might feel slower at the start, it dramatically reduces the technical, product, and organizational debt that accumulates when teams work in isolation. It creates stronger solutions through diversity of thought. It builds organizational muscle memory for collaboration. Working in public isn't just about transparency — it's about creating systems that make the right thing the easy thing. What systems have you put in place to ensure your organization doesn't fall prey to silos? #leadership #strategy #productmanagement #scaling -------- 👋 Hi, I'm Nathan Broslawsky. Follow me here and subscribe to my newsletter above for more insights on leadership, product, and technology. ♻️ If you found this useful and think others might as well, please repost for reach!

Petroleum engineering isn’t exactly “YouTube famous.” But I started sharing insights anyway. Now PetroPapers reaches engineers across the world. Here’s how I built a niche tech platform from scratch. No hype. No hacks. Just one post at a time. Here’s what I learned along the way: 1/ No one talks about our field → So I did. → Turns out, people were waiting for it. Fix: Share what you wish someone had shared with you. Others are asking the same questions. 2/ You don’t need a huge audience → You need the right one. → Quality over clout. Fix: Speak to one type of reader. Engineers, not algorithms. 3/ Don’t wait until you feel “expert enough” → Start when you still have questions. → That’s when your voice is real. Fix: Write what you’re learning now. Someone else is just behind you. 4/ Content isn’t just for reach → It’s for connection. → It builds community faster than coffee meetings. Fix: Reply. Repost. Rethink out loud. That’s how trust grows. 5/ Niche is power → I didn’t chase trends. → I focused on value only engineers would get. Fix: Go deeper, not broader. That’s how you stand out in silence. PetroPapers started with zero followers. Today, it’s a global hub for tech minds. Not because I’m loud. But because I stayed useful. P.S. Thinking of starting your own niche platform?

After many years of working in steel structure design, I’ve built up a collection of detailed notes- part -1, calculations, and practical insights — all based on real project experience and continuous learning from AISC code. I’m excited to share these notes with my network to help other engineers bridge the gap between theory and site reality. I’ll be posting sections soon covering: -Base plate and anchor bolt design -Connection detailing (bearing vs slip-critical) -STAAD modeling tips for steel structures -Practical design checks from my projects I hope these notes will be helpful for young engineers and professionals looking to refine their design workflow. Let’s keep learning and growing together 💪 #SteelDesign #StructuralEngineering #AISC #STAAD #EngineeringCommunity #KnowledgeSharing

The most underrated dev skill no one teaches in college? It’s not DSA. It’s not operating systems. It’s how to present your work and build in public. Engineering colleges cover everything from physics and calculus in the first semester to OS and computer architecture by the last. But almost none teach you how to showcase what you build. Here’s how I learned it the hard way and how you can start doing it better: 1. Building in public ≠ just posting on social media It also means attending hackathons, building on the spot, and presenting your work confidently to judges. One of my first internships came from a hackathon judge who liked how I explained my project. 2. Share your progress. Collaborate openly. Talk about your projects with friends, post small wins, ask for feedback. Once your peers know what you’re building, you’ll feel more accountable to finish it. That’s the good kind of peer pressure. 3. My LinkedIn internships came inbound Why? Because I posted demos, thought processes, and lessons from every project I worked on. Recruiters notice devs who show their work — not just list it. 4. When no AI internships came, I made my own path I started a blog called The AI Playbook on Hashnode and wrote consistently. That blog alone landed me an AI internship at IISc Bangalore. 5. Even fun side projects count Made a small game? Built a quiz app? Great. Side projects show curiosity and consistency. Don’t wait for a big launch — talk about them. Building in public shaped my tech journey — and it can shape yours too. It builds credibility, invites collaboration, and creates unexpected opportunities. Start small. Stay consistent. Happy coding

Share Your Knowledge: The Ripple Effect of Learning 🌍✨ Knowledge is one of the few resources that grows when shared. Too often, professionals guard their expertise, fearing competition or undervaluing the impact of their insights. Yet, the act of sharing knowledge is not about giving away your advantage — it’s about multiplying value. Why Sharing Matters - Empowers others: When you teach, mentor, or simply explain, you help someone else unlock potential they didn’t know they had. - Builds credibility: Sharing your expertise positions you as a thought leader and trusted voice in your field. - Strengthens collaboration: Teams thrive when information flows freely, creating innovation instead of silos. - Creates legacy: What you know today can inspire someone tomorrow — and that ripple effect is immeasurable. Practical Ways to Share Knowledge - Write articles, posts, or blogs that distill your experiences into actionable insights. - Offer mentorship or coaching sessions, even informally. - Host workshops or webinars to reach wider audiences. - Encourage open dialogue in meetings — sometimes the smallest tip sparks the biggest idea. The Mindset Shift Sharing knowledge isn’t about proving you’re the smartest in the room. It’s about being generous enough to lift others up, confident enough to know your value doesn’t diminish, and wise enough to see that collective growth benefits everyone. Do you agree? Follow Lisa A. Jones, GGAF CEO, PMHA