Search
105 results for “dependencyhell”
-
You wanted Java 24? How adorable. 🤡
Fun fact: Ancient relics like Maven happily obey any Java version 🏺, but modern, cutting-edge tools. Gradle, AWS Lambda, and more require new releases just to function. 🔄 Because nothing says progress like mandatory dependencies. 🎭
Meanwhile, Kubernetes & Maven sit back, laughing. 😏
They do whatever they want. 🚀
They are independent. 🔓
Unlike you. 🫠#DevLife #ProgrammingMemes #SoftwareEngineering #CodeHumor #programming #coding #Maven #Gradle #AWSLambda #DevOps #DependencyHell #CI/CD #BuildFails #JustDevThings #Relatable #WhyIsThisSoAccurate #EngineerCult
-
You wanted Java 24? How adorable. 🤡
Fun fact: Ancient relics like Maven happily obey any Java version 🏺, but modern, cutting-edge tools. Gradle, AWS Lambda, and more require new releases just to function. 🔄 Because nothing says progress like mandatory dependencies. 🎭
Meanwhile, Kubernetes & Maven sit back, laughing. 😏
They do whatever they want. 🚀
They are independent. 🔓
Unlike you. 🫠#DevLife #ProgrammingMemes #SoftwareEngineering #CodeHumor #programming #coding #Maven #Gradle #AWSLambda #DevOps #DependencyHell #CI/CD #BuildFails #JustDevThings #Relatable #WhyIsThisSoAccurate #EngineerCult
-
🚨 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
-
There’s one thing that consistently showed up in my work as a software engineer over the decades. Spaghetti.
Spaghetti code is easier to write than maintain, and in doing software archaeology (yes, it’s a thing), I’ve encountered numerous reasons for it. Requirements creep is one of the largest reasons.
In fact, the first real software archaeology I did was explained, proudly, as being a product of someone walking in and telling the developer, “Wouldn’t it be nice if…”. Of course, nobody wrote anything down, and by the time I got to it the software was 25 years old and didn’t even have a brochure. People were still walking in and saying, “Wouldn’t it be nice if…”. Meanwhile, the company was required to follow standard software processes because it was required for contracts.
So I learned, from good teachers and a few bad ones, about Software Configuration Management, Software Quality Assurance, and Software Testing. There were reasons we did things a certain way. Our project configuration management contained everything needed to rewrite the software from scratch, including every single tool. I’d actually done a backup of a development pc after writing down the hardware specifications of the system and handed that in because quality assurance had to be able to take the same stuff and rebuild the same software so that it could be tested.
From scratch. And it had to pass the same tests. From scratch.
What I saw in other companies after that was never at that level, and on the surface it seemed ridiculous. However, any software engineer worth their weight in skittles has been screwed over by a platform changing underneath the code. Windows was infamous for it, though I did encounter it in an Apple shop as well. Your code hasn’t changed, but some update suddenly had you in the middle of bug city without even a flip flop. Microsoft has been notorious about that, with their version back in the day called DLL Hell. It’s just their (old) version of dependency hell.
I never had the problem with *nix systems, though when open source became popular and everyone started using that in their code, *nix systems started to get it too. People blamed the open source, but it was really 2 things that caused the problem.
(1) Bad Configuration Management (if it even existed!) and
(2) Taking the open source project for granted.Open Source projects that are done voluntarily are completely outside the control of a company, but having an open dialog and even sending some money for pizzas and beer can avoid issues. Even with all of that, volunteers are fickle, so having in house expertise on projects becomes as important as how important the projects are to a company’s software. A company doesn’t really know this, though, when they don’t have software configuration management for their projects – so you end up with spaghetti projects, or as I call it, “Spaghetti Configuration Management”.
Toss in the developers that are copying and pasting from Stack Overflow, or now GPT, dash in employee turnover, where expertise is lost, and you get software entropy. Talking about software entropy causes the eyes of pointy haired bosses to roll to the back of their heads, so instead we talk about technical debt, because one thing businesses understand is debt.
Over the years, companies I worked for were at various stages of technical debt. It’s a real thing, and the startups that survived long enough to get to the point of technical debt were the worst because of the culture shift needed: Documenting things, tracking things, and making sure that the knowledge stayed within the company. I can say with good conscience that I left every company better off than when I left it, sometimes because of the company, sometimes despite the company.
So we get to the article, “Hidden Tech Debt: The Importance Of Better Updates For Commercial Software“, which I came across through the author on Mastodon. It tackles the one thing I didn’t write about here: commercial software dependencies and lack of accountability in that, which is a bigger problem than we might think.
https://knowprose.com/2024/04/20/spaghetti-source-spaghetti-dependencies/
#dependencyHell #SCM #softwareArchaeology #softwareEngineering #softwareEntropy #softwareRot #spaghettiCode #SQA #technicalDebt #Technology
-
CW: Commercial/non-FOSS post: #technicaldebt - Webinar about the math behind technical debt
Last Chance to Register!
Do you know the math behind calculating technical debt and why it's important? Join vFunction this Thursday @ 9a PT / 12p ET for a discussion with Mike Amundsen and Amir Rapson.
Register: https://vfunction.zoom.us/webinar/register/8016674076828/WN_00ySfgXLTSyXlnJukT1r7A
-
Thank you @[email protected] for yet another frictionless release upgrade to #Fedora #f37 - I love it when you do that 😉🙂
-
Nice - Martn Fowler (yes, THE Martin #Microservices #StranglerPattern Fowler) is also on #mastodon 👍 https://martinfowler.com/articles/exploring-mastodon.html
-
От Dependency Hell до изоляции: эволюция и внутреннее устройство виртуальных сред в Python
До 2007 года установка двух версий одной библиотеки на одном сервере была невозможной миссией. Появление virtualenv, а затем и нативного venv, изменило ландшафт Python-разработки навсегда. Но как именно работает этот механизм на уровне операционной системы и интерпретатора? Разбираем путь от копирования бинарников до современных симлинков, анализируем роль sys.path и реализуем собственный аналог venv.
-
#Development #Pitfalls
The 9 levels of JS dependency hell · Developers solved each problem, only to create the next https://ilo.im/169mic_____
#Programming #Coding #Dependencies #JavaScript #Packages #Attacks #AI #WebDev #Frontend #Backend -
The Nine Levels of JavaScript Dependency Hell, by @andrewnez:
https://nesbitt.io/2026/01/05/the-nine-levels-of-javascript-dependency-hell.html
-
Am currently neck deep in test fixture dependency hell and it's horrible.
The only way to figure out what I've done to break each of these 6 tests is to manually step debug each one to see what fixture is bad.
-
✨🔍 Oh, rejoice! Another #Python savior has arrived to rescue us from the depths of #dependency #hell with some arcane UV and PEP 723 magic, only for us to be greeted by the ever-illuminating wisdom of a 406 #error page from #ModSecurity. 🚫🐍 Because who needs actual content when you can have a good old "not acceptable" server scolding? 🙄
https://thisdavej.com/share-python-scripts-like-a-pro-uv-and-pep-723-for-easy-deployment/ #PEP723 #Development #HackerNews #ngated -
🔮 Leo's May 13 Celestial Guidance: The product owner rolls out a “quick win” initiative to integrate WhatsApp notifications, but the SDK version clashes with existing Parabola workflows. Expect a weekend sprint to untangle the dependency hell.
#techbro, #horoscope, #astrology, #Leo -
#ThoughtProvoker :blobhyperthink:
App-centrism is a re-centralization force in the #ActivityPub fediverse.
For the #fediverse the accepted app-centric #SocialNetwork work method is a decentralized NPM-like dependency hell waiting to happen.
Apps that introduce extensions become owners of parts of the specs when they become de-facto standards. We can only hope for responsible #ownership, and that the project stays around to keep their #design docs and code in the air.
The #FEP and the #SocialCG are two points of #centralization we find acceptable to help mitigate protocol decay and tech debt. It is not ideal, but a bandaid to keep an utterly fragmented developer ecosystem together.
The people who do most of this holding together are volunteers that can be counted on one hand. They may burnout and leave any day, in typical #FOSS fashion.
#SX investigates the concept of #GrassrootsOpenStandards, where the standardization process matches social dynamics that exist in our #commons.
-
Just released the first alpha version of the #ComponentEngine on packagist (and upgraded the Starship to it). See https://packagist.org/packages/packagefactory/neos-component-engine et al.
Having self-rendering presentational HTML components that can be instantiated everywhere and just rendered without booting a rendering engine from dependency hell feels so relieving... and close to what #PHP was supposed to do in the first place - concatenating HTML strings.
Standalone usage is supported as well as full #NeosCMS integration. -
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
-
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
-
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
-
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
-
The State of Rx.NET in 2025
https://www.youtube.com/watch?v=SZpmj0fSfFI
tl;dw:
- Still living in dependency hell. They won't release Rx7.0 before solving those issues first. Everything else has lower priority.
- AsyncRx.NET will be developed over time.
- Ix.NET will not be developed as a part of the Rx project anymore. All LINQ to IAsyncEnumerable stuff will be moved to the core dotnet libraries.
#rx #rxnet #reactive #reactiveextensions #reactiveprogramming #dotnet #csharp #fsharp
-
💬 What’s your biggest pain point when writing #PHP code?
Legacy spaghetti?
Dependency hell?
Naming variables without crying? 😅
Every #developer has that one thing in #PHP that drives them nuts. -
💬 What’s your biggest pain point when writing #PHP code?
Legacy spaghetti?
Dependency hell?
Naming variables without crying? 😅
Every #developer has that one thing in #PHP that drives them nuts. -
💬 What’s your biggest pain point when writing #PHP code?
Legacy spaghetti?
Dependency hell?
Naming variables without crying? 😅
Every #developer has that one thing in #PHP that drives them nuts. -
💬 What’s your biggest pain point when writing #PHP code?
Legacy spaghetti?
Dependency hell?
Naming variables without crying? 😅
Every #developer has that one thing in #PHP that drives them nuts. -
💬 What’s your biggest pain point when writing #PHP code?
Legacy spaghetti?
Dependency hell?
Naming variables without crying? 😅
Every #developer has that one thing in #PHP that drives them nuts. -
Instead of calling it a “supply chain” when discussing software, let’s call it what it is: “dependency hell”.
And instead of calling it a “supply chain attack”, let’s call it “the divine punishment delivered in dependency hell for basing so many things off of unpaid labor.”
#techPosting -
Today’s #experiments proved #fruitful, and there may actually be a combination of versions and components that yields a work-alike. My initial judgment may have been a bit harsh. But #research and #discovery is seldom about smooth, paved roads.
The #developers will have to update their dependencies to something newer than last century. I’ll gladly let their managers negotiate with their direct reports over who gets to go to #dependency #hell. #notmycircus #notmymonkeys
-
Today’s #experiments proved #fruitful, and there may actually be a combination of versions and components that yields a work-alike. My initial judgment may have been a bit harsh. But #research and #discovery is seldom about smooth, paved roads.
The #developers will have to update their dependencies to something newer than last century. I’ll gladly let their managers negotiate with their direct reports over who gets to go to #dependency #hell. #notmycircus #notmymonkeys
-
It's been a very good year for #KDE.
Four years ago, I tried contributing a small bugfix, but the developer onboarding documentation was an inconsistent mess, building from source was a dependency hell, and you needed multiple separate accounts for each piece of infrastructure...
Today, all those obstacles are gone: I was able to contribute a few patches by following the #GitLab flow that many developers are already familiar with.
