Hi @eToro am I the only one having issues with login/write code screens?
1st try: code was wrong.
2nd try: pressing on phone call option fails.
Been like this since this morning. Any health page so i can monitor when the issue is solved?
We hired a backend guy recently who didn’t know half the buzzwords.
No Saga, no CQRS, shaky on K8s. On paper, easy reject.
Then we gave him a real prod-ish bug:
sporadic 500s, p95 spikes, only on one endpoint.
He did 3 things:
1. Asked for repro + timeline. “When did it start? What changed? Any new feature release?”
2. Cut the problem space. Logs first, then metrics, then a single failing request ID.
3. Formed a hypothesis, tested it, wrote down what each result would mean.
Found it in 25 mins:
connection pool exhausted from one code path leaking retries + no timeout.
I’ll take that over memorized concepts anyday.
This is what people don't get right, companies hire for fundamentals + debugging. You can teach patterns. You can’t teach calm thinking under failure.
Today, we’re rolling out ACP Agent Registry in JetBrains IDEs.
Instead of manually setting up coding agents one by one, you can now browse what’s available and install them with a single click. Try different agents, see what’s best for your workflow, and switch as needed.
Thank you to @zeddotdev for a great collaboration 🙌
Full details in the blog post 👇
https://t.co/PGncxFYvQz
Why offset pagination collapses at scale and how a production-grade cursor design keeps PostgreSQL fast, predictable, and boring.
https://t.co/8H33qKXZwH
Just a reminder, the Quarkus Community Call happening tomorrow (January 20th at 2pm Paris time).
This week's topic: Office Hours - Ask Us Anything!
Join via Google meet:
https://t.co/Milefdf4XX
If you want to crack interviews, you MUST master System Design.
Most candidates practice random problems…
Top companies ask very specific ones.
This cheatsheet brings together 35 real system design questions asked at companies like Google, Meta, Amazon, Uber, Netflix, Stripe, Airbnb, Microsoft, and more.
These cover every core area you’re expected to know:
✅ Distributed Systems
– Metrics logging & aggregation
– Distributed queues (RabbitMQ/Kafka)
– Stream processing engines
– Distributed tracing
– Job schedulers & notification systems
✅ High-Scale Architecture
– Rate limiters
– Surge pricing (Uber/Lyft)
– A/B testing systems
– Price alerting engines
– Monitoring cluster health
✅ Real-World Applications
– Dropbox/Google Drive design
– Hotel booking systems
– ETA prediction for Uber
– Calendar systems
– File downloaders
– Photo-sharing platforms
✅ Advanced Topics
– Dependency injection frameworks
– Control plane for distributed DBs
– Marketplace features
– IoC systems
– Complex pipeline orchestrators
If you are preparing for SDE2+, Senior Engineer, System Design rounds, or Architect roles, this list should be your roadmap.
Save this. Practice each one deeply. Build mental patterns.
System Design is not about memorizing, it’s about thinking in systems.
The biggest trap for Senior Engineers interviewing right now?
"Fundamentals."
Companies are starting interviews with CS 101 questions you haven't touched in 5-10 years.
The logic: "We need to verify the basics before we discuss architecture."
The reality: You look incompetent because you forgot the textbook definition of polymorphism.
It logical for them, but it's annoying as hell for you.
But from my desk, I can tell you this isn't changing.
You have a choice:
• Complain that the system is broken.
• Spend time relearning the basics and get the offer.
You can be right, or you can be hired.
Our Black Friday sale ends at midnight tomorrow night, which means this is your final opportunity to access career-defining training at a significantly reduced cost.
👇
🅰️ #Angular 21 is here!🎉
The highlights:
✨ Zoneless is now the default
🧪 Signal Forms (experimental)
⚡ Vitest replaces Karma/Jasmine
✅ angular/aria for accessibility
🤖 MCP server & AGENTS․md for AI assistants now stable
More details here:
https://t.co/8xRALrbKCo
Explore how JUnit 6 streamlines test execution, boosts performance, and modernizes Java testing in Quarkus projects built on Java 17 and beyond.
https://t.co/wh7xXhqS7Y
I've migrated the first application to Spring Boot 4. The two things that I had to change were both releated to testing.
First, I had to add the WebMVC test dependency:
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-webmvc-test</artifactId>
<scope>test</scope>
</dependency>
Then @WithMockUser stopped working in combination with MockMVC and Webclient. There, I had to add springSecurity() to the config.
WebClient webClient = MockMvcWebClientBuilder.webAppContextSetup(context, springSecurity()).build();
Other than that everything works! Great job Spring Team!
I'm documenting Spring Boot 4 features with:
✅ Code examples
✅ Video tutorials
✅ Blog Posts
All organized in one central repo 👇
https://t.co/fqiCgYpB0Q
📢 Kotlin 2.3.0-RC is out! Here are some of the highlights:
✅Language: more stable and default features, a new checker for unused return values, and changes to context-sensitive resolution.
✅Kotlin/JVM: support for Java 25.
✅Kotlin/Native: improved interop through Swift export and type checks on generic type boundaries enabled by default.
✅Kotlin/Wasm: fully qualified names and new exception handling proposal enabled by default.
✅Kotlin/JS: new experimental suspend function export and LongArray representation.
✅Gradle: compatibility with Gradle 9.0 and a new API for registering generated sources.
✅Standard library: stable time tracking functionality.
Try it out: https://t.co/R8NbCpUFO4