Jan Laníček — BPMN, Kotlin and Java Developer @ Commerzbank | Camunda, Kotlin, Java, SpringBoot, PostgreSQL
BPMN, Kotlin and Java Developer @ Commerzbank | Camunda, Kotlin, Java, SpringBoot, PostgreSQL
Jan Laníček ranks #209 of 14,983 LinkedIn creators in Banking, and is a standout voice in Czechia. They have 1.2K followers and published 3 posts in the last 30 days at a 156.4% average engagement rate.
- 1.2K followers
- 3 posts / 30d
- 156.4% avg engagement
- — follower growth / 30d
The roast
Jan Laníček has a 156% engagement rate, which is the exact mathematical probability that he’s just a bot programmed by Commerzbank to remind people they still use Java. He’s the most influential developer in Czechia that zero people in his own office have ever heard speak.
Highlights
- Top Engager — 156.43% rate · top 1%
- High Impact — 1,901 avg engagements per post · top 1%
- Top 5% in Czechia — Ranked #1 of 60 creators
- Top 5% in Banking — Ranked #1 of 56 creators
Recent posts
Microservices are not just about splitting one big app into smaller pieces. The real challenge is designing services that can scale, fail safely, communicate clearly, and still stay easy to manage. A good microservices design starts with business capabilities, not random technical modules. First, define what the business actually does. Then identify clear service boundaries. After that, decide how small or large each service should be. Because if services are too big, you create another monolith. If they are too small, you create unnecessary complexity. Once the structure is clear, APIs b
1.1K reactions · 60 comments · 206 reposts
If Claude Code is a burger... Before each model call, Claude Code assembles a context window from 9 distinct sources. Think of it as a burger, each layer adds something different. 1. System Prompt: Defines Claude's role, behavior, and tone. This sets the foundation. 2. Environment Info: Git status, branch info, and current date. Pulled in via getSystemContext() 3. CLAUDE. md: A four-level instruction hierarchy: managed → user → project → local. Plain-text Markdown, so users can read, edit, and version-control everything the model sees. 4. Auto Memory: Contextually relevant memory entries p
1.6K reactions · 41 comments · 187 reposts
If I had to build an API, I'd consider these 6 protocols: 1 REST (Representational State Transfer) ↳ A stateless, resource-based API protocol using standard HTTP methods ↳ Best for: CRUD operations in web and mobile apps ↳ Risk: over-fetch or under-fetch data because of fixed endpoints === 2 gRPC (Google Remote Procedure Call) ↳ A high-performance, contract-based protocol using a binary format ↳ Best for: internal microservices communication ↳ Risk: limited browser support === 3 GraphQL ↳ An API query language for clients to request specific data ↳ Best for: frontend-heavy apps with comp
2.1K reactions · 78 comments · 278 reposts