Norman Coloma García

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

𝘞𝘩𝘺 𝘠𝘖𝘜𝘙 Automation 𝘧𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬 𝘸𝘪𝘭𝘭 𝘍𝘈𝘐𝘓 𝘪𝘯 6 𝘮𝘰𝘯𝘵𝘩𝘴 (𝘢𝘯𝘥 𝘩𝘰𝘸 𝘵𝘰 𝘧𝘪𝘹 𝘪𝘵) I just audited a $50M company's automation framework. Result? 73% of their tests were failing randomly. Their CTO asked me one question: "How did we go from 10 passing tests to complete chaos?" The Brutal Truth: 85% of Selenium Projects Die the Same Death Month 1: "Our automation is amazing!" Month 6: "Why does everything break when we deploy?" Here's what kills every framework (and the fix): 1️⃣ The "Everything in One Folder" Disaster ❌ Death pattern: UI, API, utils all mixed together ✅ Fix: Dedicated packages → UI, API, POJO, services separated Reality check: Good teams onboard new devs in 2 hours, not 2 weeks. 2️⃣ The "Hardcoded Hell" Problem ❌ Death pattern: URLs, data, timeouts scattered everywhere ✅ Fix: Environment property files + externalized test data Game changer: Switch DEV→QA→PROD with one command. 3️⃣ The "No POJO = No Scale" Trap ❌ Death pattern: Raw JSON strings, manual API payloads ✅ Fix: Request/Response POJOs + schema validation Impact: API tests become 10x more maintainable. 4️⃣ The "Debug Nightmare" Issue ❌ Death pattern: "Test failed" with zero context ✅ Fix: Extent Reports + screenshots + API logs Truth: Debug time drops from 2 hours → 5 minutes The Framework That Actually Scales I've built a production-ready structure that includes: 🏗️ Proper separation of UI/API/POJO layers 🔧 External configurations for all environments 📊 Rich reporting with screenshots & metrics 🚀 CI/CD ready with Docker & Jenkins support 🎯 BDD structure that business teams understand The Bottom Line: Stop building "quick automation scripts." Start building software systems that scale. Your framework should work at test #10 AND test #1000. Want the complete folder structure? 👇 Comment "𝑭𝑹𝑨𝑴𝑬𝑾𝑶𝑹𝑲" and I'll send it to your inbox! Found this helpful? Share with someone struggling with flaky tests! 🚀 -x-x- Full Stack QA & Automation Framework Course with Clearing SDET Coding Rounds: https://lnkd.in/g7tn6Uif #japneetsachdeva

157

10 comentarios

From Developer to CEO Part 03: 5 to 10 years of experience Congratulations, you’re now a senior developer. But you’re not a senior just because you’ve reached 5 years of experience. You’re a senior because you’ve seen more problems— and you know how to prevent them. At this stage, you should be able to build software from A to Z. But your main focus must now shift to business impact. Not just how to code, but how to solve real business problems. Code shouldn’t be your challenge. Code should be your tool—to deliver value. For that, start asking the right questions: • What’s the real problem the customer is trying to solve? • Why does the client need this feature? • What’s the expected benefit for their business? • Is there a better solution? You’re not just a developer anymore. You should become a technical partner to your clients, not just someone who takes orders. Your new mindset: 👉 How can I maximize my customer’s success? If you follow these tips, you’ll level up faster. ⸻ After 20+ years in web development, I’m sharing what I wish I had known when I was younger. This post is a follow-up to Julien Rajerison’s post. Tomorrow, we’ll talk about developers with 10+ years of experience. ⸻ You’ve got this. I’m Toky RABESON. I’m a seasoned web developer.

94

4 comentarios

'We only hire senior developers' Congrats! You're building a time bomb. Here's why: Senior-only teams create: • Echo chambers of outdated practices • Zero knowledge transfer • Expensive solutions to simple problems • 10 architects, no builders What you're really missing: • Fresh perspectives • Hunger to learn • Questions that challenge assumptions • Future leaders The brutal truth: • Your 'senior' requirements are fear-based • Your '10 years experience' is arbitrary • Your 'no junior devs' policy is expensive technical debt Why this matters: • Innovation needs new eyes • Growth requires teaching • Sustainability demands succession • AI is leveling the experience gap anyway How to fix it: 1. Hire for potential, not just experience 2. Create mentorship structures 3. Balance your team pyramid 4. Accept that juniors today code better than seniors did 5 years ago Remember: Today's 'risky' junior is tomorrow's 'savior'. What's your take on the senior-only trend? Drop your thoughts below 👇 *** P.S. If your entire team is senior developers, who's asking the 'stupid' questions that prevent stupid mistakes?

93

23 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

MediatR is powerful. But here's the truth: 👉 Using it for a simple project is like using a chainsaw to slice bread. Technically possible, but massively overkill. If your team and your app are small, chances are you don't need pipelines, handlers, and all the extra complexity. Stick to direct calls, filters, and middlewares — you'll ship faster with less cognitive load. 💡 The real flex? Choosing the simplest architecture that solves the actual problem.

35

3 comentarios

At the last weeks, I have been working in a microservices ecosystem combining C++ backend with TypeScript orchestration. I had this idea after some months working with AWS lambdas and thinking about on how to implement a toy project to learn and practice. Architecture Highlights: - Service Mesh: Independent C++ microservices with RESTful APIs - API Gateway: TypeScript-based routing and load balancing with auto-routing to C++ services - PM2 Process Management for production-grade service orchestration - Database Layer: PostgreSQL with connection pooling and migrations - Configuration Management: Multi-tier config with environment isolation DevOps Engineering: - CI/CD Pipeline: Automated build, test, and deployment - Infrastructure as Code: Self-hosted GitHub Actions runners - Security: Secrets management with environment-specific configs - Monitoring: Health checks and performance baselines Development Experience: - IDE Integration: VS Code with IntelliSense and test discovery - Dependency Management: Git submodules for third-party libraries - Testing Strategy: Unit tests, integration tests, and lab environment - Documentation: Comprehensive setup and deployment guides Performance Benefits: - Native C++ execution for compute-intensive operations - TypeScript flexibility for business logic and routing - PostgreSQL optimization for data consistency and performance Production Features: - PM2 Orchestration: Auto-restart, load balancing, and process monitoring - Hybrid Architecture: C++ for compute-intensive tasks, TypeScript for HTTP handling - Smart Configuration: Multi-tier config system (JSON → .env → env vars) - Git Submodules: Clean third-party dependency management - Health Checks: Automated service health monitoring and alerting - Zero-downtime deploys: PM2 graceful restarts with health validation Technical Roadmap: - Phase 1: Structured logging system with centralized aggregation and PM2 aggregation - Phase 2: Automated semantic versioning with GitHub Actions integration - Phase 3: Development framework and scaffolding tools for rapid microservice creation - Phase 4: Complete observability stack (metrics, tracing, alerting) Engineering Principles: - Performance-first: C++ where speed matters, TypeScript where flexibility wins - Developer Experience: Tooling that accelerates development without sacrificing quality - Production-ready: Security, monitoring, and deployment automation from day one - Scalable Architecture: Each component can evolve and scale independently This project showcases the evolution from traditional web stacks to hybrid architectures that leverage the best of both worlds: C++ performance with modern web development practices. Follow the link to github: https://lnkd.in/d3CXhngV #systemsarchitecture #cpp #microservices #performanceengineering #devops #postgresql #typescript #softwarearchitecture #backend #cloudnative #AWS

36

11 comentarios

Features are built, tested, ready to ship. Code review passes. Then someone asks: "Do we have docs for this?" and suddenly, documentation becomes a scramble. The typical flow is that we either write it from memory (and risk getting details wrong), or spend hours reverse-engineering our own code to explain what it does. I just experimented with using Depot Claude remote sandboxes to automate documentation workflows, and the results were surprisingly efficient: - Claude analyses your code changes automatically.  - Check your existing docs repo for gaps.  - Generates informed drafts based on actual usage patterns.  - Creates pull requests ready for review. - The entire Claude session persists and is shareable with your team. This helps the reviewers resume the exact session, ask Claude directly, and iterate within the sandbox. All the context, reasoning, and decision-making is preserved. Want to learn more about this and understand how Depot is using AI agents to streamline docs workflows : https://fandf.co/4o5NKN3 Thanks to Depot for partnering on this content piece. #Depot #Claude #AI #Tech #Collab

443

20 comentarios

Most junior engineers think they’ll be rewarded if they: → close lots of tickets → stay late and jump on every bug → write clever code and push big PRs But you’re rewarded for being the person who: → ships predictable outcomes, not surprises → prevents incidents before they happen with tests, alerts, and runbooks → makes the team faster with clear docs, small PRs, and crisp reviews → understands the user and ties work to a metric the business cares about → reduces cost and risk: cleaner designs, fewer moving parts, simpler ops Hard fact: believing “more hours + more tickets = growth” is a recipe for burnout and stalled careers. You’ll feel busy, but you won’t be valuable. Do this instead: → Pick one metric to move this quarter: p95 latency, crash rate, signup conversion, cloud spend. → Own one thing end to end: read code paths, write a tiny RFC, add dashboards, add alerts, add tests. → Kill recurring pain: automate a flaky deploy step, fix a flaky test, script a one-click local setup. → Review like a pro: spot risk, ask for data, suggest simpler designs, add examples to docs. → Learn the domain: sit with PM, Support, or Data weekly; collect real user stories. → Teach one person: pair once a week, share your notes, leave the project better than you found it. Yes, work hard. Give it your all. But keep asking, “What action creates the most impact for my team and our users today?” It may not feel like much each day. Some days it is just one small improvement. Stack those improvements for 90 days and you become the person people rely on. Stack them for a year and you become the person they plan around. You’re not paid for sweating more. You’re paid for being hard to replace.

811

40 comentarios