Miko Pawlikowski 🎙️'s Linkedin Analytics

Most underrated traits at work: 0/ Be easy to work with 1/ Get things done 2/ Growth mindset 3/ Help others grow & succeed 4/ Don’t be a diva / low drama None of it requires particular talents. 🟢 Everyone can do it. 🔴 Why are so many people getting this wrong? ♻️ Repost to pass to your network And follow me Miko Pawlikowski 🎙️ for more.

5 Worst Colleagues in Software Engineering: 0/ Chronic Rescheduler ↳ Cancels 5 minutes before ↳ Wastes everyone’s time 1/ Rambler ↳ Doesn’t get anything done ↳ Talks enough to prevent you from work too 2/ Review blocker ↳ Commits to review your PR ↳ Doesn’t do it for days 3/ Overcommiter & underdeliverer ↳ Takes on too much ↳ Doesn’t finish 4/ Email avalanche ↳ Starts email avalanches ↳ Always deep into some discussion Bonus: Message ghoster ↳ Starts a chat with “hi” ↳ Disappears ↳ Sends another “hi” 5 min after you moved on ♻️ Repost for other devs to beware! 🔔 And follow Miko Pawlikowski 🎙️ for more.

Don't stop... It takes time. ♻️ Repost to inspire others. And follow me (Miko Pawlikowski) for more.

Fear of making mistakes will kill your career. What nobody tells you (learn from Stan Lee): 👉 all successful people made awful mistakes (you just didn't see them). People try to avoid mistakes: ↳ Hiding in their comfort zone ↳ Pretending to know everything 🔴 It doesn't work. 🟢 Here's what to ask yourself instead: 0/ Is the decision reversible? ↳ If so, you can always go back and change 1/ Reframe ↳ "I'm not qualified" -> "I'm learning" 2/ Seek discomfort ↳ Take on challenges that are feasible, but stretch you* 3/ Acknowledge what you don't know ↳ Say "I don't know" to build your credibility 🎯 Remember: Stan Lee was nearly 40 before he saw any success. Marvel movies have grossed over $22 billion worldwide. What mistakes set you up for later success? ♻ Repost to inspire a friend. 🔔 Follow Miko Pawlikowski 🎙️ for more. * unless you're a pilot or surgeon mid-flight

Nobody remembers your title. They remember how you make them feel. Many workplaces are toxic: * draining energy * encouraging backstabbing * everyone for themselves 🔴 You can't change a culture overnight. 🟢 But you be good to others to set the example. Here's 5 easy things you can do today: 0/ Don't gossip → Talk to people's faces, not backs 1/ Assume good intent → It gets lost easily in Slack 2/ Back up every criticism with a solution → Without a solution, it's just complaining 3/ Recognise good work → It doesn't cost much to appreciate someone 4/ Explain, don't order → Don't pull titles. Explain your thinking Agree? ♻️ Share to make work more bearable 🔔 Follow Miko Pawlikowski 🎙️ for tech & career posts.

13 Lessons from 13 years in Software Engineering: 0. Good code is wasted on a bad company 1. Understand the business, not just the tech 2. Be both a mentor & mentee - simultaneously 3. Imposter syndrome stays forever - get used to it 4. It's always a trade-off, sometimes hidden 5. Side projects are the best way to learn 6. Write things down for your own clarity 7. Write a technical book - at least one 8. Be the go-to person for something 9. Titles don't mean anything 10. Act like a leader from day 1 11. Simple is hard to achieve 12. Always be useful What should I add to the list? ♻️ Repost so that more developers see this. And follow Miko Pawlikowski 🎙️for more.

Be the person everyone wants to work with. Nobody wants to tell you the truth: -> it matters more than your IQ, skills or experience People think (wrong): ↳ they can be mean without consequences ↳ their work will "speak for itself" ↳ they don't need other people 🔴 It doesn't work. 🟢 Want an amazing career? Do this: 0/ Be consistent → always show up → always on time 1/ Really listen to people → understand what they want & feel → don't focus on responding 2/ Appreciate & celebrate wins → nothing bonds better than a team celebration → give credit where it's due 3/ Be genuinely interested → people see though fake quickly → genuinely care for other people 4/ Take responsibility for your mistakes → be the first one to accept your mistake → focus on solutions to others' mistakes, not What did I miss? ♻ Repost to inspire someone today ➕ And follow me Miko Pawlikowski 🎙️ for more.

You're told successful people never quit. That's TOTAL BS 💩 : 🟢 Yes, persistence is critical. 🔴 But sticking to something that doesn't work is stupid. Watch out for these signs before it's too late: 1) You Hate Mondays Are you feeling anxious every Sunday afternoon? 2) You're Always Drained Is your motivation and energy down? 3) You'd advise a friend against it Would you honestly cheer a good friend on this? 4) You feel invisible Does your work go unappreciated? 5) There is no Growth Path Are you missing a clear picture of where you're going? 6) You don't trust your manager Is your boss not aligned with your best interest? 7) The Culture is Toxic Does nothing ever improve and people leave? What's ONE sign that means you should leave for sure? ♻ Share to save a friend from misery ➕ Follow Miko Pawlikowski 🎙️ for more

7 Archetypes of Software Engineering (updated): 0/ The Vibes Coder ↳ Centers a div with Claude ↳ Fixes Claude's bugs with Cursor ↳ Explain the code with Gemini Pro 1/ The Elder ↳ Remembers the time things were first built ↳ Walking documentation ↳ Aura of wisdom, purity & knowledge 2/ The Code Whisperer ↳ Once debugged a toaster ↳ Everything is a challenge ↳ Just don't ask questions 3/ The Firefighter 🔥 ↳ Actually enjoys the chaos. ↳ Will debug a toaster for food. ↳ Unfireable (you see what I did there?) 4/ The Human Linter ↳ Detects missing semicolons under 22ms ↳ Makes you look bad ↳ Talks about coding standards LOTS 5/ The Agile Guru ↳ Has "JIRA" tattoo on their cheek ↳ Created 99% of the meetings in your calendar ↳ Wants your estimates 6/ The LGTM dealer ↳ Reviews PRs within seconds of creation ↳ Never leaves any comments ↳ Always says LGTM Which one do you want to be? ♻️ Repost & tag people this covers! 🔔 And follow Miko Pawlikowski 🎙️ for more.

90% of software engineers just don't get it: 🔴 You're not paid to write code; 🟢 You're hired to solve problems. The code only matters when it solves a business problem. Your career will SUFFER until you understand that. Why is it so common? ♻️ Repost so that it finally lands 🔔 And follow Miko Pawlikowski 🎙️ for more.

Your boss impacts your health more than your doctor. Brutal truth: ↳ It makes or breaks your quality of life. 🔴 Don't settle for bad bosses. 🟢 Look for good managers who: 1/ Want to see you succeed ↳ They should be in your corner, not on your shoulders 2/ Give you opportunities to grow ↳ You either grow or stagnate. There is no in-between 3/ Encourage you to take care of your health ↳ The healthier you, the better the work you do 4/ Let you leave work at work ↳ Unless you're on call, you should be able to relax 5/ Listen to you (actually listen) ↳ Just a genuine, human connection Are you a manager? Be the boss you'd want to have. What's THE best thing a manager did for you? LMK 👇 ♻️ Share to inspire better work culture 🔔 Follow Miko Pawlikowski 🎙️ for posts like this.

19 Worst Rules of Software Engineering: 0. Ship bad software, call it "shipping early" 1. Show off your IQ with complex solutions 2. Evaluate devs by the number of LOC written 3. Withhold bonuses for missed estimates 4. Fix symptoms (ignore the root cause) 5. Ignore coding standards (they're for others) 6. Optimise for performance from day 0 7. If you can't understand, rewrite 8. Use that hot, new dependency 9. Argue over "the best" solution 10. Be "the smartest in the room" 11. Get defensive in code reviews 12. Make your juniors feel stupid 13. Stay in your expertise zone 14. Don't "waste time" on docs 15. Only learn the basics 16. git commit -m fix 17. Ignore security 18. Go full JIRA What's no 20 I should add? ♻️ Repost if you agree. And follow Miko Pawlikowski 🎙️for more.

11 Subtle Career Truths: 0/ Hard work is not enough → You need to make your work seen 1/ Your job title doesn't matter → It's not yours, it's on a lease 2/ A salary bump for dead-end job will cost you → They know what they're paying for 3/ Loyalty doesn't pay rent → What happens when they leave or get fired? 4/ Relationships are crucial → Not "networking", real relationships which cost energy 5/ Comfort kills growth → You can be comfortable or growing. Choose one. 6/ Challenging your boss is an art → Learn how to challenge AND make them look good 7/ Feedback is gold → Discard silly stuff, implement the genuine 8/ Progress is never linear → And we always expect it to be 9/ Burnout is not cool → Others will outlast you 10/ Perfection slows you down → Apply 80/20 rule 90% of the time What did I miss? ♻ Share to inspire a friend ➕ Follow Miko Pawlikowski 🎙️ for more

🔴 You can't have both growth and comfort Why? 🟢 You pay for growth with comfort It's the price of admission. What's one time trading comfort for growth worked for you? ♻ Repost to inspire someone today ➕ And follow me Miko Pawlikowski 🎙️ for more.

You're never too important to be kind. Kindness is a win-win. If you lack kindness, it doesn't matter how good you are. People won't want to work with you. Here are 7 simple ways to be kind: ✅ Be humble, especially when successful ✅ Offer help without asking for anything ✅ Don't take it out on people, ever ✅ Ask people how they're feeling ✅ Take genuine interest in people's lives ✅ Respect other people's time & boundaries ✅ Appreciate publicly, give feedback privately People will remember how you made them feel, even after they forgot what you said. What's your best advice for leading with kindness? ♻ Repost to inspire your network ➕ Follow me (Miko Pawlikowski 🎙️) for more like this Image Credit: Unknown

A positive work culture is not: - Free bananas - Ping pong table - Pizza Fridays A positive work culture sounds like this: 0/ Doctor's appointment? ↳ "Don't need to ask permission, just let the team know" 1/ Taking a holiday? ↳ "No need to run it by me, just let the team know" 2/ Family commitment? ↳ "Of course, go take care of your family" 3/ Feeling sick? ↳ "Go home and recover. Trust you, no need for proof" Good culture is about outcomes. Not the minutia. It's not complicated. What did I miss? Repost for your network to see. Follow me Miko Pawlikowski 🎙️ for posts like this.

You don't need a title to be a leader. 7 subtle signs you're already a leader: 0/ You lead by example ↳ be what you preach 1/ You take initiative ↳ solve problems when spotted 2/ You own your mistakes ↳ builds trust 3/ You support others ↳ even when nobody sees 4/ You communicate effectively ↳ in your own style 5/ You solve instead of complaining ↳ you find solutions, instead of problems 6/ You want people around you to succeed ↳ you lift others up Who's one leader you'll never forget? ♻️ Repost to inspire a friend And follow me Miko Pawlikowski 🎙️ for more.

Imposter syndrome will kill your career. Here's what nobody wants to tell you: -> It never goes away People try fight it: ↳ Hiding in their comfort zone ↳ Looking for external validation ↳ Pretending to know everything 🔴 It doesn't work. 🟢 Here's what to do instead: 1/ Reframe ↳ "I'm not qualified" -> "I'm learning" 2/ Love discomfort ↳ Take on challenges that are feasible, but stretch you 3/ Seek feedback ↳ Actively looking for feedback builds your confidence 4/ Be open about not knowing things ↳ Say "I don't know" to build your credibility 5/ Own your success criteria ↳ Don't live your life to someone else's standards Confidence is a result of action. Don't let the imposter syndrome stop you from starting. ♻ Repost to inspire someone today ➕ And follow me Miko Pawlikowski 🎙️ for more.

18 Subtle Rules of Software Engineering: 0. You WILL regret complexity when on-call 1. Stop falling in love with your own code 2. Every single thing is a trade-off - no "best" 3. Every line of code you wrote is a liability 4. Document your designs and decisions 5. Everyone hates code they didn’t write 6. Don't use unnecessary dependencies 7. Coding standards prevent arguments 8. Write meaningful commit descriptions 9. Never ever stop learning new things 10. Code reviews are to spread context 11. Always build for maintainability 12. Always ask for help when stuck 13. Fix root causes, not symptoms 14. Software is never finished 15. Estimates are not promises 16. Ship early, iterate often 17. Keep. It. Simple. What did I miss? ♻️ Repost so that more developers see this. And follow Miko Pawlikowski 🎙️for more.

Work/life balance explained with an 🥑 "Work is a subset of life, not a superset" You've heard before. But it hasn't hit. It doesn't for most people. Simple advice to do better than most people: 🔴 Don't buy bad avocados 🟢 Look for good avocados Practical ways of achieving good 🥑: 0/ nurture relationships (we all need them) 1/ physical & time boundaries (you need to know where work ends and home starts) 2/ look after your health (it's 10x easier to maintain, than regain) 3/ growth mindset (your brain needs to keep learning) 4/ have hobbies (your brain needs a pattern break) Harsh reality: we all start from zero. Early career, you might have to optimise for work. Long term, think about your 🥑 What made you think about this for the first time? ♻ Repost to inspire someone today ➕ And follow me Miko Pawlikowski 🎙️ for more.