🍂 Hello Fullstackers!
September is the month when ideas turn into real progress. Holidays are behind us, projects are gaining momentum, and every commit feels like a step toward something bigger.
💡 “Great things are not done by impulse, but by a series of small things brought together.” — Vincent van Gogh
In this edition, you’ll find your usual mix of:
🔄 Kafka tips to strengthen your pipelines
👥 A team spark to boost collaboration
☕ Java insights to polish your craft
📋 A Scrum bite to keep agility sharp
☸️ Kubernetes wisdom for smoother ops
😂 And the classic dev joke to lighten the mood
Let’s embrace the season of focus and build great things together. 🚀
#kafka
Can you search for specific data inside a Kafka topic?
✅ Yes
❌ No
Answer:
❌ No.
👉 Kafka is made for data streaming, not for queries or search.
#team
Onboarding of a new team member?
Helping with the onboarding of new team members is crucial for the success of your Scrum team. Here are some steps you can take to assist in their onboarding:
1. Provide a Warm Welcome:
Start by welcoming the new team members with a friendly and inclusive attitude. Make them feel like they are part of the team from day one.
2. Share Documentation and Resources:
Share any relevant documentation, coding guidelines, and process documentation with them. This could include coding standards, architecture diagrams, and project documentation.
3. Set Up Development Environments:
Help them set up their development environments. This includes installing necessary software, configuring version control systems, and granting access to code repositories.
4. Pair Programming:
Encourage pair programming sessions with both senior and junior developers. This helps in knowledge transfer, builds camaraderie, and ensures that best practices are followed.
5. Code Reviews:
Explain your team's code review process. Encourage them to participate in code reviews and provide constructive feedback.
6. Shadowing:
Allow junior developers to shadow senior developers on tasks. This can be a great learning experience and help them understand the codebase and development practices faster.
7. Scrum Process Explanation:
If the new team members are not familiar with Scrum, provide them with a clear explanation of the Scrum framework. Discuss roles, ceremonies, and artifacts.
8. Introduction to Stakeholders:
Introduce them to key stakeholders and team members outside of your immediate Scrum team. This can include product owners, testers, and other teams they may need to collaborate with.
9. Answer Questions and Offer Support:
Be approachable and available to answer any questions they might have. Make it clear that they can come to you or other team members for help and guidance.
10. Encourage Learning:
Encourage ongoing learning and skill development. Share resources, recommend books or online courses, and discuss opportunities for growth within the team.
11. Regular Check-Ins:
Schedule regular check-ins to see how they are adapting to the team and if they have any concerns or need additional support.
12. Feedback and Improvement:
Be open to feedback from the new team members about the onboarding process. Use their feedback to continuously improve the onboarding experience for future team members.
13. Scrum Master Support:
Work closely with the Scrum Master to ensure that they are aware of the team's needs and that they can provide the necessary support and facilitation of Scrum processes.
Onboarding is an ongoing process, and it may take some time for new team members to fully integrate into the team and become productive. Be patient and supportive, and foster a culture of learning and collaboration within your Scrum team.
#java
🚀 Java 25: big, drop-in performance wins
From the latest SPECjbb2015 numbers (higher is better):
Versus older LTS:
+113% critical jOPS vs JDK 8 🤯
+31% max jOPS vs JDK 17 🔝
Versus the previous LTS:
+10% critical jOPS vs JDK 21
+5% max jOPS vs JDK 21
The killer feature? No app recompile needed — just run your workloads on JDK 25 and enjoy lower tail latency and more headroom under peak load.
Are you planning a JDK 25 rollout for your services/batch jobs? Which distribution will you use?
#Java25 #JDK25 #Performance #SPECjbb2015 #JVM #Latency #Throughput #JavaEngineering
Go further with Java certification:
Java👇
Spring👇
#scrum
Tired of shipping “requirements” nobody uses? 😬
What if User Stories started as hypotheses tied to clear OKRs, validated with tiny experiments—not big-bang releases?
In this quick read, I recap David Hawks’ take on remodeling User Stories so teams focus less on output and more on customer outcomes.
From requirements ➜ hypotheses
From delivery-only ➜ risk-driven experiments
From stakeholder asks ➜ measurable objectives 🎯
#Scrum #OKR #Agile #ProductManagement #UserStories #Lean #HypothesisDrivenDevelopment
#kubernetes
❓ How do you allow external access to the Kubernetes API Server for only some namespaces?
Pick one:
- RBAC roles and bindings
- API flag --enable-namespaces-isolation
- Ingress Controller to the API Server
- NetworkPolicy for API Server
✅ Correct Answer: 1. RBAC roles and bindings
💡 Why? RBAC controls who can access the API and what they can do. With roles and role bindings, you can give permissions only to the namespaces you choose.
❌ Why the others are wrong:
2. API flag → That flag doesn’t exist.
3. Ingress Controller → Ingress handles HTTP traffic to services, not the API Server.
4. NetworkPolicy → Works inside the Pod network, not on the API Server.
🎰 Vibe coding the Las Vegas for developers
#VibeCoding is basically Las Vegas for developers.
- You don’t walk in with a spec… you buy tokens. You don’t compile… you hit Generate.
- Sometimes you land a jackpot (bug-free app) — sometimes you get pure nonsense that won’t even run.
- Instead of flashing lights, you get: “Great idea! Of course! Here’s the perfect solution!”
- You don’t say “I have a strategy”… you say “I’m a prompt engineer.”
- And when things go sideways: “One more prompt and I’ll win it all back!”
- In the end? Curosr always wins. 😉
My take: treat AI like a high-roller table with limits — guardrails, tests, and reviews. Let it amplify your craft, not gamble your codebase away.
What’s your biggest AI win… or most expensive “one more prompt” moment?
#Java #Spring #AI #GenAI #SoftwareEngineering #CleanCode #Testing #DeveloperLife #Productivity #LLM #PairProgramming
Go further with Java certification:
Java👇
Spring👇