Search
20 results for “LunaFreyja”
-
@LunaFreyja Thank goodness #Maven uses #XML and not a cute #DSL based on a dynamic language that depends on ASM and #bytecode tricks. Why? Because I can freely upgrade to #JDK24 (or even #JDK25 EA) and Maven keeps chugging along, and no multiple weeks of waiting for a new compatible release ... (looks over at #Gradle and #Kotlin) #Java #OpenJDK
-
💰 Salary, 🌟 Development, 😊 Joy.
Everyone in your Team needs these values.
Pick two? You won't last.Yes, you can earn well without joy. But your weekends vanish. Your energy dies. Your money gets spent on escape.
Yes, you can love your job and get paid well. But if you're stuck with no growth, no challenge, eventually your spark fades.
And working forever on your weaknesses? That's not growth. That's managerial malpractice. Real development means doubling down on strengths, not sanding down your edges.
Also: the €5k difference between €95k and €100k? You won't feel it.
But the difference between €48k and €60k? That hits your daily.Want joy, growth, and sustainability?
→ Fewer roles.
→ Smaller teams.
→ Clearer direction.
→ Less compromise.
→ Room and Space for every role.That's how you build something that actually works.
#Leadership #TeamDesign #DeveloperExperience #WorkJoy #CareerGrowth #NoMoreBS #MinimalTeams #Productivity #FutureOfWork #PragmaticLeadership #TechCulture #WorkLifeDesign #TeamClarity
-
💡 Some people chase profits. Others build magic.
I love projects like this one:
👉 https://lnkd.in/dx2rU3unIt turns your MacBook trackpad into a digital scale.
No special hardware. No ads. No paywall. Just… curiosity turned into code.It hijacks the Force Touch sensors, calibrates raw pressure data, and gives you surprisingly accurate weight readings—all with your finger and a clever hack.
This is what I wish more tech looked like:
🧠 smart
🧰 simple
💸 not for saleWhile others gatekeep innovation behind SDKs and subscriptions, this project goes:
here’s how it works, enjoy.
Open Source with purpose, not polish for profit.It’s niche, odd, and brilliant.
And that’s exactly why it matters.To everyone trying to monetise every byte:
You’re missing the joy. You’re missing the point.To TrackWeight:
You nailed it.
Hacky, educational, experimental.
No evil. No upsell. Just exploration.
Thumbs up.#opensource #macos #trackpad #forceTouch #diytech #sideprojects #devtools #swiftui #buildinpublic #indietech #hardwarehacks #notforsale #curiositydriven #engineeringmagic #trackweight
-
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
-
Zero Trust Login
How I Stopped Reading Your Data in my servicesI build systems where not even the almighty admin (me) can read your data.
No backdoors. No db.users.find(). Just encrypted chaos. Beautiful, unreadable, untouchable chaos.Security isn't magic, we are just scared to lose control.
If I'm debugging live prod data, I've already failed my architecture exam.Many pretend to do the same using JWTs/JWKs. Cute. But let's be honest:
There's always someone with access. Production isn't a vault, it's just a cleaner sandbox.Most systems cling to readable tokens, human friendly JSON, and debug services like a comfort blanket.
I don't.Zero trust could work like this:
1. User signs up
➤ They give a password.
➤ I derive a unique key from that password.
➤ That key encrypts a randomly generated User Key.
➤ That User Key encrypts everything else (emails, usernames, secrets, hopes, dreams).2. User logs in
➤ Same password = same derived key.
➤ That unlocks their User Key.
➤ That unlocks their encrypted data.
➤ Voilà. Magic. But not magic. Math.3. Token generation
➤ It has no traceable info and All Session Data are encrypted with the backend-only key.
➤ It expires. Quickly.
➤ It is fingerprinted to the device/browser.
➤ You steal it? Good luck. Doesn’t work on your laptop, Dave.👁️ Zero Visibility ≠ Zero Functionality
• 🔒 I can’t decrypt your data. Not even if I'm angry.
• 🛡️ Backend is stateless. Frontend is stateless. Token is everything.
• 👨💻 No user ID in memory. No session storage. No cookies.
• 🪪 You want access? Bring your password, WebAuthn, 2FA or other login methods.
• 🕵️ No OAuth weirdness, no redirect hell.
• 🧠 Works like OAuth, but with actual privacy. Not even a user ID is exposed
• ⚙️ Agnostic to used technologies - Cloud, OnPremise, SQL, NoSQL, doesn't matter.Because security isn't magic. It's math, discipline, and just enough spite to not let anyone (including yourself) peek behind the curtain.
Until then, I'll be in the server room. Giggling at encrypted documents I can't read.
#ZeroTrust #Encryption #Security #Stateless #PrivacyByDesign #BackendOnlyAccess #NoRootForYou #Coding #Programming
-
Most companies chase quarters like lab rats chasing pellets.
Real ones? They chase galaxies.
OKRs make you efficient. Vision makes you dangerous.
Apple didn’t invent the iPhone to hit a KPI. SpaceX isn’t escaping Earth for a performance bonus.
If your team’s mission fits in a JIRA ticket, congratulations, you’re irrelevant.
Be vision-driven. Or enjoy your slow, optimized decay.
#Leadership #VisionDriven #ProductStrategy #Innovation #ThinkBig #NoMoreOKRs #BuildTheFuture #QuarterlyMadness #TechLeadership #SpaceXMindset
-
Is Node.js the future of backend development, or just a beautifully wrapped grenade?
Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.
When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.
Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.
So I wonder:
Is this the future? Or am I just… old?Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?
Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.#NodeJS #BackendSecurity #SecureCoding #PII #Compliance #SoftwareArchitecture #ServerSideRendering #TypeScript #Java #Kotlin #Golang #Erlang #Ruby #Scalability #Observability #DevSecOps #LegacyVsModern #SecureByDesign #CompiledLanguages #CloudArchitecture #StatelessDesign #SecurityTheatre #TechSatire #LinkedInTechRant
-
Stone Age Leadership: still alive.
Stop boxing humans like warehouse cats.
They're not broken robots to "fix".
They’re powerful, flawed, focused, and enough.Your job as a leader?
🌱 Build worlds they thrive in
🧩 Form RPG squads, not clones
🔥 Growth = support, not solo quests
🫶 Reward quiet excellenceMotivation > Title. Impact > Volume.
Gardens grow. Factories burn.#Leadership #ServantLeadership #TeamDynamics #QuietPower #PeopleNotBoxes #WorkplaceWisdom #FutureOfWork
-
Dear Gradle, Why So Stubborn?
Do I do something wrong?Watching juniors try to set up a project and being greeted by cryptic stack traces like it's some kind of initiation ritual.
`Unsupported class file major version 61`
`invalid CEN header zip64 no access package`, ...Java can compile code for older versions just fine.
It's literally designed for that.
Oh why, must Gradle behave like a bitter librarian who refuses to hand over a book unless I whisper the exact Dewey Decimal Code?
Every other Language will laugh again at java, seeing this.💡 Why is Gradle bound to a java version? And if Gradle knows it needs Java 11… why doesn't it just do this for me?
Like using `/usr/libexec/java_home -v 11` in background?🤖 Is there a clean way to force Gradle into submission without adding another tool like SDKMAN or jabba or YunaBraska/gradle-java-fix or whatever the trendy painkiller of the week is?
#Java #Gradle #BuildTools #DevHumor #DeveloperProblems #JDK #ProgrammingPain #CleanCode #SoftwareEngineering #OpenJDK #CodeNewbie #BackendDev #BuildFails
-
🚨 When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
#MinimalismMatters #CleanCode #DependencyHell #JavaPurist #DoYouEvenCare #LessIsMore #CodeSmart #TechDebt #DependencyManagement #JavaDeveloper #SecureCoding #LightweightCode #ModernJava #RefactorYourLife #NoBloat #CodeQuality #developer #code
-
🚨 When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
#MinimalismMatters #CleanCode #DependencyHell #JavaPurist #DoYouEvenCare #LessIsMore #CodeSmart #TechDebt #DependencyManagement #JavaDeveloper #SecureCoding #LightweightCode #ModernJava #RefactorYourLife #NoBloat #CodeQuality #developer #code
-
🚨 When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
#MinimalismMatters #CleanCode #DependencyHell #JavaPurist #DoYouEvenCare #LessIsMore #CodeSmart #TechDebt #DependencyManagement #JavaDeveloper #SecureCoding #LightweightCode #ModernJava #RefactorYourLife #NoBloat #CodeQuality #developer #code
-
🚨 When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
#MinimalismMatters #CleanCode #DependencyHell #JavaPurist #DoYouEvenCare #LessIsMore #CodeSmart #TechDebt #DependencyManagement #JavaDeveloper #SecureCoding #LightweightCode #ModernJava #RefactorYourLife #NoBloat #CodeQuality #developer #code
-
🚨 When your code is a few KB, but your dependencies rival AAA game installations. Still believe in fairy tales of secure code?
Gigabytes of code you didn't write. Licences you didn't read. Security flaws you didn't anticipate. Yet, you trust them. Adorable.
Not just Node.js. Gradle caches, AWS libs with 400 sub-dependencies + reflection parties. In control? How cute.
I use plain Java with jlink + jpackage. Minimal. Secure. No bloat.
Fewer deps = fewer surprises. Because I care.
But hey, keep stacking that Jenga tower. Watching it fall will be fun.
#MinimalismMatters #CleanCode #DependencyHell #JavaPurist #DoYouEvenCare #LessIsMore #CodeSmart #TechDebt #DependencyManagement #JavaDeveloper #SecureCoding #LightweightCode #ModernJava #RefactorYourLife #NoBloat #CodeQuality #developer #code
-
Java's final classes stifling innovation
I wanted to extend Optional for seamless integration of my TypeMap library. Fluent, functional, and reflection-free. But nope, Optional is final. Now I’m stuck recreating and syncing its methods manually. Final or Private classes don’t prevent misuse, they block creativity and create more mess when copying functionalities. I love final, but not on classes.
TypeMap: https://github.com/YunaBraska/type-map#Java #Programming #Optional #FinalClass #CodeProblems #DevLife #TypeSafe #InnovationBlocked #FunctionalProgramming #CodeDesign
-
🚀 Smart CI pipeline == less thinking, more coding! 🎯 Focus on the real work - let automation handle updates, versioning, deployment, and releases across services. 💡 Keep it simple, robust, and adaptable. Tech should simplify, not complicate! 💻✨
Example pipeline: https://github.com/NanoNative/nano/actions
#Java #CleanCode #FunctionalProgramming #Microservices #Async
@nano_native
#nanoative #graalvm #developer #DevOps #Automation #Maven #Gradle #CICD #TechSimplified #DeveloperLife #CodeSmart -
🚀 Smart CI pipeline == less thinking, more coding! 🎯 Focus on the real work - let automation handle updates, versioning, deployment, and releases across services. 💡 Keep it simple, robust, and adaptable. Tech should simplify, not complicate! 💻✨
Example pipeline: https://github.com/NanoNative/nano/actions
#Java #CleanCode #FunctionalProgramming #Microservices #Async
@nano_native
#nanoative #graalvm #developer #DevOps #Automation #Maven #Gradle #CICD #TechSimplified #DeveloperLife #CodeSmart -
🚀 Smart CI pipeline == less thinking, more coding! 🎯 Focus on the real work - let automation handle updates, versioning, deployment, and releases across services. 💡 Keep it simple, robust, and adaptable. Tech should simplify, not complicate! 💻✨
Example pipeline: https://github.com/NanoNative/nano/actions
#Java #CleanCode #FunctionalProgramming #Microservices #Async
@nano_native
#nanoative #graalvm #developer #DevOps #Automation #Maven #Gradle #CICD #TechSimplified #DeveloperLife #CodeSmart -
🚀 Smart CI pipeline == less thinking, more coding! 🎯 Focus on the real work - let automation handle updates, versioning, deployment, and releases across services. 💡 Keep it simple, robust, and adaptable. Tech should simplify, not complicate! 💻✨
Example pipeline: https://github.com/NanoNative/nano/actions
#Java #CleanCode #FunctionalProgramming #Microservices #Async
@nano_native
#nanoative #graalvm #developer #DevOps #Automation #Maven #Gradle #CICD #TechSimplified #DeveloperLife #CodeSmart -
🚀 Smart CI pipeline == less thinking, more coding! 🎯 Focus on the real work - let automation handle updates, versioning, deployment, and releases across services. 💡 Keep it simple, robust, and adaptable. Tech should simplify, not complicate! 💻✨
Example pipeline: https://github.com/NanoNative/nano/actions
#Java #CleanCode #FunctionalProgramming #Microservices #Async
@nano_native
#nanoative #graalvm #developer #DevOps #Automation #Maven #Gradle #CICD #TechSimplified #DeveloperLife #CodeSmart