Enger Jimenez

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. 🔔 Follow Miko Pawlikowski 🎙️ for more.

2166

113 comentarios

JetBrains just announced they're moving to a single, unified IntelliJ distribution starting with version 2025.3. No more choosing between Community and Ultimate - it's one IDE with features unlocked by subscription. Why does this matter? • Some previously paid features (Spring support, database tools) are becoming FREE • The open-source commitment remains, but with a twist • This signals bigger changes in how dev tools compete in the AI era I spent time analyzing the announcement and its implications. This isn't just about IntelliJ - it's about the future of IDEs in a world where AI assistants are changing how we write code. Full analysis here → https://lnkd.in/gBpSNWUu Curious: How many of you are using IntelliJ Community Edition today? What's your take on this change?

162

4 comentarios

In good times, you’re measured by what you build. In bad times, you’re measured by what you’re worth. When budgets shrink, the scoreboard changes. The sprint board doesn’t matter. Your clean code doesn’t matter. Your “critical” role in the next release doesn’t matter. The only engineers who are safe are the ones tied directly to the money. The ones who own revenue-generating systems. The ones who can explain their impact in business terms. The ones whose absence would make the quarterly numbers drop. If losing you wouldn’t hurt revenue, you’re a line item waiting to be erased. That’s why real job security isn’t in the backlog. It’s in the P&L. Stop being just a cost. Make yourself profit. I help engineers become indispensable to the business. Here's how: https://lnkd.in/gMGfmVas

126

54 comentarios

Here's an uncomfortable truth: many developers struggle to produce effective documentation. I was one of them. My commit messages looked like "fixed bug" and my PR descriptions were basically empty. Then I discovered QuillBot's Chrome Extension and it completely changed how I communicate as a developer. It's not just another grammar tool. It's a structured, lightweight solution tailored for developers who need to write clear documentation, PRs, and emails while juggling complex codebases. Here's what QuillBot handles for me daily: ✔️ Paraphrasing technical explanations - Turn complex logic into clear comments ✔️ Grammar checking commit messages - Professional git history that impresses leads ✔️ Humanizing AI-generated documentation - Make ChatGPT docs sound naturally written ✔️ Polishing PR descriptions - Clear, concise explanations that get faster approvals ✔️ Improving client emails - Professional communication without grammar anxiety Whether you're writing technical blogs, documenting APIs, or just want to sound more professional in team communications, QuillBot helps you stay consistent without the writing overwhelm. The best part? It works right in your browser. No switching contexts, no breaking flow - just better writing wherever you type. As developers, we spend 40% of our time communicating. Why not make it effortless? Try QuillBot’s Chrome Extension for free - your future self (and your code reviewers) will thank you. What's your biggest technical writing challenge? #QuillBotForWork #QuillBotPartner #Ad

162

20 comentarios

Your JSONB query isn’t slow. You’re just using the wrong index. Let’s say you’re storing events like this: { "user_id": "123", "status": "completed", "source": "mobile" } And you're filtering like this: SELECT * FROM events WHERE payload @> '{"status":"completed"}'; You indexed the whole payload column with a B-Tree. That won’t work. Postgres can’t optimize deep JSONB lookups with B-Tree indexes. So it falls back to a full scan on every query. To fix this, you need a GIN (Generalized Inverted Index) Now Postgres creates an inverted index: - It breaks each JSONB object into keys and values. - It maps them to row IDs. - So instead of scanning every row, it jumps directly to matches. Pro tip: Add the jsonb_path_ops option for even leaner indexes, if you're not using containment queries. Faster. Smaller. Cleaner. ------------------------------------------------------------ Jobright provides the latest System Design jobs. Check it out here 👇 https://lnkd.in/emR7tBw5

282

80 comentarios

Your coding skills are worthless if no one understands what you're saying. Here's how to transform from a technical expert to a strategic powerhouse: 1/ Decode Business Objectives ↳ Understand what truly matters to leadership ↳ Connect your data directly to company goals 2/ Speak Their Language ↳ Translate complex algorithms into dollar signs ↳ Show impact, not just technical complexity 3/ Master Data Storytelling ↳ Create narratives, not just spreadsheets ↳ Make your insights compelling and memorable 4/ Deliver Actionable Insights ↳ Every chart should trigger a decision ↳ Recommend clear, executable strategies 5/ Build Contextual Intelligence ↳ Look beyond numbers ↳ Understand the broader business ecosystem 6/ Simplify Technical Complexity ↳ Explain like you're talking to a curious 5-year-old ↳ Cut the jargon, focus on clarity 7/ Learn Business Dynamics ↳ Study industry trends ↳ Know what keeps executives up at night 8/ Network Strategically ↳ Build relationships across departments ↳ Be more than just the "tech person" 9/ Continuous Learning ↳ Stay curious about business strategy ↳ Read beyond technical journals 10/ Quantify Your Value ↳ Track how insights drive decisions ↳ Prove your worth beyond code Technical skills get you hired. Strategic communication gets you promoted. Combine analytical depth with business acumen, and you become unstoppable. ♻️ Repost to help data professionals unlock their true potential. Follow Tuan Sihan for frameworks that turn data nerds into business heroes.

98

31 comentarios

I worked with enums on daily basis. And I'm sharing my 4 best practices to keep your project clean: - Explicitly specify storage type - Use description attributes for display names - Helper method for description attribute - Safe parsing with TryParse What would you add to this list?

1317

81 comentarios

Anthropic has taken many of the core concepts of Claude Flow and integrated them directly into its new Claude Agent SDK. In my Flow platform, I had to build orchestration around features like artifact tracking, retries, and context persistence because the SDK didn’t provide them. Now those same ideas are native. Tool governance, artifact durability, and context checkpoints are primitives in the SDK. For example, in Claude Flow I wrote custom routines to retry failed tool calls with exponential backoff. The SDK now includes built-in retry handling. I built artifact management so outputs could be stored, versioned, and reused. The SDK now provides artifact durability out of the box. I had to wire in checkpoints to let an agent recover from mid-flow errors. The SDK now exposes context checkpoints directly. This validates the Flow approach. Structured cycles weren’t a workaround, they were the correct abstraction. Developers can now spin up long-running agents without bolting on any orchestration. The friction is lower, the foundation is stronger. At the same time, Anthropic is absorbing practices we pioneered back into its stack. Not that they have given any acknowledgement. Subagents? That was literally our term. The good news is this makes agents easier for newcomers to build, but it also sets tighter boundaries on how Claude agents are expected to work.

181

33 comentarios

Heads up, Android devs! 👋 So I just finished diving deep into Android 15's new 16KB page size requirement, and honestly? It's bigger than most people realize. Starting November 1st 2025, if your app targets API 35+ and uses ANY native libraries (your own .so files or ones from SDKs), you're going to need to rebuild them. No exceptions. I'll be real with you - when I first heard about this, I thought great, another compliance hoop to jump through. But after testing it out, I'm actually excited about the performance improvements. We're talking: - Apps launching 30% faster - Camera opens 4-6% quicker - Way less CPU strain - Better battery life The tricky part? Figuring out if you're even affected. Pure Kotlin/Java apps are mostly fine, but if you're using any third-party SDKs, there's a good chance they bundle native code you don't even know about. I spent the last few weeks testing this migration and put together a complete walkthrough - everything from updating your build tools to testing on actual devices. The deadline feels far away, but trust me on this one: don't leave it until October. I've seen too many last-minute scrambles with Android updates. Full guide is in the comments if you want to get ahead of this 📝 Anyone else already started preparing for this? Would love to hear what challenges you're running into. #AndroidDev #Android15 #MobileDevelopment #android

340

21 comentarios

3 top tips for Junior Software Developers: 1. Never let a mentor touch your keyboard: If you can't find something or don't know what to search for, have them guide you, not do it for you. Embrace the struggle. 2. Present solutions, not just problems: As a junior engineer there will be a lot you don't know, can't do or haven't experienced. Communicate how you think you might be able to overcome them, or what you might need to help solve it. Go beyond 'I don't know'. 3. Get involved with other areas of the business: One way to really stand out is to have domain knowledge deeper than code. Ask to spend a week answering calls with Customer Service, take a day to learn how Marketing does outreach, and walk through your Client archetype with the Sales team. I bitterly miss the feeling of unending learning and wonder that comes with being a Junior Software Engineer.

60

4 comentarios

Stop writing messy C# code that makes your team cry. I've spent 13+ years watching developers struggle with the same patterns. Over time, I've realized this: Clean code isn't about grand rewrites. It's about consistent, small improvements that compound over time. Let me share the 6 steps I use daily to turn spaghetti into systems people actually want to maintain: 1. Remove unused code ↳ Dead code is cognitive overhead ↳ If it's not running in prod, it shouldn't be in your codebase ↳ Git has your history - let it go 2. Simplify nested if-else ↳ Guard clauses at the top ↳ One level of nesting max ↳ Extract complex conditions into well-named methods 3. Reduce method length ↳ Each method should do exactly one thing ↳ Extract till it's crystal clear 4. Automate repetitive tasks ↳ If you've done it three times, automate it ↳ Create snippets for common patterns ↳ Let tools handle the boring stuff 5. Improve names to add clarity ↳ Variables should tell what they hold ↳ Methods should be verbs ↳ Classes should be nouns 6. Improve project structure ↳ Related code lives together ↳ Clear boundaries between modules ↳ Solution structure matches domain concepts What devs often get wrong is that they wait for permission to write better code. But you don't need: - A dedicated refactoring sprint - Approval from your boss - The perfect architecture You just need to make one small improvement today. Then another tomorrow. Because clean code isn't a destination. It's a daily practice. Start small. Stay consistent. Watch your codebase transform.

36

2 comentarios