Search
1000 results for “junit”
-
A Comprehensive guide to Spring Boot 3.2 with Java 21, Virtual Threads, Spring Security, PostgreSQL, Flyway, Caching, Micrometer, Opentelemetry, JUnit 5, RabbitMQ, Keycloak Integration, and More!
-
Upgraded to Spring Boot 3 (yes i am late). Found out `@PreAuthorize is a decorative corpse`. You now need `@EnableMethodSecurity(prePostEnabled = true)` to reanimate it. Laughable.
Thankfully, I had tests. Which is ironic, because I wanted to test my code, not Spring’s trust issues.
This dev experience? Trash tier. Writing one annotation to enable another? That’s not configuration—that’s a scavenger hunt in a haunted house. 👻🔍
Annotations should do something when you use them. Not wait for permission like a guilty intern. Imagine you would have to add a Junit annotation to tell, that test failures are thrown.
Should’ve just gone full auth(request) at every endpoint. More stable. Less betrayal.
#SpringBoot3
#WhyTrustWhenYouCanTest
#AnnotationAnxiety
#CodeOrCursedRitual
#IDidntChooseTheBugLife
#PreAuthorizePostMortem
#FrameworkGaslighting
#coding
#programming -
Эта неделя в мире Java (21 ноября)
Все сенсации, интриги, расследования, которые вам нужны 21 ноября. Брайан Гёц — гриб (видео под катом, интервью с @boomburum ) jHipster требует Java 21 и не согласен на меньшее Живой мастер-класс по JUnit от JUnit-джедая Депо поездов имени В.В. Спринга Тонна фиксов CVE уязвимостей Первые попытки поддержать CRaC Новая поделка: Penna для логов в JSON Обновы в Quarkus, Micronaut, Payara, OpenLiberty, Mojarra, Grails, Tomcat... Ничоси. Читать далее
https://habr.com/ru/companies/bar/articles/775308/
#java #javawatch #olegchir #failoverbar #spring #jakarta #gradle #micronaut #quarkus #tomcat
-
Weil ja nun wieder in Mode ist mal wieder über die #Uhrenumstellung zu reden, hier mal meine "two cents" dazu:
Dass es im Sommer länger hell ist als im Winter hat nur ganz am Rande etwas mit der Uhrzeit zu tun.
Dezembertage sind halt nun mal nur gut 8h lang im Gegensatz zu den 16h eines Junitags. Da ändert sich nichts dran, egal wie viel wir die Uhren hin und her drehen oder auch nicht.
-
Upgraded to Spring Boot 3 (yes i am late). Found out `@PreAuthorize is a decorative corpse`. You now need `@EnableMethodSecurity(prePostEnabled = true)` to reanimate it. Laughable.
Thankfully, I had tests. Which is ironic, because I wanted to test my code, not Spring’s trust issues.
This dev experience? Trash tier. Writing one annotation to enable another? That’s not configuration—that’s a scavenger hunt in a haunted house. 👻🔍
Annotations should do something when you use them. Not wait for permission like a guilty intern. Imagine you would have to add a Junit annotation to tell, that test failures are thrown.
Should’ve just gone full auth(request) at every endpoint. More stable. Less betrayal.
#SpringBoot3
#WhyTrustWhenYouCanTest
#AnnotationAnxiety
#CodeOrCursedRitual
#IDidntChooseTheBugLife
#PreAuthorizePostMortem
#FrameworkGaslighting
#coding
#programming -
Upgraded to Spring Boot 3 (yes i am late). Found out `@PreAuthorize is a decorative corpse`. You now need `@EnableMethodSecurity(prePostEnabled = true)` to reanimate it. Laughable.
Thankfully, I had tests. Which is ironic, because I wanted to test my code, not Spring’s trust issues.
This dev experience? Trash tier. Writing one annotation to enable another? That’s not configuration—that’s a scavenger hunt in a haunted house. 👻🔍
Annotations should do something when you use them. Not wait for permission like a guilty intern. Imagine you would have to add a Junit annotation to tell, that test failures are thrown.
Should’ve just gone full auth(request) at every endpoint. More stable. Less betrayal.
#SpringBoot3
#WhyTrustWhenYouCanTest
#AnnotationAnxiety
#CodeOrCursedRitual
#IDidntChooseTheBugLife
#PreAuthorizePostMortem
#FrameworkGaslighting
#coding
#programming -
Upgraded to Spring Boot 3 (yes i am late). Found out `@PreAuthorize is a decorative corpse`. You now need `@EnableMethodSecurity(prePostEnabled = true)` to reanimate it. Laughable.
Thankfully, I had tests. Which is ironic, because I wanted to test my code, not Spring’s trust issues.
This dev experience? Trash tier. Writing one annotation to enable another? That’s not configuration—that’s a scavenger hunt in a haunted house. 👻🔍
Annotations should do something when you use them. Not wait for permission like a guilty intern. Imagine you would have to add a Junit annotation to tell, that test failures are thrown.
Should’ve just gone full auth(request) at every endpoint. More stable. Less betrayal.
#SpringBoot3
#WhyTrustWhenYouCanTest
#AnnotationAnxiety
#CodeOrCursedRitual
#IDidntChooseTheBugLife
#PreAuthorizePostMortem
#FrameworkGaslighting
#coding
#programming -
Upgraded to Spring Boot 3 (yes i am late). Found out `@PreAuthorize is a decorative corpse`. You now need `@EnableMethodSecurity(prePostEnabled = true)` to reanimate it. Laughable.
Thankfully, I had tests. Which is ironic, because I wanted to test my code, not Spring’s trust issues.
This dev experience? Trash tier. Writing one annotation to enable another? That’s not configuration—that’s a scavenger hunt in a haunted house. 👻🔍
Annotations should do something when you use them. Not wait for permission like a guilty intern. Imagine you would have to add a Junit annotation to tell, that test failures are thrown.
Should’ve just gone full auth(request) at every endpoint. More stable. Less betrayal.
#SpringBoot3
#WhyTrustWhenYouCanTest
#AnnotationAnxiety
#CodeOrCursedRitual
#IDidntChooseTheBugLife
#PreAuthorizePostMortem
#FrameworkGaslighting
#coding
#programming -
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
JetBrains builds brilliant tools. No question. But somewhere along the way, something shifted. The IDE that once felt like a sleek exosuit now wears more like a lead apron. Familiar, powerful but exhausting.
Remember Eclipse? I do. Grew up with it. Then grew out of it, death by poor developer experience. I see echoes of that fate in JetBrains, and it terrifies me. Not because JetBrains is bad. But because it was once… fun.
I've seen more memory leaks, heavier startup times, and codebases that feel like they took a wrong turn into a garbage collector. A "Hello World" project now needs 5GB If I leave it open long enough. It starts asking me existential questions.
My IDE now eats up 15GB with simple projects. Caches? Massive. Often useless. Builds that run clean in terminal break in IntelliJ until I do the sacred dance: Build → Rebuild Project or Invalidate Caches. It's a modern ritual. I now default to my terminal. It's honest. It listens. It doesn't pretend.
Plugin development? A labyrinth. Testing plugins is like chasing asynchronous shadows. Documentation is scarce, SDKs mutate overnight, and the event system reminds me of a toddler with espresso. Thousands of change events for a single file edit. I wanted to build useful tools.
Even giants like AWS and CodePilot plugins throw random exceptions. Testing? What's that? The SDK laughs in JUnit.
The final twist: my own plugin, full of hope and effort, is now the ugliest code I've ever written. I can't fix it. I barely recognize it. I miss simplicity. I miss reliability. I miss fun.
JetBrains still has brilliance. But quality? It's slipping. The warning signs are glowing. Not with malice, but with entropy.
Would be poetic if a new IDE emerged soon. Just like JetBrains once did, fresh, small, efficient. Until then, I'll keep fighting caches, memory bloat, and undetectable test classes… while whispering my Eclipse shortcuts in IntelliJ like ancient spells.
Funny, isn't it? Software today feels less like writing code and more like running a game engine. But the bugs aren't part of the plot. They're just bugs.
#JetBrains #IntelliJ #PluginDevelopment #Java #DeveloperExperience #IDEThoughts #Kotlin #MemoryLeaks #BringBackFun #TerminalNeverLies
-
I'm Now an Official NATS Maintainer! 🎉.
The votes are in, and I'm deeply honoured to join the NATS maintainers list, This is more than just a title. It's a moment of genuine pride.
Years ago, I got tired of the complexities and overhead that came with traditional messaging systems. Kafka? Powerful, yes, but exhausting. Then I discovered NATS. Brutally simple, elegant in design, and feature-rich without the bloat. Clustering, multi tenancy, portability – it just works. And that changed everything for me.
As a Java developer, I wanted to bring NATS into my ecosystem. As i love meaningful tests, I've built testing tools for it. For JUnit, Spring Boot, and plain Java.
The goal? The same philosophy as NATS: simple, reliable, user-friendly. These tools now have high test coverage, automation, and are easy to extend – just like NATS inspired me to do.Open source became more than a hobby. It became my space. A place where I can contribute, grow, take ownership, and be appreciated globally. There are no politics, no "office vs home office" debates, no gatekeeping. Just a community building solid, high quality software that the world relies on.
I'll never forget when Synadia reached out and allowed me to use the NATS logo for my libs and even sent me a package from the USA. That personal written letter? Still on my desk. A reminder that kindness and recognition can come from anywhere.
In OSS, I don't follow OKRs, SCRUMs, or agile charts. I follow curiosity, quality, and contribution. And I believe this is where innovation really thrives.
💡 One thing I still hope for: that more developers and companies recognize NATS as the powerful tool it is. Yes, there were recent changes in the CNCF relationship and yes, it raised questions. But the APL-licensed NATS is here to stay. And it's still gold.
Companies build their businesses on OSS. I hope one day they'll also support it financially or through real contributions. Without open source, there is no modern software and no Business.
To everyone in the NATS and broader OSS community: thank you. I'm proud to be one of you. @Scott, @Ginger, @derek
#NATS #OpenSource #Java #Messaging #ProudMaintainer #DevLife #Synadia #SoftwareEngineering #Innovation #Gratitude
-
https://open.spotify.com/episode/3WMlGLA66GecQUJXbvFvmq?si=BSx0glUHT-iXmIxHSBL2xg
Ein sehr gutes Gespräch zum Thema Menschen im Unternehmen. Dr. Judith Muster hat dazu ein paar echt sehr gute Gedanken!
-
https://open.spotify.com/episode/3WMlGLA66GecQUJXbvFvmq?si=BSx0glUHT-iXmIxHSBL2xg
Ein sehr gutes Gespräch zum Thema Menschen im Unternehmen. Dr. Judith Muster hat dazu ein paar echt sehr gute Gedanken!
-
https://open.spotify.com/episode/3WMlGLA66GecQUJXbvFvmq?si=BSx0glUHT-iXmIxHSBL2xg
Ein sehr gutes Gespräch zum Thema Menschen im Unternehmen. Dr. Judith Muster hat dazu ein paar echt sehr gute Gedanken!
-
Er is weer een COP bezig! #COP28.
Vorig jaar waren mijn collega-raadslid Judith Hofte van de @PartijvoordeDieren en ik uitgenodigd om de klimaatconferentie in Egypte te duiden (#COP27 -Conference Of the Parties):
Ter voorbereiding ben ik toen even geholpen door Laurens Dassen die daar is geweest, en door Carolina Pereira Marghidan, klimaatwetenschapper aan de UT.
Ook leerde ik hoe zo'n COP werkt bij deze lezing van Maarten van Aalst op de UT: https://www.youtube.com/watch?v=aOgAdQsvXnk
-
Er is weer een COP bezig! #COP28.
Vorig jaar waren mijn collega-raadslid Judith Hofte van de @PartijvoordeDieren en ik uitgenodigd om de klimaatconferentie in Egypte te duiden (#COP27 -Conference Of the Parties):
Ter voorbereiding ben ik toen even geholpen door Laurens Dassen die daar is geweest, en door Carolina Pereira Marghidan, klimaatwetenschapper aan de UT.
Ook leerde ik hoe zo'n COP werkt bij deze lezing van Maarten van Aalst op de UT: https://www.youtube.com/watch?v=aOgAdQsvXnk
-
Er is weer een COP bezig! #COP28.
Vorig jaar waren mijn collega-raadslid Judith Hofte van de @PartijvoordeDieren en ik uitgenodigd om de klimaatconferentie in Egypte te duiden (#COP27 -Conference Of the Parties):
Ter voorbereiding ben ik toen even geholpen door Laurens Dassen die daar is geweest, en door Carolina Pereira Marghidan, klimaatwetenschapper aan de UT.
Ook leerde ik hoe zo'n COP werkt bij deze lezing van Maarten van Aalst op de UT: https://www.youtube.com/watch?v=aOgAdQsvXnk
-
A new episode of #Silo is out now on #AppleTVPlus.
“The Janitor’s Boy” (S1, E5)
The dystopian sci-fi series stars #RebeccaFerguson, #Common, #TimRobbins, #HarrietWalter, #ChinazaUche, #AviNash and more.
-
A new episode of #Silo is out now on #AppleTVPlus.
“The Janitor’s Boy” (S1, E5)
The dystopian sci-fi series stars #RebeccaFerguson, #Common, #TimRobbins, #HarrietWalter, #ChinazaUche, #AviNash and more.
-
A new episode of #Silo is out now on #AppleTVPlus.
“The Janitor’s Boy” (S1, E5)
The dystopian sci-fi series stars #RebeccaFerguson, #Common, #TimRobbins, #HarrietWalter, #ChinazaUche, #AviNash and more.
-
A new episode of #Silo is out now on #AppleTVPlus.
“The Janitor’s Boy” (S1, E5)
The dystopian sci-fi series stars #RebeccaFerguson, #Common, #TimRobbins, #HarrietWalter, #ChinazaUche, #AviNash and more.
-
A new episode of #Silo is out now on #AppleTVPlus.
“The Janitor’s Boy” (S1, E5)
The dystopian sci-fi series stars #RebeccaFerguson, #Common, #TimRobbins, #HarrietWalter, #ChinazaUche, #AviNash and more.
-
A quotation from Judith Martin
It is, indeed, a trial to maintain the virtue of humility when one can’t help being right.
Judith Martin (b. 1938) American author, journalist, etiquette expert [a.k.a. Miss Manners]
“Miss Manners,” syndicated column (1999-02-02)More info about this quote: wist.info/martin-judith/79642/
#quote #quotes #quotation #qotd #judithmartin #missmanners #correctness #ego #falsemodesty #humility #modesty #pride #rectitude #selfrighteousness
-
Modern life is rubbish. Case in point; #WebSearch. I just tried to search;
greens.org.nz spokespeople
I think it's pretty clear what I'm after. I want results from that website *only*, that include the keyword 'spokespeople', right?
#DuckDuckGo gives me thier Wikipedia page, a bunch of spokespeople announcements from 2023, an ActionStation page on alcocol policy that lists Judith Collins as National leader, and the list of spokespeople for the *NZ Labour* party, FFS. Useless.
(1/?)
-
Modern life is rubbish. Case in point; #WebSearch. I just tried to search;
greens.org.nz spokespeople
I think it's pretty clear what I'm after. I want results from that website *only*, that include the keyword 'spokespeople', right?
#DuckDuckGo gives me thier Wikipedia page, a bunch of spokespeople announcements from 2023, an ActionStation page on alcocol policy that lists Judith Collins as National leader, and the list of spokespeople for the *NZ Labour* party, FFS. Useless.
(1/?)
-
Modern life is rubbish. Case in point; #WebSearch. I just tried to search;
greens.org.nz spokespeople
I think it's pretty clear what I'm after. I want results from that website *only*, that include the keyword 'spokespeople', right?
#DuckDuckGo gives me thier Wikipedia page, a bunch of spokespeople announcements from 2023, an ActionStation page on alcocol policy that lists Judith Collins as National leader, and the list of spokespeople for the *NZ Labour* party, FFS. Useless.
(1/?)
-
Modern life is rubbish. Case in point; #WebSearch. I just tried to search;
greens.org.nz spokespeople
I think it's pretty clear what I'm after. I want results from that website *only*, that include the keyword 'spokespeople', right?
#DuckDuckGo gives me thier Wikipedia page, a bunch of spokespeople announcements from 2023, an ActionStation page on alcocol policy that lists Judith Collins as National leader, and the list of spokespeople for the *NZ Labour* party, FFS. Useless.
(1/?)