Marco Portillo

AngularAI An experimental, browser-first agent that truly understands your Angular app. It has full context to make prototyping easier: - Source files & config - Runtime state & internal data structures This enables hyper-contextual debugging, prototyping, and more. Check out a quick demo and let me know what you think! #ai #ml #machinelearning #agents #softwaredevelopment #programming #webdev #webdevelopment #webdev #llm #llms

1.108

58 Kommentare

The Angular job market in 2025? Not what most people expect. I went through over 1,200 job ads from top tech hubs here’s what stood out: 🔥 The Upside: 💸 Salaries typically range from $120K–$180K — about 15% more than most React roles 💼 60% of openings target senior developers 🌍 Remote-friendly companies (especially in enterprise sectors) lean heavily toward Angular 🧊 The Flip Side: 📉 Only 2–3 fresh Angular listings per day (compared to 15+ for React) 🧠 Most roles ask for 5+ years of experience 🏢 Angular demand is strongest in finance, healthcare, and large-scale enterprise apps 🧠 My Perspective: Angular isn’t fading — it’s focusing. While React rules the startup scene, Angular quietly powers the core systems behind major industries. ✅ Less noise ✅ Higher expectations ✅ Greater reward for those who truly master it Developers seeing success with Angular tend to have: Strong architectural knowledge Deep RxJS skills Solid grasp of enterprise design patterns Experience with performance tuning at scale In short: Angular is shifting toward specialization over popularity. If you're thinking about doubling down on Angular… this could be the ideal time to stand out. #Angular #WebDevelopment #FrontendCareers #EnterpriseTech #RxJS #AngularJobs #DevCareers #SeniorDev #TechTrends2025

82

5 Kommentare

The forgotten Enum in the #Angular ecosystem Did you know that Angular has a dedicated Enum for HTTP status codes❓ It's a very useful Enum and I rarely see people using it. Mostly, I see people using "magic number" to check for specific status codes🫷 if (response.status === 401) {  // do something } At first glance, it appears to be fine. But over time, this kind of "magic number" usage becomes a silent code smell 👃 — especially in large applications, teams, or when you revisit the code months later. Now imagine seeing this instead: if (response.status === HttpStatusCode.Unauthorized) {  // do something } 📌 Instant understanding. 📌 Self-documenting code. 📌 No need to remember that 403 = forbidden, or 409 = conflict. You can find the full Enum here: https://lnkd.in/eKT74QdJ It's based on: https://lnkd.in/exT9upad

321

35 Kommentare

The discard operator _ in C# might look simple, but it’s a powerful way to make your code cleaner and more efficient. It allows you to ignore values you don’t actually need, reducing noise and improving readability. Where You Can Use _: ↳ Task Results Skip capturing results from async operations when they aren’t required. ↳ Pattern Matching Ignore parts of a match that don’t matter in your logic. ↳ Tuples Discard tuple members you don’t need without creating unused variables. ↳ Out Parameters Eliminate unnecessary dummy variables when a method provides extra outputs. ↳ Expression Results Quietly ignore return values that don’t need handling. Why It’s Useful: ✅ No extra variables cluttering your methods ✅ Signals to other developers that a value was purposely ignored ✅ Lets the compiler avoid unnecessary assignments Though often overlooked in async tasks and out parameters, using _ can make your code much more elegant! 💡 Have you applied the discard operator in your C# projects? ——— ♻ Share this post if you found it useful! 👉 Elliot here — Sharing insights on modern engineering, AI/ML, & tech. #dotnet #csharp #cleancode #coding #tech

159

9 Kommentare

If you're conducting frontend developer interviews, it's time to stop asking these types of questions: 1. "Guess the output" questions where there's no real-world value, but you're expecting the candidate to know obscure edge cases. Example: let x = 10, a, b; — now what’s the type of a? Is it let or const? 2. Pre and post-increment puzzles like ++a + --b. These are rarely used in real-world code, and instead of assessing actual skills, they often just confuse candidates without offering meaningful insights. 3. Expecting candidates to fully implement a machine coding round—including both styling and complete functionality—within 30 minutes. Let’s be honest, very few people can do that under pressure, and even fewer are expected to in real-life projects. 4. Deeply nested promise chains and then asking candidates to guess the output. Who writes or maintains code like that in production today? Interviews should be realistic. It’s okay to include a few edge cases or tricky scenarios, but they shouldn't be the deciding factor in evaluating a candidate's capabilities. What do you think? Do you still include pre/post-increment questions in your interviews? follow me and I will help you to find you're dream job: Vasanth Bhat

82

4 Kommentare

🍃 Last week, I wrote the last part to introduce the most important features of the latest version of Spring Boot (3.4), the following are the links for the four parts of these reviews: 1️⃣ Structured Logging (https://lnkd.in/d76kqMSZ) 2️⃣ MockMvc AssertJ Integration (https://lnkd.in/dPfdWjHd) 3️⃣ Multiple Docker Compose files (https://lnkd.in/df9RYeTY) 4️⃣ New Bean Validation behavior for Configuration Properties (https://lnkd.in/d43WiM-S) ❓ What feature are you looking forward to seeing in the next version of Spring Boot?

134

3 Kommentare

Top things I learned on LinkedIn recently: - TDD is sh*t - TDD is awesome, you just don't know how to use it - Learn Clean Code - Clean Code is cargo-cult nonsense - Learn Code Patterns - Patterns are cargo-cult nonsense - QA is a must for any serious org - QA or having testers is last-century gatekeeping nonsense - Developers can't test - Developers CAN test - Cucumber is sh*t (this one's settled) Thank you, people on LinkedIn, for these nuggets of wisdom 🙏 #tdd #programming #softwaretesting #qa

241

123 Kommentare

When reading nested object properties, you can use multiple layers of destructuring. However, I don't recommend it because: - if any nested property is undefined, your code will crash with an error - to prevent errors, you need default values, which makes the code hard to read - deep nesting hurts readability That's why I prefer the standard approach using optional chaining and default values. However, when you have just one nested level, object destructuring is fine to use. - Stè

35

7 Kommentare

The Angular team is now working on a new Signal primitive called Deep Signal, that lets you reactively access and update nested properties within Signals. 🎯 This means managing nested state in Angular will become much simpler, cleaner, and more performant, without the need for complicated workarounds. In my latest article, I explore what Deep Signals are, how they work, and why they will improve our Angular codebases. If you want to stay ahead and get ready for this upcoming feature, don’t miss it! 👉 Read more here: https://lnkd.in/eWsTq4uy #Angular #WebDevelopment #Frontend #Signals #StateManagement #DeepSignal #AngularSignals #TechInnovation #Programming

185

12 Kommentare

If Go and Node.js were roommates… Node: "I made you a REST API, here’s 42 npm packages you’ll never use." Go: "I rewrote it in 20 lines and lowered the AWS bill." Node: still debugging async hell Go: already deployed and chilling Switching to Go isn’t just a tech decision—it’s a lifestyle choice. Choose peace, choose performance, choose Go 🐹 #golang #nodejs #devhumor #cloudengineering #weekendvibes

548

148 Kommentare

Yesterday, I talked about how to throw errors like a pro in Node.js, let’s take it further - handling errors in middleware. Most Node.js developers have one big error middleware that looks something like this: - Checks error type - Sends email to support - Logs the error - Sends the error to monitoring tools - Maybe even calls next() for some edge case And it’s all in one function. This works but it gets messy fast and It’s harder to test, scale, or read. A cleaner way is to break those actions into small services or functions. Then create an ErrorHandler class that runs them all. This way, your middleware stays clean, actions reusable and everything becomes easier to manage. See attached image for illustration. If your application needs another error tracking like slack notifications for example, it's easy to add the service. In the next post, I'll address graceful process exits and catching unhandled errors. stay tuned. #devs #nodejs

28

3 Kommentare

👎 LLMs struggle with coding in Angular. Despite Angular's rapid evolution, most models can’t keep up. Developers might lean towards frameworks that “play nicer” with AI just to boost productivity. Curious to hear your thoughts: is this a real risk in the adoption of Angular?

171

76 Kommentare

📝 Just published: "Things I Wish I Knew When I Started Testing Spring Boot Applications" After years of learning the hard way, I'm sharing the testing insights that would have saved me countless hours of frustration: ✅ The hidden testing toolkit that comes with EVERY Spring Boot app ✅ Why loading the entire application context is slowing down your tests (and what to do instead) ✅ How to use Spring Boot's "test slicing" for lightning-fast feedback loops ✅ Common JUnit 4/5 pitfalls that trip up even experienced developers Testing shouldn't be an afterthought, but many of us weren't taught HOW to test effectively - especially with Spring Boot's powerful (but sometimes confusing) testing support. Whether you're new to Spring Boot or looking to optimize your existing test suite, these practical insights will help you write better tests in less time. Read the full article here: https://lnkd.in/dDqVFzqC #SpringBoot #JavaDevelopment #Testing #SoftwareQuality #SpringFramework #Java

16

🔍 How does JSON.parse really work? We use JSON.parse() all the time, but most developers don’t think about what the parser is actually expecting when it looks at the very first character. According to the JSON spec, the input must represent a valid JSON value. That means the string must start with one of these: { → for an object [ → for an array " → for a string A digit (0–9) or - → for a number t, f, n → for true, false, or null Anything else at position 0 immediately fails. ✅ Correct inputs include objects, arrays, strings, numbers, booleans, and null. ❌ Incorrect inputs include things like unquoted strings, undefined, single-quoted keys, or even an empty string. The best part: the error messages are very specific. That’s the engine telling you exactly why it failed and where. I think understanding how JSON.parse works under the hood helps you debug much faster, especially when dealing with malformed API responses or debugging serialization bugs. #JavaScript #WebDevelopment #Frontend #React

41

3 Kommentare