After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

friggin' node dependencies

Linux sucks.

Now now, chill. I'm using it as my main OS for a few years now. I know what I'm talking and this title is a bit click-baity, but this just has to go out there:

1. It's usable as a Windows replacement just fine - FALSE. XFCE4 is years old and buggy as hell especially on multi-monitor set-up, Gnome3 gets stuck more often than my Windows 98 machine used to, KDE is like a rich kid on meth. Plug in Bluetooth headphones? Well no, sorry, you have to research that online, since you'll probably need to install some packages for it to work. Did I say "work"? Well no, because after more research you realize that Debian on Gnome3 on gdm3 launches pulseaudio on its own, so you have 2 instances of pulseaudio, and one of them is stealing your headphones sometimes and you either have no sound or shitty sound. How do I know that you ask? The same way I know everything else - every time you try to do something new on any Linux, it involves a ton of research. Exciting research, don't get me wrong, but at this point it looks more like a toy than a reliable desktop computer operating system.

2. And why am I using pulseaudio? Why not alsa? years ago people were discussing on forums that pulseaudio is old and dead, yet here we are with new LTS release of Ubuntu still shining with Pulseaudio. How about several different service management systems being deprecated by new ones, each having different configurations and calling methods? Apparently systemd is old and lame now. It's a mix of 10 year old software that works badly, with a 5 year old replacement that works worse, somehow trying to live under the same roof. Does it work? Ask my headphones who sound like a fucking dial-up modem.

3. Let's talk about displays, shall we? xorg is old and deprecated, right? We got Wayland that's mostly stable. Don't know what that is? That's just basic knowledge for Linux. And when you try to install network-manager, it also tries to install Mir toolkits. Because why the fuck not install 3 display managers when you want a network manager, of which one is old and dying, one is young and stupid, and another is an infant that died of cancer?

4. Want to integrate with Google Drive? Yeah, there's a tool that mounts the drive as a local directory. Yeah only for Ubuntu. Want it on Debian? You need to compile it. Oh wait, it's on Ocaml, because fuck mainstream languages, we're hipsters. How do you compile Ocaml? Well you need to have Ocaml on your system, dummy. How do you do that? Well you need to compile Ocaml. Ok, how do I do that? Well, git clone, download and install some dependencies, configure, make... oh sorry, you're using libssl1.0.2g when you need libssl1.0.1f, nope, sorry, won't work. Want to install libssl1.0.1f? Why? You already have the "g", stupid! Want to remove libssl1.0.2g? Bye-bye literally everything that you have on your PC. But at least you got the "f". Does it work now? Well no, because you need libssl1.0.2g for another dependency to work.
And all I ever wanted was to get a fucking document from google drive (not nudes, I promise).

5. Want to watch a movie? Let me tear that screen in half and make the bottom half late by a couple of frames, because who needs vertical sync, right? Oh you do? Well install the native drivers maybe. Oh you have? Welcome to eternal Boot to Recovery mode, motherfucka!

---------------------------------

Yeah, most of the times things work just fine. But the reason I know what those things are and how they work is not curiosity. The reason that I know the inner workings of Linux much better than the inner workings of Windows, is because in those few years that I've been using it full time, it has caused me 10 times more headache than I have ever experienced with other systems. And it's not the usual annoyances like "OMG it rebooted when I didn't ask it to", but more like "Oh, it won't work and I need 2 days to find out why" kind of stuff, because even if you experience the same thing again, it's always caused by some new shit and the old solution won't work any more.

I still love it, and will continue to use it. I don't know why really. Maybe because I'm not afraid of fucking it up any more? Maybe because I can do what I want in it and recovering will be easier than on Windows?
It's a toy for me, after all these years. And I also use it for professional reasons.

But whenever someone presents it as a better alternative to Windows, I just want to puke.

LONG RANT AHEAD!

In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.

mvn clean && mvn install

same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.

mvn clean && mvn install

the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...

Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...

I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.

Today, after two hours of debugging, my girlfriend called me to break up.

Then my backend started giving strange errors about some unmet dependencies.

Underlying pure C library and NodeJS wrapper

I believe by the time Elon Musk sets up a colony on Mars, npm will be done installing those fucking dependencies.

When all project dependencies can be installed using apt-get...

Co Worker: "Your computer is missing a mouse!"
Me: "I require less dependencies to use a computer"

BBUUUURRRRNN

Smart India Hackathon: Horrible experience
Background:- Our task was to do load forecasting for a given area. Hourly energy consumption data for past 5 years was given to us.

One government official asks the following questions:-
1. Why are you using deep learning for the project? Why are you not doing data analysis?
2. Which neural network "algorithm" you are using? He wanted to ask which model we are using, but he didn't have a single clue about Neural Networks.

3. Why are you using libraries? Why not your own code?

Here comes the biggest one,

4. Why haven't you developed your own "algorithm" (again, he meant model)? All you have done is used sone library. Where is "novelty" in your project?

I just want to say that if you don't know anything about ML/AI, then don't comment anything about it. And worst thing was, he was not ready to accept the fact that for capturing temporal dependencies where underlying probability distribution ia unknown, deep learning performs much better than traditional data analysis techniques.
After hearing his first question, second one was not a surprise for us. We were expecting something like that. For a few moments, we were speechless. Then one of us started by showing neural network architecture. But after some time, he rudely repeated the same question, "where is the algorithm". We told him every fucking thing used in the project, ranging from RMSprop optimizer to Backpropagation through time algorithm to mean squared loss error function.

Then very calmly, he asked third question, why are you using libraries? That moron wanted us to write a whole fucking optimized library. We were speechless at this question. Finally, one of us told him the "obvious" answer. We were completely demotivated. But it didnt end here. The real question was waiting. At the end, after listening to all of us, he dropped the final bomb, WHY HAVE YOU USED A NEURAL NETWORK "ALGORITHM" WHICH HAS ALREADY BEEN IMPLEMENTED? WHY DIDN'T YOU MAKE YOU OWN "ALGORITHM"? We again stated the obvious answer that it takes atleast an year or two of continuous hardwork to develop a state of art algorithm, that too when gou build it on top of some existing "algorithm". After listening to this, he left. His final response was "Try to make a new "algorithm"".

Needless to say, we were completely demotivated after this evaluation. We all had worked too hard for this. And we had ability to explain each and every part of the project intuitively and mathematically, but he was not even ready to listen.
Now, all of us are sitting aimlessly, waiting for Hackathon to end.😢😢😢😢😢

So I was sitting at my university's PC pool and was compiling some open source project that I need. It's a pretty big project with lots of dependencies, so I was already pretty frustrated…

Then, suddenly a guy walked to me and said, very angrily, "Hey! What are you doing there? I'm the sysadmin and someone told me you're hacking the computers!"

I told him I was just compiling some source code but he didn't stop and said he was going to call his boss. He said that "Only hackers use the terminal". I was getting very irritated and asked him what kind of sysadmin he was, rambling on in confusement.

Suddenly, he started laughing. Apparently, he got bored at his job, saw that I was struggling to install dozens of dependencies, and wanted to fool around a little. He actually installed me the dependencies as root afterwards :D

I just hate npm dependencies.

If you want to write a small website with npm dependencies (some frontend deps like Bootstrap and some development deps like gulp or babel) you will have more npm dependencies in your project than own code. It is ridiculous, how some lazy developers just add dependencies to their projects, without evaluating their dependencies. The source code of one of my projects is around 4MB (without any dependencies). If you then run yarn as required, it grows to around 80MB (where 73MB are node_modules).

This is just terrible.

I rant about this, as I made the mistake to upload my node_modules directories when restoring a backup of my server. Worst idea one could ever have.

sudo apt-get random-tool

Traceback (most recent call last):

Aborting because there's a fork in the spoon compartment on line 43 in main

Error this script only works on Python 2.7 and maybe 4.1 on line 59 in main

Missing symbols when trying to decipher Sumerian recipe for steamed vegetables on line 67 in main

Cannot open shared object: Your OS is a bully and is hiding my files on line 98 in main

Are you sure all directories matching ^(/)?([^/\0]+(/)?)+$ are in your $PATH on line 268 in main

Your computer is kind of vibrating in an annoying way on line 332 in main

Failing because I'm feeling insecure please hold me on line 587 in main

I'm feeling confused about my sentience when running TensorFlow models on line 682 in main

FUCK

HAS ANYONE EVER MANAGED TO JUST FUCKING INSTALL A PYTHON BASED APPLICATION WITHOUT DEBUGGING RANDOM COMPUTER STATE SHIT AND DEPENDENCIES FOR THREE HOURS?

A quick note about node.js security.

Decompiled Discord, a widely used chat app. Found 5 vulnerabilities (that are now reported.) Why? Severely outdated dependencies.

Cloned Mattermost, a business communication app like Slack, but open source, and (from their site) the Department of Defense uses it. Found 10 vulnerabilities (that are now reported.) Why? Severely outdated dependencies.

I get that some versions conflict, and in a fast moving enviroment, that is a huge risk - but update your damn dependencies.

I think the coolest project I did was a few years ago, it was actually a Minecraft plugin.

I decided to learn Java for Minecraft, and a few months after I started learning Java, I was approached by someone who'd like to work with me to create this full-blown Gun Game style gamemode for Minecraft. I made it clear I didn't have the most knowledge, but I was willing to learn.

We began working on the project, the projects main class was bigger than any project I had worked on. Within a few months, it became one of the more popular plugins out there, even though we were still in an alpha mode. Had nearly 1,000 servers running the plugin, over 10k+ players total testing out the plugin.

Cause of this project, I learnt how to properly organize my code, how to make it efficient, learnt how to network, learned how to properly secure and verify anything being sent by the client, working with dependencies, adding features that can support a bunch of other plugins that other developers had, and a bunch more.

Sadly we couldn't finish the plugin anymore, so we gave someone else the source code who has kept it updated to this day. (I know I didn't provide much insight into what I'm saying and just gave a general overview, got a killer headache.)

Me: Well, it's time to make a new app!
* opens up VS Code *
* opens folder selection dialog *
* creates a new folder called "notes app" *
* yarn inits that folder *
* installs react and react-dom *
* installs webpack, webpack-cli, babel-core, babel-loader, babel-preset-env, babel-preset-react, style-loader, css-loader, file-loader, html-webpack-plugin and clean-webpack-plugin as a dev dependency (install is pending) *
* copies a webpack config from some other project *
* creates a babelrc file *
* copies a yarn script called "build:dev" which would launch webpack *
* dev dependencies installed *
* tries to save *
* vscode doesn't save because files differ *
* tries to copy dev dependencies *
* fail *
* tries again *
* saves *
* writes bare-bones index.jsx *
* yarn build:dev *
* opens build/index.html in firefox *
* gets satisfaction *
* writes bare-bones App.jsx which is a react component but it's an entire app *
* yarn build:dev *
* opens build/index.html in firefox *
* gets satisfaction *
-- trim --
* walks out of his room to his mom's room where's sbc is located *
* grandma plays solitare on laptop *
* i ask grandma for a laptop *
* grandma gives me laptop *
* glues all components into App.jsx *
* yarn start:dev (magic of webpack-dev-server) *
* opens localhost:8080 in firefox *
* searches how to update a component prop *
* nothing found *
* registers on devrant and verifies his email *
* writes this rant *

<rant data-type="corny">

My Gf of 3 years left me for some douche. Thus said, she "removed" her feelings before kissing him. WTF! I didn't know feeling came like dependencies...

</rant>

Just e-mail the dependencies in a zip, that 'pip' stuff is too complicated

So today I decided to switch to angular 4(material) on a project I had done. I have to say I am shocked by the sheer size of the node modules dependencies I have to install. Why wouldn't they just ship it all in one package. 😤 I had to install the client, material SDK, animations etc and all this is happening over shit sub-saharan Africa internet speed. I have been setting up for the past 5 hours and I'm only halfway through. If anyone reading this rant has a company that works to bring internet to Africa please hurry. We need you.

I don't know.. I mean I'm spending so much time developing what I'm developing but.. In a couple of years, maybe the dependencies I'm using will be updated and my program will become obsolete.. what if the whole framework on which my application is based upgrades.. I don't want to have to rewrite code again because it's just too much work..

I think we need to figure out ways to future proof stuff.. like a decade into the future or so.. We shouldn't have to support prehistoric code..

Colleague: Hey want to get access to our repo so we can see each others code, collaborate, discuss design patterns etc?

Me: Yeah sounds like a great idea. Would love to get to know a bit more about how others are building mobile apps in the company.

Colleague: Heres the link to the iOS app: xxxxxxxxxx

*Opens link*
*looks around a bit*
*Opens cocoapods folder*
*Sees 89 dependencies*

Me: .......... actually, you know what, I have major deadlines coming up. I can't look at this right now. Lets talk in the new year.

*closes slack*

I had this prepared in advance and executed on April 1st few years ago.

1. I wrote an app in Python that would autostart self & listen to UDP multicast and spam screen with message boxes once a special "magic" UDP broadcast kicks in. The app had minimum dependencies and used native libs for GUI to achieve this.
2. I posted this app source code on sprunge.us and remembered the short URL.
3. Once one of my coworkers left their PC unlocked, I opened their terminal and executed '$(wget -c sprunge.us/ASDF)' and closed the terminal as if nothing happened. I infected almost all machines this way.
4. On the April 1st I get to my office, open the terminal, send a magic UDP broadcast packet anf enjoy the chaos.

Man, that was hilarious.

There is code reuse and then there is stupidity. This npm module has 4 dependents and 2 dependencies.

I’m a .NET desktop fullstack dev these days… Never worked web unless for my own small needs/personal projects.
I started using tech one way or the other by the time windows was version 3.1 and been through quite a bit ground-breaking changes in the industry of software development and the internet but if there’s one thing I cannot understand of it all, no matter how much thought I put into it is: How the fuck did we manage to make it so fucking complicated to develop anything these days?
I remember like it was yesterday that you could stand a website with HTML, CSS and JS, three fucking files and you’ve made yourself a single page site. Then came the word “Responsive”, “Responsive” written everywhere. Fair enough, grid system popped up. All of the sudden jQuery was summoned… and everything that happened after this point has been a fucking circus of high-pitched teens talking on conferences about fucking libraries and frameworks to make integration with real time, highly scalable, eco-friendly, serverless, data driven, genome aware, genderless, quantum technologies to interact with bio dynamically generated organisms, namely fucking users.
Every fucking bit of the process of building a mobile/web application seems to be stopped by yet another incredibly dumb attempt to suicide a developer. Can you go from starting an app and publishing an app without jumping through a thousand VERY specific hoops? No, fuck no.
I fucking hate it… It’s a bit hard to get Desktop dev jobs these days but for as long as I work on IT I will continue to stick to that area, until someone for the love of life comes up with a fucking solution to all this decadent circus of bureaucratic technocracy.
Fuck big industry, fuck tech giants, fuck javascript and webassembly, fuck kids putting ASCII art on console applications that I DON’T FUCKING NEED to install dependencies THAT I DON’T FUCKING NEED to extend functionality on frameworks that I DON’T FUCKING NEED… oh wait, I do need all this because YOU FUCKING MADE IT MANDATORY NOW! FUUUUUUUUUUUUUUUUUUUUUUUCK YOU!!!

Dev1: We need you to name this service
Dev2: Name it whatever
Dev1: You should name it
Dev2: Can we change it later?
Dev1: No
Dev2: Are you going to have dependencies on the name
Dev1: Yes
Dev2: Call it StupidDev1
Dev1: Ok we will name it

Saturday plan: serious switch to Linux.
1. Installs Fedora, lookin nice.
2. Let's update it, fails to boot.
3. Nouveau driver fails, lets install proprietary one.
4. dnf install dependencies, repo returns 503
5. Be stuck on a 640x480 bash.
6. Boot windows, start overwatch.

I want to cry.

To start, some of you know that I live in Reunion Island.
But there are a week ago, the SAFE cable is broken (one of the two cables that give us internet access), due to that, my ISP reduced a lot the connection speed.

Yesterday, I downloaded some packages in my Ubuntu computer. I left it download during the night.

So, today I was checking if it was done.

"6 926 kB downloaded in 5h 30m 9s (349 B/s)"

But it isn't the worst. I got a many "timed out" when downloading the dependencies.

😭😭😭😭😭😭😭😭😭😭

When you can't remove an app cause one of its dependencies depends on itself

Do you know what really annoys me?

Installing dependencies for the dependencies for the dependencies ... etc... for the libaray you are trying to use.

FUCKING FUCK JAVASCRIPT AND IT'S FUCKING 10000 DEVDEPENDENCIES.

LET ME FUCKING CODE AND WRITE TESTS AND NOT SPEND FUCKING ONE FUCKITY FUCK WEEK TRYING TO FIGURE OUT HOW TO FUCKING MAKE MOCHA AND KARMA PLAY WITH FUCKING ES6 CODE YOU FUCKING FUCKTARD PIECE OF SHIT TECH.

I NO LONGER FUCKING KNOW WHICH PACKAGES I FUCKING NEED AND WHICH I FUCKING DON'T FUCKING DUMBFUCK FUCKWIT OPEN AND HACKABLE MY BROWN ASS PIECE OF TECHNOLOGY STACK.

[14 dependencies]

"Geez this project has a lot of dependencies. I know, I should use a package manager!"

[15 dependencies]

Hey look, npm broke my project again. Surprise!

Code and dependencies on my local machine, all untouched for a couple of weeks, no longer works. I've no idea how it even managed that.

Oh, and `npm update` crashes.

eventually solved by upgrading npm and running `npm update --depth 500` because some arbitrary child dependencies changed without updating the parent packages, ofc. on my local machine. without me having run `npm update` for about a month.

because of course that makes sense.
Second time in two months, too.

isn't npm great?

Dependencies here dependencies there, dependencies fucking everywhere.

Oh yes, I very much like you, Mr. 1337-DevPro-Ultra-Haxxor. Thank you for using a boilerplate from github, that is bloated like some random female pr0nstar after an orgy. Oh and it is also very funky of you, that the setup scripts and tasks only work on Apple OSX, because using a simple gulpfile with 3 npm dependencies and 5 lines of code would not be trendy enough.

Some JS "devs" should be punished by drowning in their own feces aka a mix of bower, yarn, npm, brew and the crusty stuff that is left behind after running it.

When you about to start a project by doing a small module, but as you code, you keep thinking about scalability, security dependencies and such....

....three hours later, you still haven't written code

Me and my team are working on a system where we depend on a component that was built by a different dev team and hasn't been integration tested yet, because it's that new. This is how it's going..

Help.

I'm a hardware guy. If I do software, it's bare-metal (almost always). I need to fully understand my build system and tweak it exactly to my needs. I'm the sorta guy that needs memory alignment and bitwise operations on a daily basis. I'm always cautious about processor cycles, memory allocation, and power consumption. I think twice if I really need to use a float there and I consider exactly what cost the abstraction layers I build come at.

I had done some web design and development, but that was back in the day when you knew all the workarounds for IE 5-7 by heart and when people were disappointed there wasn't going to be a XHTML 2.0. I didn't build anything large until recently.

Since that time, a lot has happened. Web development has evolved in a way I didn't really fancy, to say the least. Client-side rendering for everything the server could easily do? Of course. Wasting precious energy on mobile devices because it works well enough? Naturally. Solving the simplest problems with a gigantic mess of dependencies you don't even bother to inspect? Well, how else are you going to handle all your sensitive data?

I was going to compare this to the Arduino culture of using modules you don't understand in code you don't understand. But then again, you don't see consumer products or customer-specific electronics powered by an Arduino (at least not that I'm aware of).

I'm just not fit for that shooting-drills-at-walls methodology for getting holes. I'm not against neither easy nor pretty-to-look-at solutions, but it just comes across as wasteful for me nowadays.

So, after my hiatus from web development, I've now been in a sort of internet platform project for a few months. I'm now directly confronted with all that you guys love and hate, frontend frameworks and Node for the backend and whatever. I deliberately didn't voice my opinion when the stack was chosen, because I didn't want to interfere with the modern ways and instead get some experience out of it (and I am).

And now, I'm slowly starting to feel like it was OKAY to work like this.

"Older versions are more stable"

The whole concept of LTS in development pisses me off.

Delayed upgrading, whether it's the language itself, dependencies or tooling, does just one thing: It makes future upgrading way more difficult, often to the point where the company eventually runs into this maintainability wall, and gets stuck in old, unsupported versions.

"But... stability!" — The tiny chance that the newer version has such serious stability regressions that it negatively impacts your own product doesn't weigh up against the clusterfuck you fall into if you push the task too far into the future.

You can relatively easily assess a new major language version using benchmarks and unit tests. Predicting the repercussions of staying on PHP 5.4 or Python 2.7 for another year, predicting the impact of upgrading the codebase later, that is almost impossible.

I'm not saying you should live on the bleeding edge in production, but as soon as a new stable version of a core technology is released, just fucking drop everything you're doing and port those deprecated methods!

The company I interned at last summer decided to adopt a JS framework a little over a year ago. The managers went with the old Angular 1.x because they didn't want a JS build process. Each page has ~100 script tags on it, and these are manually included in various files (no automated way to include dependencies). None of the CSS/JS files are minified, either.

They really should have chose Angular 2+, or an entirely different framework (React, VueJS). They're also just now upgrading the codebase from PHP 5.6 to PHP 7.2 (5.6 support ended a long time ago, and security support ends this month).

I love the company itself but these practices are poor.

I may be working there full time eventually. I hope to eventually help with the inevitable transition to a newer framework once Angular 1.x is dead since I am an avid user of newer JS technologies. Any tips on convincing manager(s) towards newer technology? (Or at least convincing them to combine+minify these files in production to reduce # of requests and bandwidth.)

Also this company's product has millions of active users.

I got some work on a new project so I ran the 500, or so, unit tests and it took almost 3 minutes. Everything was mocked and no external dependencies so I got curious as to how on earth they could take so long.

I found some suspicious code doing a while loop over a date range incrementing by 1 day each time. It turned out the tests didn't initialise the start date which defaults to 01/01/0001, and there are 5 scenarios!

I got test execution down to a respectful 10s.

Time to rant about JavaScript tutorials.

If you don't know the 'jQuery basic arithmetic' joke, Google it now. It'll make you laugh, promised.

In that manner i just remembered a JavaScript tutorial my fiancee tried to follow when she did an internship at the company i work for last year.

She was tasked to create a temperature interface for our server rack, which she wanted to do via an Arduino and a webserver aswell as an SQL database.

The Arduino part wasn't really a problem, but since she had no experience with js she very closely clinged to a chart visualisation tutorial.

All of that worked very well, but beeing the person i am i looked at the code and found something off.

The chart library had no dependencies to external libraries or any local files for any of them. Though the tutorial used a jQuery import.

So why did it use jQuery?
Well...
To load the chart initialization after the page has loaded.

So they pulled the entirety of jQuery in just to do what fucking window.addEventListener('DOMContentLoaded',function(){...}); could have done.

I wonder how many people who just want something to work did this shit. I hate it that so many tutorials do not adhere any kinds of standards, override behavior because they don't like it, even though it may have a very good reason to exist, pull entire libraries in for something vanilla <language> can do in 3 lines, etc.

Fuck.

Installing all the needed Latex dependencies on linux takes maybe 15 seconds, on windows I need 5GB of space and it takes forever to install.

Ok friends let's try to compile Flownet2 with Torch. It's made by NVIDIA themselves so there won't be any problem at all with dependencies right?????? /s

Let's use Deep Learning AMI with a K80 on AWS, totally updated and ready to go super great always works with everything else.

> CUDA error
> CuDNN version mismatch
> CUDA versions overwrite
> Library paths not updated ever
> Torch 0.4.1 doesn't work so have to go back to Torch 0.4
> Flownet doesn't compile, get bunch of CUDA errors piece of shit code
> online forums have lots of questions and 0 answers
> Decide to skip straight to vid2vid
> More cuda errors
> Can't compile the fucking 2d kernel
> Through some act of God reinstalling cuda and CuDNN, manage to finally compile Flownet2
> Try running
> "Kernel image" error
> excusemewhatthefuck.jpg
> Try without a label map because fuck it the instructions and flags they gave are basically guaranteed not to work, it's fucking Nvidia amirite
> Enormous fucking CUDA error and Torch error, makes no sense, online no one agrees and 0 answers again
> Try again but this time on a clean machine
> Still no go
> Last resort, use the docker image they themselves provided of flownet
> Same fucking error
> While in the process of debugging, realize my training image set is also bound to have bad results because "directly concatenating" images together as they claim in the paper actually has horrible results, and the network doesn't accept 6 channel input no matter what, so the only way to get around this is to make 2 images (3 * 2 = 6 quick maths)
> Fix my training data, fuck Nvidia dude who gave me wrong info
> Try again
> Same fucking errors
> Doesn't give nay helpful information, just spits out a bunch of fucking memory addresses and long function names from the CUDA core
> Try reinstalling and then making a basic torch network, works perfectly fine
> FINALLY.png
> Setup vid2vid and flownet again
> SAME FUCKING ERROR

> Try to build the entire network in tensorflow
> CUDA error
> CuDNN version mismatch
> Doesn't work with TF
> HAVE TO FUCKING DOWNGEADE DRIVERS TOO
> TF doesn't support latest cuda because no one in the ML community can be bothered to support anything other than their own machine
> After setting up everything again, realize have no space left on 75gb machine
> Try torch again, hoping that the entire change will fix things

At this point I'll leave a space so you can try to guess what happened next before seeing the result.

Ready?

3

2

1

> SAME FUCKING ERROR

In conclusion, NVIDIA is a fucking piece of shit that can't make their own libraries compatible with themselves, and can't be fucked to write instructions that actually work.

If anyone has vid2vid working or has gotten around the kernel image error for AWS K80s please throw me a lifeline, in exchange you can have my soul or what little is left of it

Loaded morning dependencies 😬

I fucking HATE testing JavaScript. It's such fucking bullshit. I've been struggling to test one simple functionality for multiple hours. It's probably one stupid thing I can't figure out, so I hope some sleep will grant me a fresh look tomorrow.

Also it's absolute bullshit the amount of libraries and dependencies you need to have to get some proper scalable tests going. Jasmine, Babel, ES2015, yarn/npm (because Jenkins is too fucking old to handle yarn). React, react test helpers, webpack. The list continues. FUCK OFF!

"I'm almost done, I'll just need to add tests!"

Booom! You did it, that was a nuke going off in my head.

No, you shouldn't just need to add tests. The tests should have been written from the get go! You most likely won't cover all the cases. You won't know if adding the tests will break your feature, as you had none, as you refactor your untested mess in order to make your code testable.

When reading your mess of a test case and the painful mocking process you went through, I silently cry out into the void: "Why oh why!? All of this suffering could have been avoided!"

Since most of the time, your mocking pain boils down to not understanding what your "unit" in your "unit test" should be.

So let it be said:

- If you want to build a parser for an XML file, then just write a function / class whose *only* purpose is: parse the XML file, return a value object. That's it. Nothing more, nothing less.
- If you want to build a parser for an XML file, it MUST NOT: download a zip, extract that zip, merge all those files to one big file, parse that big file, talk to some other random APIs as a side-effect, and then return a value object.

Because then you suddenly have to mock away a http service and deal with zip files in your test cases.

The http util of your programming language will most likely work. Your unzip library will most likely work. So just assume it working. There are valid use cases where you want to make sure you acutally send a request and get a response, yet I am talking unit test here only.

In the scope of a class, keep the public methods to a reasonable minimum. As for each public method you shall at least create one test case. If you ever have the feeling "I want to test that private method" replace that statement in your head with: "I should extract that functionality to a new class where that method public. I then can create a unit test case a for that." That new service then becomes a dependency in your current service. Problem solved.

Also, mocking away dependencies should a simple process. If your mocking process fills half the screen, your test setup is overly complicated and your class is doing too much.

That's why I currently dig functional programming so much. When you build pure functions without side effects, unit tests are easy to write. Yet you can apply pure functions to OOP as well (to a degree). Embrace immutability.

Sidenote:

It's really not helpful that a lot of developers don't understand the difference between unit, functional acceptance, integration testing. Then they wonder why they can't test something easily, write overly complex test cases, until someone points out to them: No, in the scope of unit tests, we don't need to test our persistance layer. We just assume that it works. We should only test our businsess logic. You know: "Assuming that I get that response from the database, I expect that to happen." You don't need a test db, make a real query against that, in order to test that. (That still is a valid thing to do. Yet not in the scope of unit tests.)

I recently ranted so much about languages but here it goes

JS we need to talk. BECAUSE YOU GOT FAT AND UGLY STUPID BITCH! Dumb piece of bloatware. What even is your problem? Depending on a library for strpad and then blow up like Steve jobs ego. Bastardized fuckfest. I used to like you bro and then you screw me over!
It's like you fuck my wife while I try to fix your car. Why can't you even be usefully on your own anymore? I'd be richer than bill gates if I get a dollar for every damn framework people pull from their asses. Are you writing this fuck while shitting so you can compare colors of your outcome?

Normalize the fucking base, don't add to the bukkakke! bitch is drowning already. Why is everyone jerking of to react and angular? When have YOU written something in vanilla the last time? Why even bother? Remove the core and hardcore every damn framework into the browsers. Guess that saves you 200kb. Oh wait I forgot that's about unminified jQuery.

Now I need to load about 2GB of dependencies, some creating code that puts code in my code to load code out of my code which was generated out of something that remotely resembles JS so every browser is able to execute my fancy shit. But hey, it's fast. And of course there are the fanboys. You are worse than apple fags. You sample your own jizz with your friends in a wine glass. there was a Time it was bad practice to mix logic and view. Now you made it mandatory. "Browser does the rendering" ofc you imbecile pile of fuck don't show me a damn preloader for 1 picture and 20 lines of text. Who fucked your brain so hard?

So react seems to be the cool kid now, then I tell someone I know angular it's like showing up in a pikachu onsie to a formal dinner with the queen.

I used to love you girl. I loved how we could dirty things together. Now you are like a pig. Please loose weight bby the sight of you disgusts me nowadays

Wow!
Makefiles are SO much cooler than I thought before

$< = the first dependency file
$^ = all the dependency files
$@ = the build target

AND if I try to build something who's dependencies don't exist, it'll automatically try to build them!

I just removed a couple of packages from package.json and my compiled war went from 53 MB to 37 MB.

What the heck are you downloading node? I don't like such bloated packages.

"The hardest part in programming is installing what you need."-the guy that almost threw it's PC out of the window because he spent 2 hours installing the wrong version of opencv

Never remove Python (and its dependencies) from Ubuntu.... I'm not proud...

Last week our department drama queen was showing off Visual Studio’s ability to create a visual code map.
He focused on one “ball of mud”, vilifying the number of references, naming, etc and bragging he’s been cleaning up the code. Typical “Oooohhh…this code is such a mess…good thing I’m fixing it all..” nonsense. Drama queen forgot I wrote that ‘ball of mud’

Me: “So, what exactly are you changing?”
DK: “Everything. It’s a mess”
Me: “OK, are any of the references changing? What exactly is the improvement?”
DK: “There are methods that accept Lists. They should take IEnumerables.”
Me: “How is that an improvement?”
<in a somewhat condescending tone>
DK: “Uh…testability. Took me almost two weeks to make all the changes. It was a lot of work, but now the code is at least readable now.”
Me: “Did you write any tests?”
DK: “Um…no…I have no idea what uses these projects.”
Me: “Yes you do, you showed me map.”
DK: “Yes, but I don’t know how they are being used. All the map shows are the dependencies.”
Me: “Do you know where the changes are being deployed?”
DK: “I suppose the support team knows. Not really our problem.”
Me: “You’re kinda right. It’s not anyone’s problem.”
DK: “Wha…huh…what do you mean?”
Me: “That code has been depreciated ever since the business process changed over 4 years ago.”
DK: “Nooo…are you sure? The references were everywhere.”
Me: “Not according to your map. Looks like just one solution. It can be deleted, let me do that real quick”
<I delete the solution+code from source control>
Me: “Man, sorry you wasted all that time.”

I could tell he was kinda’ pissed and I wasn’t really sorry. :)

Who here is programming with React Native and is crying about it?

It's so volatile. Shit it has done so far:

- Randomly changed my IP location that it serves to and npm start that shows the welcome information keeps the old IP address, so I spent way too long trying to figure out why it wasn't working.

- Constantly having to rm -rf the node modules and npm i them because Expo randomly starts loading so slowly that you want to scream.

- Downgrading my react-native-scripts version in the package.json because it hangs forever on the starting packager.

- I also had to downgrade my expo dependencies because during one of my node module reinstalls, it would update the version and apparently Expo is incompatible with its own updated version.

And now I'm randomly getting an error that's apparently a known bug in one of the react dependencies and now I have to downgrade that as well.

Just. Why.

I love and hate at the same time how the dependencies of some projects can turn into projects themselves.

Working on a quite big project right now and need notifications in the form of smartphone notifications/signal messages/emails right now for that which is nearly all working but now I'm realizing that it'd be ten times more useful to write a general messaging gateway/API wich can be called through a url which handles any type of messaging/notifications I need to send out.

Love it because those kinda projects are useful and awesome imo but that'd be YET ANOTHER project 😅😥

I feel like the web frontend landscape has gone to hell...

It used to be a priority to develop lean front end applications that load fast and work the same on most devices. If resources are required you try to share them. I have always liked the way this was solved using CDN.

Proper workflow: include some small libs you might need, script your interactions, test site, deliver.

And now our friends of the Javascript community have discovered the nuclear science called npm... It started off as this great benefit allowing frontenders to complete entire projects in the language they know and love but I feel like it has grown into an abomination that produces bulky applications with more boilerplate configuration than actual active code...

Surely I can't be the only one who is completely fed up with the direction this is going? Is anyone else looking for a lean way of developing javascript again using only a couple of small libs instead of those monstrous frameworks.

I have even considered to develop a library that makes it easy to develop with CDN (and dependencies) in mind but I don't even know if it will be worth it as more and more people tend to move away from it.

I'm sad

So we have an API that my team is supposed send messages to in a fire and forget kind of style.

We are dependent on it. If it fails there is some annoying manual labor involved to clean that mess up. (If it even can be cleaned up, as sometimes it is also time-sensitive.)

Yet once in a while, that endpoint just crashes by letting the request vanish. No response, no error, nothing, it is just gone.

Digging through the log files of that API nothing pops up. Yet then I realize the size of the log files. About ~30GB on good old plain text log files.

It turns out that that API has taken the LOG EVERYTHING approach so much too heart that it logs to the point of its own death.

Is circular logging such a bleeding edge technology? It's not like there are external solutions for it like loggly or kibana. But oh, one might have to pay for them. Just dump it to the disk :/

This is again a combination of developers thinking "I don't need to care about space! It's cheap!" and managers thinking "100 GB should be enough for that server cluster. Let's restrict its HDD to 100GB, save some money!"

And then, here I stand trying to keep my sanity :/

When configuring a digitalocean server and install shit loads of dependencies takes less time than npm install .....

When you look through your team’s custom protocols to figure out which one you need, and someone has not only made a massive typo, they then DOUBLED DOWN on the typo and made a bunch of dependencies based on that typo.

As in, the word “downloadable” spelled three completely different ways, and EACH ONE is treated like a different class with its own attached dependencies.

AND THE COMMIT MESSAGE ATTACHED IS “lots of cool stuff.” HOW IS THAT A COMMIT MESSAGE? WHICH ONE DO I USE?!

I’m never finishing this ticket, I’m going to get fired, etc. 😡😡😡😡😡

Time spent during a nodejs project:
- 2-4 hours trying to install modules and dependencies.
- 1 hour actual coding!

how to learn web development in 2018:

- watch youtube video of that new shiny promising framework

- spend hours trying to set up development environment

- spend another hours waiting for the dependencies to install

- spend the next few hours wondering and googling why it wont work even at fresh install

- spend another few hours redoing everything just to make sure you haven't missed a step

- realize that the youtube video you watched is uploaded last week, and now the framework developers mysteriously decided to change literally everything

- spend hours looking for another youtube video until you realize that now you are watching completely unrelated youtube video

- spend next hours wondering how your life become this pathetic while overthinking all of your past mistakes, and now you are just this lonely pathetic person with no clear future and that you will spend the rest of your life working at a fastfood chain below the minimum wage with no social life living on your parent's basement.

I freakin' love this message...
Welcome to the dependencies hell.

unpopular opinion: javascript has broken standards, and nobody corrects it. people use these frameworks and shit with 600 dependencies, then can't figure out how to update their application when things go out of date. now people are expecting you to use NPM to make a - - > static <- - website

A Visual Studio solution that had 62 (SIXTY TWO) projects for a webpage that was like 8 user forms total was like going to a shop to buy 3 items and receiving 15 tickets for that.
PMs saying no to refactoring due to not having enough time for a months. The first task took me 2 days just by fixing cyclic dependencies among the libraries. Went home and merged all the projects to just 3, building instantly in just two hours. Fuck idiot PMs that do not know how to code, buys shit and don't listen to devs. Fuck all idiots.

Plus 247 errors and dependencies.

Oh man where to start:

Not wanting to use LINQ because he did not wanted to "download external dependencies"

Not wanting to use prepared statements on their php sql code, and refusing to use pdo because they will "always use mysql"(moved to postgreSQL shortly after I left)

For some reason including a php file that only had ?>......thats it....only ?>

Use c++ but refused to learn oop and use structs for everything, importing stdio.h and printf everything.....like really?

Maybe just nitpicking, but refusing to use the recyclerview pattern on am android app. The implementation was faster after I made the change.

Importing a library for promises instead of using the ones already in the language(JS)

Changing the style of aaaaall p tags instead of using classes as well as refusing to use divs in place of p tags...well...fuck

Not indent his ASP classic code

Use notepad on his asp classic code

Use ASP Classic in 2017, even for new projects

Decided to give WSL (Windows Subsystem for Linux) a chance.........it was a BAD idea.

I go to the directory of my Node project and do "yarn" to install the packages.

Bash freezes while Yarn is linking dependencies. At this point I don't even know if it's still doing its job in the background or not, so I try to Ctrl+C.

Ctrl+C doesn't work either, I have to force-close the console.

When I try to open bash again, it doesn't even open. The only way to solve this is to re-login to Windows.

I appreciate Microsoft's intent in making their OS a better home for developers, but they still have a long way to go.

P.S.: No, this isn't a Yarn issue, everything works perfectly in both Linux and Windows :)

That moment you receive an email: your CI build is failing.

Ok. What went wrong?

Three new commits that do not seem to alter anything related to the failure.

*reverts commits and tries again*

Still failing.

WTF?!

*restarts previous builds*

They now fail too.

FUCK! BASTARD! Are you kidding me?

*investigates*

Turns out that repo of dependency changed and is not compatible anymore.

Argh! Son of bitch!

I've never been more glad for ubuntu on Windows. Python dependencies (through babun) were fuckin' me left, right and centre.

The worst architecture I've seen is WordPress.
How can you be so drunk to design such a filthy mess?
In some way PHP might be to blame. Its API is a fucking mess as well and may have stirred WP developers in this puke around so they couldn't come up with a better CMS architecture.
Don't get me wrong. I do love PHP. But only in it's OO form with namespaces and type hints and composer dependencies.

I've seen enough of PHP functional programming and it still haunts me.

Why does node-sass have such garbage documentation?!
I've now spent over an hour trying to get a clear and concise answer to how that shit works, and what do I get? This: (see picture)

I don't know what any of that means, nor do they care to tell me.
I don't want to render this shit at runtime, I want it to compile the sass code when I make changes to it so my app doesn't get boggled down by unnecessary background processes.
But nooo of course not.
To top it off, the "easy" electron-compile solution doesn't even fucking compile because all its dependencies are either outdated or 404 on me. 😡

It's shit like this that makes me hate web-style development. Lacking documentation and people who just assume everything is logical and clear from the start. It's fucking not.

Node.js: 3 dependencies, 8448 depents ... GG

Inherited a simple marketplace website that matches job seekers and hospitals in healthcare. Typically, all you need for this sort of thing is a web server, a database with search

But the precious devs decided to go micro-services in a container and db per service fashion. They ended up with over 50 docker containers with 50ish databases. It was a nightmare to scale or maintain!

With 50 database for for a simple web application that clearly needs to share data, integration testing was impossible, data loss became common, very hard to pin down, debugging was a nightmare, and also dangerous to change a service’s schema as dependencies were all tangled up.

The obvious thing was to scale down the infrastructure, so we could scale up properly, in a resource driven manner, rather than following the trend.

We made plans, but the CTO seemed worried about yet another architectural changes, so he invested in more infrastructure services, kubernetes, zipkin, prometheus etc without any idea what problems those infra services would solve.

The reason why "it works on my machine":
Python: dependencies

You add the next language and reason

Internal mail form CIO's office:

"Thank you for being part of the internal trial for NPMe, we have decided to remove this tool in favour of Artifactory because of its support for multiple platforms and tools. We are sorry for the inconvenience, here is a link to migration scripts ..."

Migration "script" readme, please clone this repo, create file A, and B, and install these 2 dependencies.

Dependency 1:

- "install via homebrew ..."
- .... homebrew needs to update, checking for updates
- 10 mins later = Update failed, please upgrade to Ruby version 2.3
- Installs ruby version manager
- GPG signature verification failed
- Install GPG v2 + accept keys
- Install ruby version manager
- "please execute this command before running rvm"
- execute command
- "rvm install ruby-2.3"
- Install failed, please see log file
- Opens log file
- "Xcode on its own is not sufficient, please install xcode cli tools"
- Install xcode tools
- 5 minutes later -> "rvm install ruby-2.3"
- 10 minutes later "brew install jq"

Ok back to read me, "login to Artifactory, go here and copy paste XXX."

- Login to Artifactory
- Eventually find repo
- Login again to actually see credentials for some reason
- Screen doesn't match instructions in readme
- Click around
- Back to readme
- Back to artifactory
- Login again
- Execute command auth / setup command
- Copy contents to npmrc file .... now all my scoped packages are going to point to 1 specific repo

Fuck the migration, Fuck these shitty instructions, i'll set them all up again manually. See tags below for further opinions on this matter.

Earlier this day, I was about to start a new project. So I copied my favourite gulpfile.js into that projects root and installed all dependencies with npm. After running Gulp for the first time it threw an error.

Silly me tried to fix stuff and got googling the error and trying random things... After a break of a few hours I just fucking rerun Gulp and read the fucking error completely. It stood there. The fucking solution just stood there, run "npm blah --force" to reconfigure package blah....

Of course it worked right away and I finally could start working. But this shit took way too long. Why I just can't read the fucking error message. Damn

*needs to repartition disks
*is mounted, need live usb
*download and burn gparted live, ≈20min
*reboot, usb not bootable
*try again, maybe it's corrupt...
* nope it just won't boot
*download and burn puppy Linux ≈20min
*is bootable
*installs gparted
*opens gparted
*repartition disks
*NOPE
*e2fsck failed: get a newer version of e2fsck
*already the latest version
*hmmm, maybe if I build it myself
*dependency hell
*dependency hell
*dependency hell
*give up
*download and burn Debian live ≈40min
*try to install gparted
*can't get WiFi drivers working
*give up
*download and burn Ubuntu
*opens gparted (already installed)
*partitions disk, leaves to complete overnight (it will have to move ≈60GiB)
*comes back in morning
*computer went to sleep after 10 mins
*late to work but oh well I at least got it done

The whole point of having a daily scrum is to let your team know about the progress you've made from last day and what you'd be needing to stick to the sprint plan.

So ideally everyone has 30-60 seconds to give a gist of their activities. And a small scrum team would be productive because everybody is on the same page.

Our scrum meetings usually wait for all of us to assemble with our coffees and donuts, sit down, joke, and then agonizingly go over everybody's existential crisis as a developer because of the task they've been assigned to has too many dependencies. And this happens every single fucking day! These "scrum" meetings tend to go for 1 hour. FML!

Ok, so many people rant about windows update. It can fuck up things, starts unexpectedly (after 100 warnings and messages letting you choose when but ok) and it takes too long to update.

I use Windows daily so I update regularly and never takes more than 5 mins. 20 when its a major update twice a year. So let's talk about Linux.

Yesterday I wanted to try out .net core on Linux so I booted my antergos vm to do it. TLDR: Didn't do shut because, surprise, Linux updates.

So apparently I downloaded the wrong version of visual studio code. Uninstall and install the right one then. Nope, can't do that. Some dependency must be updated. That dependency is on the highest version on the AUR, I have to get a different one. Ok, no problem. But I can install the other because uninstalling the original breaks more dependencies. Well fuck then.

So I decided I'd do a full system update with pacman, shouldn't take long. 1.6gb worth of update. I have 200mb download so it should be fast right? Well, I had to wait a couple of hours.

So I couldn't do anything on my afternoon because of Linux updates. That's an original rant isn't it?

And before the comments get here, yeah I know it's arch, it's difficult and all that. This isn't about being hard to do. It's just annoying and making me lose time.

Im forced to work with c++ on windows for a course.

0) c++ is fucking unusable without a central repo for managing dependencies. Maybe im just too used to maven but you shouldnt be downloading dll files in 2018.

1) visual studio can go suck a fat one. I got a fairly fast pc and it takes fucking forever to load anything. For comparison, eclipse with all my plugins (and i have a lot) loads in ~10 seconds, vs2017 does in 35.

2) why the fuck is there no cross platform compilation for c++? Its supposed to run on everything right? Whats so hard about porting a fucking linux compiler so i dont realixe i have .exe files when i want to work with my laptop on the bus?

3) c++17 (? Or whatevers the newest) syntax is like a deep barf on a hot summer day after eating a whole watermelon. Its fucking unreadable and autopointers simply dont work. And its not even my lack of skill this time, its the code that the other members used and it worked for half of them.

!rant

Need some opinions. Joined a new company recently (yippee!!!). Just getting to grips with everything at the minute. I'm working on mobile and I will be setting up a new team to take over a project from a remote team. Looking at their iOS and Android code and they are using RxSwift and RxJava in them.

Don't know a whole lot about the Android space yet, but on iOS I did look into Reactive Cocoa at one point, and really didn't like it. Does anyone here use Rx, or have an opinion about them, good or bad? I can learn them myself, i'm not looking for help with that, i'm more interested in opinions on the tools themselves.

My initial view (with a lack of experience in the area):

- I'm not a huge fan of frameworks like this that attempt to change the entire flow or structure of a language / platform. I like using third party libraries, but to me, its excessive to include something like this rather than just learning the in's / out's of the platform. I think the reactive approach has its use cases and i'm not knocking the it all together. I just feel like this is a little bit of forcing a square peg into a round hole. Swift wasn't designed to work like that and a big layer will need to be added in, in order to change it. I would want to see tremendous gains in order to justify it, and frankly I don't see it compared to other approaches.

- I do like the MVVM approach included with it, but i've easily managed to do similar with a handful of protocols that didn't require a new architecture and approach.

- Not sure if this is an RxSwift thing, or just how its implemented here. But all ViewControllers need to be created by using a coordinator first. This really bugs me because it means changing everything again. When I first opened this app, login was being skipped, trying to add it back in by selecting the default storyboard gave me "unwrapping a nil optional" errors, which took a little while to figure out what was going on. This, to me, again is changing too much in the platform that even the basic launching of a screen now needs to be changed. It will be confusing while trying to build a new team who may or may not know the tech.

- I'm concerned about hiring new staff and having to make sure that they know this, can learn it or are even happy to do so.

- I'm concerned about having a decrease in the community size to debug issues. Had horrible experiences with this in the past with hybrid tech.

- I'm concerned with bugs being introduced or patterns being changed in the tool itself. Because it changes and touches everything, it will be a nightmare to rip it out or use something else and we'll be stuck with the issue. This seems to have happened with ReactiveCocoa where they made a change to their approach that seems to have caused a divide in the community, with people splitting off into other tech.

- In this app we have base Swift, with RxSwift and RxCocoa on top, with AlamoFire on top of that, with Moya on that and RxMoya on top again. This to me is too much when only looking at basic screens and networking. I would be concerned that moving to something more complex that we might end up with a tonne of dependencies.

- There seems to be issues with the server (nothing to do with RxSwift) but the errors seem to be getting caught by RxSwift and turned into very vague and difficult to debug console logs. "RxSwift.RxError error 4" is not great. Now again this could be a "way its being used" issue as oppose to an issue with RxSwift itself. But again were back to a big middle layer sitting between me and what I want to access. I've already had issues with login seeming to have 2 states, success or wrong password, meaning its not telling the user whats actually wrong. Now i'm not sure if this is bad dev or bad tools, but I get a sense RxSwift is contributing to it in some fashion, at least in this specific use of it.

I'll leave it there for now, any opinions or advice would be appreciated.

Getting nugets and dependencies of a big project to restore properly (most of the time the dev fcks his solution up - it works for 'him')

Installing some dependencies with a tool from the company
« Error »

I click on More Details.
It was blank.
Thanks. Helpful as always 👌

Learning Angular, starting with a hello world example:

$ ng new wtf
added 1180 packages from 1294 contributors and audited 21849 packages in 18.753s
found 13 vulnerabilities (9 low, 4 high)

Oh, great! Broken from the get-to! But wait, there's more joy!

$ vimdiff wtf/node_modules/is-odd/node_modules/is-number/index.js wtf/node_modules/is-number/index.js

Fresh project, is-odd requires is-number, the project itself requires is-number. And is-number is there twice in two different versions. The notion of a number must have changed drastically in the last couple of years!

Seriously? Angular doesn't even give me the chance to fuck up the dependencies on my own!

Web dev in 2016:

Keep installing node dependencies until it works.

I love python, but I hate dealing with python dependencies, especially on Windows.
I was tinkering and researching with neural networks, so I wanted to try out pybrain. I wrote my project, with pybrain installed via pip, and tried to build it.
Oh, what's that? Pybrain doesn't work with python 3? Well I'll download the version that's supposed to. Oh, that version has a deprecated numpy api? Let me just install those other resources. Oh, that requires a broken module that has no publicly available source?
Let's try python 2. Oh, now that's working, I just need to export environment variables for some "bls source". Some quick Google searching and the only solution that would work is building a bunch of cywgin modules by hand. That's fine, I have an ubuntu partition.
An hour later I'm compiling FORTRAN dependencies on Ubuntu.
Coding time: 1 hour
Dependency time: 3 hours

Fuck nuget, .NET and whole C#, I'm solving problem with dependencies since yesterday.

Developers who think complex code is good.

"Oh, lookie here, I can swizzle methods and inject dependencies in the runtime!"

"Although we have no valid use case, let's use dependency injection and follow the commandory stateor patterns because I watched a video."

Just because you learn something new that looks cool does not make it practical, you tosser.

So I decided to install Arch on my Vps.
Problem: no connection from Vps to internet.
Info: I have terminal access from my hostings panel.
Solution: basic troubleshooting and Google
Problem: this hosting uses outdated install image with broken systemd-networkd.
Solution: install networkmanager
Problem: no internet
Solution: download networkmanager and dependencies on my laptop
Problem: How do I upload them?
Solution: put them in a tar archive, then base64 it and copy paste it via the panel.
Problem: That base64 is over 30MB. No browser lets me copy and paste so much text.
Solution: Write a quick and dirty Java that reads a .txt file and presses buttons.
Problem: Browser freezes after one second
Solution: Thread.sleep(10) after each character, and Thread.sleep(1000) after 10k characters for the browser to catch up.

It's currently going and I have no idea how long it will take. I'll post an update when it finishes.
And people ask me why I love programming. It can help solve so much problems with so little work.

Edit: according to some quick calculations this will take about 5-6 hours, so I'm cancelling it, sine it's past midnight now. I'll start it up tommorow before going to college

During a design meeting, our boss tells me that Vertx's MySQL drivers don't have prepared statements, and that in the past, he's used a library or his own functions to do all the escaping.

"Are you kidding me? Are you insane?"

I insisted that surely he must be wrong; that no one would release a database library without built in support for query arguments. Escaping things by hand is just asinine and a security risk. You should always use the tools in the database drivers, as new security vulnerabilities in SQL drivers can be found and fixed so long as you keep your dependencies up to date.

He told me escaping wasn't as tricky as I made it out to be, that there were some good libraries for it, and insisted Vertx didn't have any built in support for "prepared statements." He also tried to tell us that prepared statements had performance issues.

He searched specifically for "prepared statements" and I was like, "You know they don't have to be called that. They have different names in different frameworks."

Sure enough, a short search and we discovered a function in the Vertx base database classes to allow SQL queries with parameters.

I don't like when depending on something, e.g. smoking or coffee, but
still have to carry on dependencies in node_modules.

I recently got into an argument with some people, and I want your opinion. I did a speed code in Java (just sped up clip of programming, because it looks cool lol), and someone commented:

"Way too much static abuse here. Jesus"

In which I replied:

"Actually, sir. There is near none at all, just because I use static methods does not make it static abuse. A static method belongs to the class, and is somewhat permanent. It is not a type (instance, cat, dog, animal, etc.) class, it is a Utility class, much like other dependencies you'd use are Utilities and not types."

To which they reply:

"Getting and setting is a Utility?"

Boi. If it is a static variable, yes. Like, what?

Another thing that my dev friend told/send me the code to look at: the build&deploy system of one of their clients.
It's comprised of:
- 12 regular shell scripts
- 3 BASH only scripts
- 5 ZSH only scripts (required because of floating point computations, the other *shell scrpts use inline python for computations)
-> Most of these contain inline python 2 & 3
- 9 python 2.7 scripts
- 15 python 3 scripts
- 7 perl scripts
- 14 custom executables, written in c and c++, compiled every time this mess runs
- 6 jar files
- 4 nodejs apps

All of these are used to deploy a single product.
They have to be run in a specific order manually.
And you have to install some dependencies manually(like zsh)

I definetly don't want to work at that client of his.
My friend (I'm helping him) is trying to automate and rework this horrible mess.

I hate react so much. I hate it with the fiery rage of an old testament god. I tried to like it. I wanted to like it.

Unfortunately I picked up Angular (2). I'm now used to a framework that has you covered for most things. That has logical methods of laying out your app. A router that's actually built in and makes sense.

I'm used to writing HTML in the templates, not some horrible abomination of XML that's pretending to be HTML and just waiting to pull off its mask and smack you across the face with its penis while telling you what an idiot you are.

React apps all seem to be cobbled together in a different way. You have to go hunting for the logical stuff you expect to be there.

Let's not even get started on the tome of dependencies it needs to get itself off the ground, all written by vastly different developers from different planets with completely different life goals.

I hate it. The more I learn about it the more I find myself yelling "WTF!" while shaking a fist at the wall, hot tears of rage steaming down my pudgy cheeks until my wife comes running into the room and consoles me with my head on her bosom.

...and I just started a project that will have to be seen through to the end, using.. react.

Seriously, fuck you react, I hope you die of herpes.

when the junior dev updates all npm & nuget dependencies in the project to the latest beta versions to make an impression right after joining the project...

So we had this legacy Objective-C codebase for a mobile app that was actually pretty good: I'd inherited the codebase and spent the past several years gradually improving it and I was actually quite proud of the work I put into it. So of course management decides to scrap it (with NO consultation from the engineers) and outsource a complete rewrite of the app in C# for Windows Universal.

Let me tell you. That code was without a doubt and without exaggeration the *worst* code I've seen in my close to 30 years of experience as a developer. I mean they broke every rule in the book, I'm talking rookie mistakes. Copypasta everywhere, no consistent separation of concerns, and yet way too many layers. Unnecessary layers. Layers for the sake of layers. There was en entire abstraction layer complete with a replicated version of every single data class *just* to map properties in pascal case to the same property in camel case. Adding a new field to a payload in the API amounted to hours of work and about eight different files that needed to be modified. It was a complete nightmare. This was supposed to be a thin client, yet it had a complete client-side Sqlite database with its own custom schema (oh and of course a layer for that!) completely unrelated to the serverside schema, just for kicks. The project was broken up into about eight or nine different subprojects, each having their own specific dependencies on various of the other subprojects in such a tightly-knit way that it made gradual refactoring almost impossible. This architecture was so impressively bad, it was actually self-preserving!

Suffice it to say it was a complete nightmare, and was one of the main reasons I ended up leaving that company. So just sayin', legacy code isn't always bad. :)

Why python can't into proper dependency management?

I Node.js we use npm. Modules are downloaded per project and packaging is easy.

In Java we use maven/gradle. Never been so easy to build and download libraries and package your project.

But in Python? No, it's not easy. You have to use virtualenv first so pip/anaconda won't download globally, then you must write setyp.py in a million different ways. Packaging and distribution to clients? Good luck with that.

The way I was told to write unit tests was particularly terrible.

No mocking of objects or dependencies so the tests ran the actual code in full including updating databases and files. Then at the end of each test there was code to restore all changes back to before the test.

Each test ended up being over 100 lines. Madness.

A co-worker was running into a little permission issue with some dependencies and my reflex was to say, "chmod dat hoe!".

The joys of having NPM put all my dependencies sub-dependencies in my modules folder ☺️🔫

Wordpress updates > breaks jQuery dependencies
Requests theme update > theme update upgrades database without asking
Database upgrade breaks child theme > spending 30 mins rebuilding the filestructure and database from a backup

When you want to move your site off of jQuery, but all the dependencies still use jQuery.

Also screw those services that write their client code with jQuery. Screw you all!

I miss the ease of installing shit on Windows, none of this missing dependencies nonsense!

Product Management thought of automating an entire legacy product so they funded undisclosed amount to program management who in turn hired >20 contract devs managed by architects and dev managers with zero functional or technical knowledge of product and who in turn went ahead automating the product in selenium, end result of which was an useless automation framework with lot of browser specific dependencies and whuch could run only on one setup environment and migrating test cases to another environment and running is almost impossible and tyrannical to configure. The automation test cases are highly disorganized with all generic setup, DB configurations and business case test data mixed up in same config files and which need to be rewriten every time ported from one environment to other.To add misery to my woes as a dev working in that product I was told to utilize that framework and enhance the quality of my code by writing inline automation Cases for the same. I am left speechless thoughtless and emotionless after that decision.

I love the simplicity of jQuery and Angular 1.0 - you just include the JS files and off you go. No additional dependencies or messing around.

I have the habit of adding //todo comments to my code whenever I need to implement something later. Very useful to just search your code for "todo" and see what is left to do.

That is all very well, but I just searched my project for "todo" and there are SO MANY //todo comments in the third party dependencies...

I don't consider myself a guru in JavaScript (hell I studied theoretical chemistry), but I do hate much of the rationalization behind building a Jenga stack of libraries, frameworks, dependencies... for building everything web related.

Many of the problems I see people solving with these giant stacks could be easily solved understanding how websites work (html, css, js and how interact with each other) with no dependencies giving smaller (for end users at least) and more maintainable code (in the sense it would not require updating dependencies that may be discontinued...)

I do imagine situations where these are ideal... Since there are not absolutes and developing is very context sensitive, but man if I have js article fatigue for ridiculous scenarios.

Aws Lambda and serverless framework. Yes FaaS is cool. Love it. But it is pain in ass when you have the only way for you deploy is zip the fucking code with all the dependencies. Comm'on AWS you can do better. Look at azure functions. Please give me a git deployment support. Please I beg. Each test iteration takes like for ever. Also no proper local emulator. Fuck you AWS. Fuck you serverless.

I am a Technical Lead in the department in my company that writes code for our clients that have money but doesn't have the technical expertise to handle the complexities of our own software.

Part of my tasks involve taking care of a few projects written by employees that have left after using third-party tools rather than using our own software. No one else in this department knows these third-party tools, they only know our own, and my *still limited* web development experience means I get dumped these things in my lap.

And I'm SO pissed at these projects and their authors and the manager that let these ex-employees write these things. There is this one project that was managed by two different "developers" (I don't know they deserve this title) at two different times, and it is so riddled with different technologies it makes me want to throw up almost daily.

Don't believe me? Here is a complete list of the dependencies listed in the package.json of this project: babel-polyfill, body-parser, cookie-parser, debug, edge, edge-sql, excel-to-json, exceljs, express, html-inline, jade, morgan, mssql, mysql, pug, ramda, request, rotating-file-stream, serve-favicon, webpack, xlsx, xml2js

What this doesn't even show, is that one part of this project (literally one page) is made using react, react-dom, react-redux, and jade. The other part (again literally one page) is made using Angular and Pug. In case you missed it while picking up your jaw, there's also mssql, mysql, edge and edge-sql. excel-to-json, exceljs, xlsx.

Oh you want *more* juicy details? This project takes the entire data object used by the front-end, stringifies it into JSON, and shoves it into the database *as a single field*. And instead of doing WHERE clauses in the SQL queries, it grabs the entire table, loops, parses the json, and does a condition on it. If even one of those JSON entries gets corrupted, the entire solution breaks because these "developers" don't know what try/catch is.

The client asked for a very simple change in their app, which was to add a button that queries the back-end for a URL, shows it in a modal dialog, after which a button is clicked to verify the link by doing a second query to the back-end before modifying a couple of fields in the page.

This. Took. Me. Two. Months*. Save me. Please, save me.

*between constant context switches between this and other projects that were continuously failing because of their mistakes.

I hate dependencies... I'm stuck on a project because I need to wait for some one else to provide specs and access to their API.... And well I was also given a deadline...

Set-up a 5 node EC2 cluster in AWS; Install my dependencies on all; Add private keys between all for handshake; Submit my Hadoop job for processing; AWS closes my instance within 10 minutes of starting a job that took me almost half an hour to set-up because the master node's spot costs have reached more than 15 USD :(

I'm so PISSED OFF because of all the problem fixing I do. Most of the time, I take tutorials which have 6 steps a and 10 lines of code plus some config, and ALWAYS there is a problem somewhere, where it hasn't been covered in the guide. WHAT THE FLAMING FUCK? I literally spend days after days to figure out, that it's a problem with mostly one file/value, and no goddamn guide ever mentions the dependencies, if you don't have the defaults set for somewhat reason. And it's like this with every motherfucking tutorial I do to implement something, and most of the time I do understand what I'm doing, but THAT ONE VALUE/TRICK/FILE/SETTING/XML TAG/CODE TO A NUCLEAR SILO IS NEVER MENTIONED, WHY?!?!

Had a 5 hour call today, where we wanted to set up a system from one of our subcontractors in our own environment. Struggled forever to get the backend up and running.
Turns out that some dependencies were hardcoded as local file URLs...
No, our linux machine does not have C:\Users\<username> 🙄

I hate javascript and all the shitty frameworks it has.

Background: I'm coming from Ruby on Rails world. Ruby is a nice short language built primarily for developer's happiness.

I recently started working on a meteor.js project. Oh boy that framework is terrible. Do I even have to start from all the dependencies failing to install because npm is shit, installs everything locally and only recently discovered lock files?
Fetching a post and its author from the database looks like a fucking space rocket compared to Rails' ActiveRecord fetching.

Meteor.js fetching:
```
Meteor.publishComposite('posts.all', {
find() {
return Posts.find(); },
children: [{
find(post) {
return Users.find({ _id: post.authorId });
}
}]
});
```

Rails ActiveRecord fetching:
```
Post.includes(:authors)
```

Sure, you might get more benefits like meteor uses websockets and it's all a single language, but that piece of the code above that I have to deal with all the time now...it gives me cancer.

Our company has a giant folder that you have to download every release. It contains all of the dependencies within the company and every config file.

Twice a month your workspace gets fucked...BECAUSE THESE FUCKING GENIUSES CANNOT USE FUCKING MAVEN! What the fuck?! What idiot came up with this stupid idea?

I hate it that I'm still forced to use Ubuntu 16.04 and can't upgrade to bionic beaver.tried it on vm (for testing)loved new features and default gnome interface but even after switching to xorg most of my tool were still not running properly or crashing, most important factor is that there is still no official cuda support and installing gcc g++ 6 and symlinks are nerve racking. On top of that upgrading to 18.04 LTS on my main machine will leave me with broken packages and dependencies.

p.s. for people who are going to reply saying that these issue can be solved. Please try updating your work machine and spend hours fix these issues

You wake up early on Saturday to pee and you have a bunch of alerts in your inbox about failing dependencies in production. But you haven’t gotten any call or text from your boss. What do you do?

Well, I started browsing devRant while waiting for the next scheduled alert hoping my brethren on the other end of the systems resolve it and I wouldn’t have to login.

I have a serius dependencies problem. (I've never used drugs:)

I just wanted to create a small website using PHP MVC... Haha

Every time you download a project of the internet and you have to get all the dependencies going... and then your build fails...

I think this DDoS attack has made a few people re-evaluate their runtime dependencies

>ooo new thing to play with and learn, yay!
>*Installs using directions*
>Hello world program fails
>Oh I need these dependencies
>Wait the deps all need their own deps...
>But one of them is deprecated.. what do?

I love the feeling of working on something new but
I hate ending up spending more time getting a workflow setup and chasing down random bugs or hacky fixes just to get something stable so I can start working!!!

So, I'm looking into something and end up on Stack Overflow. Someone posted the question:

"Does minified javascript improve performance?"

This question was old as shit, all they way from 07/25/09, and about an Adobe Air application. (Remember that? Me neither...) It had a great, accepted, and still accurate answer, posted the same day the question was asked. Now, fast forward 8 years and on 12/08/17 (A mere 7 months ago...) the following answer was posted. I don't know what they were thinking, but here it is, complete and unabridged, with my comments in square brackets:

"I'd like to post this as a separate answer as it somewhat contrasts the accepted one: [Somewhat contrasts? More like completely contradicts...]

Yes, it does make a performance difference as it reduces parsing time - and that's often the critical thing. For me, it was even just simply linear in the size and I could get it from 12s to 4s parse time by minifying from 3MB to 1MB. [First off, your parse time should NEVER be THE critical thing, but secondly, and more importantly, WHO THE FUCK HAS 1MB OF MINIFIED JS ON A PAGE!!!]

It's not a big app either, it just has a couple of reasonable dependencies. [THERE IS ABSOFUCKINGLUTELY NOTHING REASONABLE ABOUT ANYTHING HE JUST SAID! What dependancies is he using?! You could use minified and not even gzipped jQuery, AngularJS, Vue, Ember, React, AND Dojo libraries on the SAME PAGE, AND have 118k of application code, AND STILL NOT HAVE HIT 1MB QUITE YET!!!]

So the moral of the story here is: Yes, minifying is important for performance - and not because of bandwidth, but because of parsing. [Javascript should NEVER take longer to parse then to download, even on a low powered device...]"

So, yeah, I'm at a loss for what this guy was thinking, but the thought the people like this exist, and that my browser might one day be subjected to their horrific nightmare of code terrifies me...

That moment when you realize you lost control of everything ¯\_(ツ)_/¯

-- Who are we?
#Developers.

-- What we want?
A #stable project environment.

-- What do we say to project #dependencies?
Never again!

when you install a module on limited internet connection and it comes with over 50 dependencies

Most of the times I feel like I install stuff for longer than I code... Just random thoughts.

When you spend half the work day and skipping lunch to resolve dependencies and process packages for an API but realize you're using the wrong OS…

Started new internship last week, hired as dev but working qa till their next release goes up. See last 3 posts for some horror lmao. They... don't know how to use git but insist they do. 275MB single repo for entire angular frontend (no dependencies are pushed, few images) and "angular backend" (according to PM). Commits to master, bad commit messages, no testing except me on qa..... death

Today was my first internship day in a web dev agency. One of the developer ask me to use express and make a rest API with typescript to jauge my knowledge.
I create the project, add dependencies (express, morgan, typescript, bodyparser and they typescript definitions...) and worked till the afternoon. I pushed my code into their gitlab repository.
Some minute later:
- (the dev): The code you wrote is not working at all
- (me): what ?
- (the dev): yeah, it throw with an error (SyntaxError: Unexpected token import
)
- (me: I've check again on my computer and it work perfectly, I watch his screen and see): ```node server.ts```
- (me):(thinking wtf ) Did you convert the typescipt into javascript ?
- (the dev): what ? I use typescript all the day with angular and Ionic. you don't have to tell me how to run typescript code.
- (me): actually, you must convert the typescript code into js before running it with nodejs. I have created a cmd in the package.json file to do it (show him the script and run ```yarn build``` and the code run successfully).
- (the dev): Hum! in fact I thought that nodejs in they latest version support typescript code.
-(me): no, I don't think so

So It was my first day of internship in the agency. (me showing to the one who was suppose to teach me some thing that he must covert a typescript code into js before running it )

I was in dependency hell for two days.
Im a junior working in a team creating an ember app. Suddenly a main component refuses to work since an addon threw "EmberObject undefined"... Nobody could reproduce it and we where out of ideas, so I tried fixing it for 2days (7h total). I finally got it working after updating yarn :D
It never felt so good working again :)

A quick rant about dependency injection.

I see far too often in projects, a huge over-reliance on dependency injection / IOC frameworks which permeate throughout the entire codebase.

I cringe every time I see a constructor annotated with @Inject and 10 params.

The benefit of these frameworks is how easy they make it to manage many dependencies. What I dislike about them, is exactly that. I feel that they make it TOO easy to manage many dependencies.

How trivial is it to simply add another constructor param? exactly. And people then wonder why their dependency tree looks insane.

I am a strong believer in injecting dependencies the traditional way, via the constructor with no fancy framework. The reason being that it forces you to think more about the dependencies you are adding to your classes, and consider if they are really all needed.

The other problem I have with it, is it basically encourages you to inject everything because its so easy. The purpose of dependency injection is inversion of control and allowing classes to depend on abstraction rather than concrete implementation. All that goes out the window when you @Inject 6 different concrete classes.

Use dependency injection for its intended purpose, not as an excuse to be lazy and avoid thinking about dependencies.

tl/dr;
The prodigal dev returns, and still the same as before

Not sure how I feel about this,

Some time ago I mentioned about a tech lead that created & enforced the use of somewhat useless lib, and then the guy left not long ago,

A bit of backstory,
The project itself is (supposedly) nearing the completion stage, which the "deadline" (if there's actually any) has been delayed multiple times,

First it was supposed to be done in x months, then extended for another n months, then another n months, then another x weeks, then another n weeks, then another x days, then another n days, and the last update for deadline is due by x weeks from now

Why is it like that? My guess is being too overoptimistic and underestimating everything, basically the shit that's been happening are all uncalculated risks and doing stuff outside the original plan, I'm not even sure if what they have can even be considered as a plan in the first place,

Ok so, back to the topic, nearing the end, the higher ups suddenly decided that the performance of the app is sluggish on older android phones when accessing a very long list (it's using react native), and it has to be fixed asap (just now they realised it? The project's been going for a year ffs)

And this guy, the tech lead mentioned above is brought back to the project with the hope to be able to resolve this issue

Tbh I'm not sure what is the root cause, I'm not following the issue much, but there was not much viable option, one of it was updating the library and introduce a new and (supposedly) more efficient component,

If we update the library too far, the other dependencies will fail, since some of them still depends on the older version of the lib, so first (and most viable) solution was to update the lib just enough for it to be able to use FlatList, which was supposed to be more efficient at rendering list than the deprecated ListView,

And then just today, a meeting was held, it was more like an announcement that the lead decided to create a new component, not sure how it's even gonna work, but it's supposed to imitate the functionality of ListView and do more efficient rendering, and the main component is just basic ScrollView with a lot of Views inside it,

After the meeting ends, and my team's representative told us the story above my first thought (and I believe it's same as everyone else's) was, "fucking brilliant, here we go again, another delay in the project",

Not sure why, but there's no one objecting his approach, the guy from my team wanted to object since the decision seems unwise, but there's no way to create a compelling argument to object it with after the lead said "let's say the component is there, does 5 days enough to change all the implementation?", everyone else just silently nods and agrees,

Another too fucking optimistic statement, "if the component is there", but it fucking isn't ffs,

After we heard the full story, everyone are suddenly feeling tired and went home for the day,

Installing 1 NPM package...

350 more dependencies installed :D

I'm starting to use gulpjs and there is one thing that keeps me busy aside from looking for best dependencies for my workflow;

"DIRECTORY STRUCTURE"

My current structure is simple af but somehow it works for me, but I'm still curious how to properly use assets, lib and vendor directories.

So I had someone question why their system was broken after they installed my software and all of its dependencies to /usr by hand... ._.

TL;DR: if you are using using react native, use uglify-es@3.2.2, any newer version might break your project

I wonder how many react native projects the boys at Mishoo fucked up, mine included.

I spent 5 work days to find an unrelated issue on RN's git which had the solution to my issue in the comments which was totally different from what was being presented in the issue.

Fucking aye.

I love javascript, but packaging really is its downfall.

I suck at unit testing. I really fucking suck at it.
Every time I try to write a unit test, I think to myself, what the fuck am I doing? How does this even work? What am I testing? Why do I need to new up 100 dependencies? how do I test this private behaviour from the boundaries of my object? Can I even substitute a Factory delegate? Does that even work? What if my object needs a dependency to have certain state? How do I mock that?

Does anyone have any good reading material to make me not shit at writting automated tests?

Fucking Windows.

Current project I'm working on requires that I import data from an MS Excel workbook using .NET.

No problem, I'll just use the handy OpenXML API. Works just fine. Implement my solution with no hiccups.

The user needs to have the file open at the same time though, so that they can fill in some information in the app's GUI about which columns to pull in. Uh oh.

Turns out that Windows doesn't even let you READ an Excel workbook if anyone has it open. Through the Office GUI I get the option to open it in read-only mode in this case. Through .NET though? Not on your life. Fucking IOException. No matter how I try to open it, doesn't work.

Can't even copy the fucking thing into a temp directory (which makes absolutely no fucking sense).

Only solution I've found to try and get access to the open file is to use Shadow Copy/Virtual Snapshot Service to try and trigger a backup of the file mapped to a virtual directory. Can you say overkill?

Going to try to implement that after lunch. There's a nuget package that wraps the Win32 API at least, but that requires VC++ Redist dependencies with we don't ship with currently.

This has gotten blown way out of proportion. I'm so irritated.

Our Swift teacher at college manually creates a Podfile for every project and copies and pastes the basic initialization from an existing project, pastes the cocoapod dependencies and then installs them using terminal instead of just doing a pod init and then using nano or vim to paste the dependencies right inside the terminal. These are the times I genuinely feel sad for the way Indian education system is and the way we're taught coding in colleges here.

I tried to install a simple Python package today for a simple 10 line program and spent over an hour installing dependencies and reading documentation.

I was in charge of updating the dependencies on a microservice we have. Everything was at least 3 years old. Nice. How bad was it gonna be?

Jesus Christ, I have never felt so wrong.

A certain dependency I will hide under the name w******js allowed custom functions for a feature that accepted three arguments: paramA, paramB, paramC. The old installed version, 1.x.x, did what was intended, but for some dumb reason, 2.x.x calls the function with paramA as paramB and paramB as paramA!

It took me a god damn while to find out why shit wasn't working as expected. Who thought this was a good idea?

Company Infrastructure Team: We are doing away with proprietary libraries and using standard Java instead.

Also Company Infrastructure Team: Here have a fuck ton of new proprietary libraries with dozens of nested dependencies. Oh we don’t use Maven by the way because we are fucking idiots.

Managing dependencies with npm or yarn feels like trying to communicate with a bunch of hipster kids. "Ugh omg I no longer hang in that namespace like that was so two weeks ago"

the dependency has a dependency with a dependency

Why the fuck does Windows still not have a fcking decent package manager?

I hear you "but but but, there is Chocolatey, it's great, try it!". Well yeah if you only want binaries.

But I do need to, you know, develop and compile things, and without includes, code, and a reliable way to produce working binaries from that, it's useless.

Guess who needs to download dependencies one by one, compile them one by one?

Don't get me started on broken MinGW, or the "recommended" way of doing a bat script to have proper includes (what the hell, that's the entire purpose of env variables), or the fact that there is NO convention on where to install things.

So I'm getting brought into a team for our backend services of our administration application, and they're explicitly using Flask (Python library) for their exposed API in their application and data tiers.

As I'm familiarizing myself with their code, utilities, and dependencies, I notice they're stacking 7-8 decorators on their routes from their in-house utility module.. After further investigation, I realized half of them were entirely unnecessary, and they were proofing payload responses three times for the same JSON format.

The fact that we're using Python instead of Node or GoLang for our REST services is pain enough, but these god damn in house utilities are killing me.

I learned my lesson when I had cyclic dependencies that made my main project get to almost 400mb.. It was only a few hundred lines too..

Me, working hard on a SQL project with a deadline that is half what it should be with no support from the other people on the project and was mostly made with with data I imagined would be in there cos no one could get me any fucking shit done (i.e. effectively designed, built, tested, fixed, upgraded, documented on my own for an entire weekly/monthly/ad-hoc analysis process that would output various reports for internal/external/management)

Manager - man who is a known waste of space but for some reason is in charge of the smallest part of the project, shouldn't have been fucking involved fucking management guzzling stain magnet...

Manager: Hey, do I need to refresh the database?

Me: .................

Me: .................

Me: ............I dunno, do you think we should refresh the database that this entire project is reliant? I mean...why do we need up to date transactions to analyse? Wait....you telling me it's not been being refreshed this ENTIRE time?

Manager: No....you never said I should. So should I?

Me: ..................I never said you should!?!? Are you not in the meetings talking about dependencies?????? Do you think i should have up to date trans or just run this with old stuff????? Why would you not update it!??!!?!?!? Its transactions...... (Desperately trying not to punch through my screen, through his, into his throat)

Manager: ..............

Me: .................

Manager: I think i'll refresh it and add it to the job?

Me: ....................(goes back to work cursing with music in so I think its quiet but who knows).

Tard, don't know how he even gets to work without someone holding his fucking hand.

Happy ending, I don't work there anymore :p

Sad ending, his spirit of tard follows me to my new jobs and possesses someone (or three sometimes)

Well, I just finished resolving the problems with my Angular dependencies. It has been 3 days of trying to come up with the solution, and in the end, it was all a matter of version mismatch of three dependencies. Now I can (actually) get to work on my project.

Linux is great - to tinker, to pull in all your FOSS, mess around...
But it's so fucked up, if you actually build and maintain a product on it, i.e. try to distribute s.th. in binary for money even. It's just not intended. If you offer your code for free, you can always say: "Ah, just compile it yourself. You might need these 29 dependencies, of which 2 are not even checked by configure, oops, and now it crashes, maybe in that qt library version, you picked there's still a bug?.. you know, it worked on my machine, sorry."
But if you sell it, it better install and run! And even if you target only the main distros of all that fragmented Linuverse - let's say, Debian, Ubuntu, RHEL, CentOS, Fedora, and if you're in Germany OpenSuSE and SLES, you'll start to see the crap of work you're up with. What you could try is to orchestrate a docker fleet with one container per distro, where you take the oldest version you still support compile a newer gcc there (to at least have C++11) and all your third party libs and then hope the resulting binary runs on all the newer versions of that distro, too.
(You could even be so brave as to try to pick a deb and rpm distro to build for all other distros.)
But ABI incompatibility can still bite you. For instance we once had the insane case, that our GUI would no longer start just by switching the Window-Manager to KDE.

So an update on my last rant(s) about dependencies and wasting time...

Today I finally lost it... With deadline fast approaching, i went to the big boss and he basically got everyone on his team to get their shit together and give me what I had asked for... 2 weeks ago...

It only took them 30mins.... Just the correct SQL query really...

npm has to be the single worst package manager on the planet... Trusting devs to use semantic versioning properly and forcing devs to trust authors of dependencies to use it properly is nothing short of insane. The package-lock that is "supposed to be version controlled" causes *constant* merge conflicts. Using shrinkwrap in its place is borderline useless because it Doesn't. Lock. High. Level. Dependencies.

I don't know who designed this, but I want to give them a very bad day for every hour I've spent trying to lock versions correctly on a live project.

Not to mention requiring root by default to install things that can just run whatever they want is ludicrous.

Hopefully at work we have successfully migrated from a combination of MySQL and Mongo to only Postgres. Also we finally split up our monolith into medium sized services, so we can actually do something interesting and update our dependencies.
And port one of the services from Java Struts to Django..
..but that is only if developers were to set the plan...if sales/management: new feature here! new feature there! sell sell sell! No time for maintenance!

Python is really beginning to turn horrible now. Legacy codes...argh!! why don't developers move already to python3? and all those horrible third party dependencies for only 2 which somehow break after even some mending. God save them. Horrible night.

What do you do when you are hungry/peckish and it's late?

It's 🌃 time and I don't have anything to eat (except maybe some stupid cookies)

I wish I could do
'npm i snacks'
or
'sudo apt-get snacks'

And I would receive snacks from my computer or something..

npm might also give some extra snacks plus ingredients as dependencies 😅

Maybe I can make coffee..☕?

Lesson of the day: First read installation tutorials for software on linux completely before doimg esch step without knowing the rest...

Today is the last day of my placement.

Over the past year, I began working on small front end bugs, to becoming the sole front end developer on the project, to being full stack.

Back in July, I and the other dev on the project released the app into the wild. It now is reaching 100 users.

The app has a lot of external dependencies (10+), one of which could cripple it entirely should it cut us off (which they can do at any time, it's a free API).

I was given, effectively a week and a two days to do a complete handover/transfer of knowledge to the placement student that will be taking my place. They hadn't touched front end (like me) when starting, but also had no experience in node/js.

As of this, I can't leave feeling like I've fully completed my work, and I feel bad leaving the new guy with these clients. Undoubtedly I'll be doing some off-the-record help.

Android Studio upgrade

Over the weekend I upgraded my android studio and the project files of my current project and all went smoothly (as far as I thought).
I did not touch the project till today as was implementing some few features only for some few unexpected bugs to creap in.Been implementing that feature for some time and thought would be done in a flash only to my disappointment.
Turns after upgrading my SDK they were some conflicting dependencies that had no idea of.
To make it worse my fall to branch was way behind the active one and had to create a new project from scratch and copy paste files.
All this after spending hours in Stack
Overflow and scratching my head.

Lesson learnt to commit more frequently.

Dear Python linters, why can't any of you implement some actual linting features? Like, say, consistent use of single or double quotes? Or dict() vs {}? How about indenting nested function calls? Forcing list / set / dict literals as multiline? Trailing commas?

And while I'm at it, why can't you handle dependencies properly? Say, separating linter & linter plugins from the remaining dependencies in a way where I don't have to manually remove them from the requirements lockfile every time?

Am I the only one who very often creates a new project folder and copies all the code because it's easier than cleaning dependencies and such?

I fucking hate working with older software

I have a visual installer project, and it automatically finds the dependencies to make the setup file.

if I rebuild a certain reference, in which I made no changes, and then refresh the dependencies, it will add another dependency that already exists, but outside the dependency folder. So now I have two exactly fucking the same dependencies.

i can remove it, but removing it doesn't change any of my files. So there is nothing to commit. If you restart the project, its back.

And first it required me to actually add the dll to the build folder before it would build. And suddenly not anymore.

Im pretty sure its either the outdated installer software or visual studio 2013 fucking with me.

It also randomly added a dependency from blend. Which is apparently a known bug, but never got fixed in the two updates after they recognized it as a bug.
Fuxx you microsoft...

Saw a git repo that contains the node_modules folder and some dependencies and was wondering how'd fuck did this guy get this up here.... Mehn some devs can be super powerful(funny)

When you download whole SDK, install lots of dependencies. Setup everything. And the moment you want to start working, your internet stop working. I would consider that a sign from a good but too bad, I am atheist.

Our configuration manager is leaving for a new job and now the office is crumbling.

How do you deal with person dependencies at your workplace?

Thanks to my parents to create an Application Context and autowire all my Dependencies required to live a happy life.. !!! The best framework that provides IOC -- Parents.
Note: Finally understood spring framework IOC and DI concept.. many more to understand..

In my freshman year of college, I ran into a grouping of circular dependencies that were so intertwined it would have warranted a total rewrite. I spent 28 hours fixing it. I took over my dorms common area, had about 5 movies playing on repeat for background noise, and stayed in the same seat for the whole period.
It was rewarding, but also showed me how easily I can get tunnel vision on a task. Now that I've graduated and moved on to a real job, I have certain back ups to make sure I don't forget to eat or take my breaks. I almost got in trouble for not taking them when I first started.