Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
You say: "We added AI to our product"
I hear: "We added a bunch more IF statements to our codebase"8 -
#1
Fuck it. I obtained a Laravel codebase with 200 routes all handled by "mainController".
😓🔨
There will be rants.21 -
My teammates are working on a legacy codebase so shitty awful, so poorly written, so full of pitfalls, hidden information and intricate relationships, they gave a name to their development style:
Indiana Jones programming.6 -
when you had to maintain some stranger's shitty codebase, and you couldn't resist looking up his name on LinkedIn, then you found his profile which says he is a Rockstar coder
8 -
Just downloaded some big ass codebase and the first line i read is:
"// The source code is not well documented, but every advanced programmer will be able to understand it after some time."
Well... let's find out about your definition of "some time", Dickhead!3 -
Jr. front end dev says, "I know enough back end to be dangerous". Literally destroys entire codebase.9
-
Your code is only slightly less glitchy than the Matrix
My pet boa constrictor can write better Python than you
Your codebase looks like me after all-you-can-eat cheese fondue -- bloated AF3 -
When you see a comment like this in your codebase:
// I don't know what it does, but touching it will break it!4 -
Best: I'm still employed.
Worst: I'm still working on a PHP codebase, which only got bigger (34M lines) and more entangled this year.12 -
You know your codebase is large when you expand your project tree and it's larger than a literal tree.4
-
What the fuck is this. I swear every time I look at this codebase I find something more stupid than I did last time.
I can't wait to throw the whole legacy system away.
13 -
Job listing I just saw:
Our lead and only developer just retired after 15 years of maintaining the codebase. We need someone who is capable of working with large amounts of undocumented and untested code.
PS: This was a company that makes medical software.8 -
Should I be afraid right now?
Dev: can I swap out an existing UI framework from this codebase for a completely different one, because it doesn't do the small enhancement I've been tasked to do?
Me: ...............
please lord, give me strength in these pressing times.6 -
Found this in a legacy codebase at work. Can't imagine what the coder was thinking. "Just in case"?
5 -
The intern has directly editted the CSS file then push to the repo.
The senior optimized the old codebase and compiled the SCSS with gulp leading to the CSS file rebuild.
The vicious cycle continued until code review which was like 2 weeks later.3 -
If you ever come across a Java codebase with capitalized method names, RUN. I should've taken this advice years ago.
-
Temporary coworker with 10+ years experience, working on C++ codebase with me since 3 months, just asked me what the continue-statement in C/C++ does.
That must be either a sign of an upcoming apocalypse, or me being heavily underpaid.6 -
Teaching new recruit some SQL (even though hes supposed to fucking know SQL and have multiple years experience but I was a contractor and idgaf, not messing up my money. Just fucking annoying to have an idiot around you all the time).
Me: Okay, so sys tables, so this one is for jobs yeah?
Him: Yeah
Me: Okay, so in this table, its obviously not one row per job per step cos you have multiple rows for the same job and step. Also, there is a datetime field, so what is it showing?
Him: Hmmmmm..... (after some time, back and forth we get to the answer).... history table
Me: Cooooooool, okay, so, lets say, I have a job with 5 steps. If i run it once, how many rows will be in this table?
Him: 5 rows.
Me: Correct, so if I were to have run this same job, 10 times, how many rows get inserted into the table?
Him: (Now...you have to understand, how long this thought process was, im trying to fill the gap with words but really, he was like, having a flashback or something...I kept quiet but silently wanting him to say anything....then he looks me dead in the eyes).... 10!
Me: Motherfucker what!?!? 10 What? If 1 time == 5, what does 10 times ==?
Him: Hmmmmmmmmm.... (yes...we are doing this whole flashback montage all over again)....... Ohhhhh, 1!
Me: .....Stop, think, its a history table. It holds history, for when every step is run for a job, why would it be only one row?
Him: OMG, I know what a history table is!!!!
Me: (Pissed off cos I don't take disrespect calmly). Fine, genius, answer, go!
Him: (LONGER WAIT THAN LAST TIME!!!!)....is it not 10?
Me: I swear, I'm gonna kill you one of these days.
Him: *chuckle*
Me: No...seriously....
TOOK 20-30 MINUTES FOR HIM TO SAY 50!!!!!!
And even then, I swear he didn't understand why. Serious, he was a special breed, had a manager that was a super tard and when I worked here, the spirit of that manager possessed this idiot, the CIO and his little right hand bitch zzzzzzzzzzzzzzzzz.
If there was ever a time I was willing to catch a case at work, it was there.
Bonus: Serious, it got to the point I had to come in and tell this idiot that he can only ask me questions today if he calls me by my name...and my name has changed today...and no, you can't ask me for it cos you need my name to ask me questions.....FUCK OFF kkthxbai.5 -
⬜️Finish my indie Game
⬜️Publish my Indie Game.
⬜️Make my wife pregnant.
⬜️Clean codebase current C++ job
⬜️Learn Piano play
⬜️Create clean coding presentation
⬜️Be more productive10 -
Bugfix. About two years ago. Old C# codebase, MVC project... A fucking piece of it was sending money to the wrong Dynamics account, FOR TWO FUCKING YEARS.
Anyway...4 -
The superhuman feeling of going back to your code after a week and it all makes perfect sense, the variable names are intuitive, the doc strings are comprehensive, and the general codebase structure is sensible.2
-
Let an expert consultant write your code, they say. It will be all right, they say.
Found this today in a legacy codebase.
3 -
Sometimes I write awesome code that executes well as intended with proper file structure and clean codebase and sometimes I bring shame to my family.8
-
Fellow dev complaining about server.
Me: My servers could handle the 10x traffic. If they weren't busy apologising for your shit codebase !
*First Rant btw*6 -
When you can't figure out where you are supposed to add your code in the teams massive android spaghetti codebase. So you just add logs to every function that might be related to track down the function you need.
1 -
While trying to learn a legacy codebase, I realize one library supports almost everything. I decide to look it up.
Last updated: 19962 -
found this in our codebase today
try {
//do something
} catch () {
try {
//do something else
} catch () {
try {
//do something else else... this goes on 4-5 levels deep
} catch () {
//log... couldn't do
}
}
}9 -
Do not assume that the current codebase is perfect, or even remotely close to an example of acceptable style/structure.8
-
FUCCCCCCCCCCCKKKKKKKKKK.....I'm soooooooooooooo bored.
I'm a contractor, been here 2 months, yet to write any code. All I do is WhatsApp and devRant.
Siigggghhhhh, someone shoot me.13 -
Riddle me this Batman, why am I constantly afraid that other developers are going to fuck up my work after my time on the codebase?12
-
personalproject C++ codebase:
- Clean code,
- 1 class per file,
- naming conventions
- comments .
- No more than 10 files per folder
Work C++ codebase:
- 22 classes per file.
- Classname not the same as file name
- weird variable names CmdStng
- All files in one source folder.
- Source control from 20 years ago
Me every time I cannot find anything I wondering why it is in a different file on line 3574 inside another class with an unrelated filename6 -
If refactoring scares you, fuck off out my team.
If you keep code in the codebase simply because it took you ages to write it, fuck off out of my team.
Some people must be wishing pain and suffering upon themselves and their colleagues.8 -
This is the fucking data warehouse............
10 FUCKING INDEXES IN THE ENTIRE THING!
Btw...that includes Primary Keys
5 -
#3
There are like 50 views. But that's not the bad part about it. Each view is backed up twice or more within the same vie directory by adding a date to the views name.4 -
Went to a Hackathon, the platform looked like bs and the documentation was mehhh. So spent the time sleeping, waking only to eat Pizza :3.
(Know it was bs when no one cared >.>)2 -
> MISTER IHATEFORALIVING, YOU CAN'T CREATE YOUR FUNCTIONS! YOU MUST USE WHAT WE ALREADY HAVE, OTHERWISE WE FILL OUR CODEBASE WITH USELESS FUNCTIONS!
The very much useful functions in our codebase:
11 -
There's always a moment when your entire codebase starts breaking up piece by piece and you just wonder why did you choose this job, why you are a programmer, why you don't work at a bar or something like that9
-
> turning the whole codebase into a muddy ball of dirt because the leader didn't like 1 (one) call to an async function on startup
Way to go buddy, you sure show them how it's done. -
Today, I found this gem here in the codebase I've taken over:
#define BYTE unsigned char
FFS, use typedef, it's there for a reason. Solving the puzzle in the first comment.6 -
The ability to understand every codebase immediately to the point where I:
* don't need to rely on the documentation
* know exactly where bugs are
* know how a change (bug fix, new feature, etc.) affects other areas of the project recursively
Obviously because it's a waste of time hunting that occur when modifying a codebase, no matter how carefully one writes tests or tests their code, something could always sneak in because it's not always apparent how a change ripples through your codebase.
It's tiresome and especially annoying when working with core modules1 -
Junior dev: Can I run lint on your codebase
Senior dev: hmmm
Jdev: Its a very nice code inspection tool
Sdev: Go ahead
Jdev: wow 50 errors
Sdev:
1 -
I will turn this unholy, steaming, volatile, fubar, absolute shitstorm of a codebase into a thing of beauty, if it's the last thing I do!1
-
Being thrown in the deep end, baptism by fire is the best/worst way to learn a new codebase
Its not appropriate for everyone but it weirdly works -
!rant
Going to the gym really helps with concentration and may give you time to focus on things that are unresolved on your codebase.
It will also make you sexy as hell. Being sexy as all hell is good and gold.
Remember that10 -
Ahhhhhh anyone here use yED? I don't know how i even worked out diagrams before this. For the past couple years this has been my choice diagramming tool <3
Top image is before, bottom is after a single click. I just join boxes and let it work it out at the end. Then obviously do some adjustments to read how I like but seriously makes it easier to trial various layouts. I even make stuff in yED before recreating in something like Visio, if need be.
If anyone got another diagramming tool they like to use, post below (trying to add new stuff to my toolbox lol)
EDIT: Ahh, tried but you can't see the lines after the image gets compressed after upload (and DarkReader on chrome isn't exactly helping :p).
9 -
100% of the code defects from a recent code review are from code copied from elsewhere in the codebase.1
-
Do anybody here work with a codebase that actually has tests?
Or at the very least, the codebase has a domain layer, rather than puking lines of code randomly in the controller?
Am I trying to find an unicorn?7 -
I just received my first pull request today.
It wasn't what I wanted, expected, or hoped for.
It was a full-on codebase rewrite.4 -
I know this is kinda late but it just came in this morning..
With the current codebase I'm working with, it's not that bad of an option...😉
1 -
Sometimes my boss wants me to fire a bullet without a gun, they want me to throw the bullet so hard that it feels like it was shot via a gun.
Maintaining a legacy app sucks so bad when you don't even have the full codebase and some douche bag decided to just randomly throw the codebase on the fucking SVN. 😠1 -
- the first time I have to touch a GO codebase
- it's the day GH goes down
come on, what's happening here! First dR, now GH? Tomorrow what - SO's turn?7 -
The legacy codebase, episode 4584985948:
- outdated comment
- die parentheses space string no-space parentheses
- die AND exit, just to be on the safe side
- won't comment about the screaming boolean
- at least they used triple equals (and yep, that's a font ligature)
4 -
The legacy codebase, episode 94385948:
How to neatly organize your code in the age pre-docblocks.
Bonus: could this function be renamed to colectomy? Or maybe de-punctuation?
(yep, probably a bad joke with a "typo", sorry)
Bonus 2: seriously? A function for that?
13 -
The codebase I'm currently working on is so fucking damn wrong that I made a folder for screenshots called "facepalm".2
-
Rewriting the entire codebase anytime I learn that I was doing something wrong.
Rewriting entire functions whenever I see that my coworker coded bullshit on the fly.
In a nutshell, I should stop trying to rewrite everything!2 -
so... 9 years ago we had this super awesome codebase. 1 file, complete logic COPIED to be used in ui and service/daemon. I scrolled to the middle of the file and there was no source. it was out of bounds of my monitor to the right because of nested ifs. ok... what the fuck!! the worst part: I had to implement a new FEATURE into this mess. 2 days. I said it would not work as expected because the feature was not thought through. but project said let's gooooo! ok there I was, a junior with an impossible to implement feature and a codebase from hell. I've implemented something, all night long. next day it was the problem of the consultants. they called me, I told them why it's impossible that this would ever work, they understood and talked to the customer. he accepted the solution. WTF?! anyway, in those days I thought about quitting developing software as my daily job....4
-
we need you to do migrations in a legacy codebase which includes changes against a tool you will not have access to test against1
-
Forgive me for I have sinned.
I feel like I need a bleach shower after having had to write these methods in my Dart codebase
11 -
Best: Becoming an IT contractor
Worst: Not telling more people to "fuck off and go fuck yourself if you're not going to be helpful" while I was perm -
You know your codebase is fucked beyond restoration when a one-dimensional array is indexed using two indices and this formula.
FUCK.
8 -
One of our clients codebase, once almost completely PHP, now officially contains more JS than PHP code. I don't know if we should celebrate or cry.9
-
Why every day I have to fight for a charger cos the manager needs his phone on a constant charge from a power socket.
Fuck you and no I don't care that your shits gonna die now and yes, every fucking day we're doing this, don't fuck with me. My laptop > your phone and your ingress game
2 -
Couldnt fix a bug that conflicted with an unrelated codebase. A 1 in a million issue on github.
Had a wank.
Bug fixed, pushed, and deployed 30 minutes later.2 -
So, awesome clip to use for testing... Problem is, I found this in the codebase for a production app.
*Facepalm*
1 -
I worked at a startup that indulged in pair programming thing. Where as a junior, you'd be partnered with a senior developer.
My mentor, always insisted on having shortest variable names possible, so that the "size of codebase" will be very small.
It was a nightmare going through his code and understanding what's he's done. Best part, no comments as well.
In a way it has primed me to go through any codebase possible.5 -
When you node_modules (npm) and vendors (composer) folders account for 80% of your codebase size ...
3 -
After 1 year of working as android dev and coding in java, finally switched to another startup where everything is in Kotlin where I will be the only one maintaining that project.
Me: This code has almost no comments
Senior dev: Code is pretty self explanatory
FML
At least she spent 4 days with me and walked me through the code, so I'm not totally lost which is great!2 -
Randomly reviewing a coworker's c++ codebase revealed he was locking at the beginning of a critical section, but explicitly calling unlock for each and every error-handling branching within it. And yes, he forgot to unlock at several places.
That's just not RAIIght.
-
!rant
Today was the first day I ever added @deprecated annotations to our codebase at work
I'm not sure why, but it felt amazing to use those for the first time ever in an active project I work on1 -
This is hands-down the worst codebase I've ever touched. 50% laziness, 50% poorly-conceived alterations to business logic. One of those where if it isn't throwing an error, you DON'T TOUCH IT.
8 -
I want a job where I'm left to just refactor a horrible legacy codebase and make it easy to change5
-
Fuuuuuck this.
The shit i see at work with some fucky codebases.
I should have just gone to music school.
Oh ya, i never shared that with you devrant fam. I was going for music school before comp sci.
:)
But yeah, wonder how that would have gone.6 -
When the CIO referred to our entire backend system as a "heritage" codebase in a press interview.
Cue every backend developer scrambling to change projects, every manager scrambling to reassure the backend developers, and HR scrambling to hire new backend developers. -
Working with old codebase...
multiplyNumbers(2,5)
//adds the numbers together
What the fuck??! 4th grade math-terms??! This is real, btw4 -
Working in a preexisting codebase with 137 typedefs spread over 26 files, both ".h" and ".c"
Gonna be a long week. -
At my workplace, we are working on the codebase from 1999. It's built on Oracle Forms and Reports. Fuck my life 😔5
-
Have you ever encountered a situation like this before?
You worked in a team, made many adjustments in the codebase, and all the changes you've made are the best practice (after some research or asking the community).
But the team leader decided to go with the "messy" version of the code and the team leader does adjust the principle of "bad code" in favour of your coworker, just because he/she is a friend of the team leader.
So, whatever you adjust or contribute is simply nullified but any adjustments made by your coworker are considered "new updates".5 -
Working on codebase of a 20+ year old system that the company I work for bought five years ago and in that time there’s been no refactoring, no security updates, no attempt to create automated testing (there is none), new features have just been built on the codebase with no regard for quality and it’s just spun into the horror cesspool that it is today.
I joined one year ago and I’m slowly refactoring the codebase and updating it to get it to a more modern codebase, cleaner code, faster load times and creating a ton of dev documentation so the devs in India can start getting into best practices and start producing quality code.4 -
Writes rant, accidentally refreshes page...
.
.
.
Writes lazy rant instead.
(Was a good one aswell but im less stressed about it now :p)3 -
I hate giving estimates, especially for projects when you hardly know the codebase. But yet everybody expects you to deliver everything and everything on time.
Just get off my back maybe then I can actually finish something.
Thank you for listening. <33 -
When I have to apply a strong coat of
reverse engineering to understand an
open source codebase, what's the
point of being open.
No but really, the
WORKS ON MY BRAIN
movement is quite strong ..6 -
Every work experience so far.
The first one... Internship abroad, very messy codebase, almost no code review.
At the end I was so tired I started watching movies during worktime. -
For the love of sex, can someone help me out??!!
There is a VS Code extension that helps in creating a step-by-step tutorial of a codebase. Can someone please tell me its name?!
Google is a bitch today.4 -
Upsides of an atrocious, 10year old legacy PHP/(improperly used) CodeIgniter codebase:
When you actually manage to force it to be able to do the new thing it needs to be able to do, you feel like a God.
Downsides of an atrocious, 10year old legacy PHP/(improperly used) CodeIgniter codebase:
Everything else, especially the process leading to that single upside. -
What if an enormous asteroid hits the entirety of earth and all our codebase, hardwork, passion, and js frameworks get wiped out?6
-
Small rant for today: why in God's name do some people feel the need to ignore the conventions of the frameworks THEY chose to use for theyr projects, and start just throwing stuff randomly around the whole codebase?
ARRRGGHHHH...
Phew...all better now :)1 -
I have never encountered a codebase so horrendous. The styles are so fucking bad.
Give me a codebase with a poorly implemented programming langauge, fine.
Give me a codebase with styles that have been copy/pasted off Stackoverflow a million times until something works, not fucking fine. -
FUCK MICROSOFT!!! WHAT THE ACTUAL FUCK!?!?!?!? WHY IS THIS EVEN A THING!?!?!?!?
WHYYYYYY HAVE WE GOT A FUCKING DARK THEME IF WHEN I ADD ANNOTATIONS IN SSIS IT'S HARDCODED COLOURS.
No...seriously...not only am i doing this bullshit waste of time redundant annotations for some bullshit client that thinks they know shit but when I use the dark theme like a normal person, if you go back to a normal theme, all annotations in white.
Just finished like 30 packages on this slow ass remote connection and now all these backward ass people that use light themes (like everyone but me) can't see anything written.
Fuck you Microsoft!!!!! Soooooo many fucks for you right now....don't even know how to express the fucks.4 -
The four day rewrite of my codebase did... nothing...
No improvement. No detriment.
Just nothing...
Okay then.10 -
Overhears colleague say 'Ohh there's a plugin for that'. Few weeks later i find the dumb fuck added it to the codebase and not use the dependency manager. I'd happily shoot the senior Dev who peer reviewed it but looks like this pleb merged straight in!
With a codebase overflowing with duplicate frameworks and unused jquery plugins I'll be burning the god damn place down come next week!2 -
My biggest dev ambition is to continue supporting and improving the same codebase for at least 5 years.
That codebase is already 6 years old and going strong.2 -
A quick hack that does what the user needs it to do is much better than a beautifully crafted codebase that doesn't solve the user's problem2
-
Sharing my learnings to the community
“Reactive Streams are so simple” https://codeburst.io/reactive-strea...
Codebase is here. https://github.com/mohanramphp/...1 -
Big company asking me about query optimization during a DEV position interview... Do you really have no one better than me to optimize your queries?
I'm really afraid of your codebase now... Might decline if I pass...7 -
You do not own your companies code. Of you hate working at your job, don't let the feeling of responsibility for the codebase keep you there. I keep learning that lesson.
-
Just learnt that Stack Exchange servers are using Windows servers with IIS. Codebase written in C# (probably ASP .NET). Not sure how I feel about this.19
-
The moment I realized test cases are just super tiny applications that make use of parts of your codebase to run things and see what happens.1
-
Got one right now, no idea if it’s the “most” unrealistic, because I’ve been doing this for a while now.
Until recently, I was rewriting a very old, very brittle legacy codebase - we’re talking garbage code from two generations of complete dumbfucks, and hands down the most awful codebase I’ve ever seen. The code itself is quite difficult to describe without seeing it for yourself, but it was written over a period of about a decade by a certifiably insane person, and then maintained and arguably made much worse by a try-hard moron whose only success was making things exponentially harder for his successor to comprehend and maintain. No documentation whatsoever either. One small example of just how fucking stupid these guys were - every function is wrapped in a try catch with an empty catch, variables are declared and redeclared ten times, but never used. Hard coded credentials, hard coded widths and sizes, weird shit like the entire application 500ing if you move a button to another part of the page, or change its width by a pixel, unsanitized inputs, you name it, if it’s a textbook fuck up, it’s in there, and then some.
Because the code is so damn old as well (MySQL 8.0, C#4, and ASP.NET 3), and utterly eschews the vaguest tenets of structured, organized programming - I decided after a month of a disproportionate effort:success ratio, to just extract the SQL queries, sanitize them, and create a new back end and front end that would jointly get things where they need to be, and most importantly, make the application secure, stable, and maintainable. I’m the only developer, but one of the senior employees wrote most of the SQL queries, so I asked for his help in extracting them, to save time. He basically refused, and then told me to make my peace with God if I missed that deadline. Very helpful.
I was making really good time on it too, nearly complete after 60 days of working on it, along with supporting and maintaining the dumpster fire that is the legacy application. Suddenly my phone rings, and I’m told that management wants me to implement a payment processing feature on the site, and because I’ve been so effective at fixing problems thus far, they want to see it inside of a week. I am surprised, because I’ve been regularly communicating my progress and immediate focus to management, so I explain that I might be able to ship the feature by end of Q1, because rather than shoehorn the processor onto the decrepit piece of shit legacy app, it would be far better to just include it in the replacement. I add that PCI compliance is another matter that we must account for, and so there’s not a great chance of shipping this in a week. They tell me that I have a month to do it…and then the Marketing person asks to see my progress and ends up bitching about everything, despite the front end being a pixel perfect reproduction. Despite my making everything mobile responsive, iframe free, secure and encrypted, fast, and void of unpredictable behaviors. I tell her that this is what I was asked to do, and that there should have been no surprises at all, especially since I’ve been sending out weekly updates via email. I guess it needed more suck? But either way, fuck me and my two months of hard work. I mean really, no ego, I made a true enterprise grade app for them.
Short version, I stopped working on the rebuild, and I’m nearly done writing the payment processor as a microservice that I’ll just embed as an iframe, since the legacy build is full of those anyway, and I’m being asked to make bricks without straw. I’m probably glossing over a lot of finer points here too, just because it’s been such an epic of disappointment. The deadline is coming up, and I’m definitely going to make it, now that I have accordingly reduced the scope of work, but this whole thing has just totally pissed me off, and left a bad taste about the organization.9 -
Swear work is where you I go to fix other peoples poor design decisions and clean up the bullshit that comes out of said decisions.
CANT!
BE!
FUCKED!
How you have so many years experience and still design in way that ensures that maintenance /improvements/touching in the future is a huuugggeee clusterfuck.
Hey, I got an idea, lets make this whole data warehouse without a single index or primary key cos you know, that's the Kimball Method.2 -
FUUUUUUUUCK!!! Even the compiler has given up on this codebase! And it's still 2PM..............ON A MOTHERFUCKING MONDAY
2 -
How fucked are you if someone mistakenly deletes the codebase for Nodejs, reactjs, npm, vuejs, angularjs?21
-
God damnit!!
Just got a team assigned for the course I follow and the codebase they work looks like someone shit on the floor and dragged it all over place. No consistency, no clear structure.
The project has to be built in PHP (which is fine by the way) following the principles of MVC. Did I say the codebase looks like shit all over the place? Well that's exactly what it is!!
They use $_SERVER['DOCUMENT_ROOT'] everywhere!! In every fucking file!! Why the FUCK would someone possibly want to do that??
I know I'm not perfect, but what the fuck!!
Now comes the most weird thing. They have to work on a remote server without SSH access, so working with FTP is mandatory. This is because the school won't setup ssh. That's fine by me, but because of that they don't use git!! They upload files directly to the production server. They merge everything manually. I asked why they didn't use git and the answer was so fucking SHIT!! "Because the teacher wants to see who uploaded to the server.."
First off all: what happened to git blame? Second: Later I heard that there is only one FTP account, so all the things they said where just bullshit!!
The fuck.
Tomorrow I'm going to try and convince them to use git..1 -
That feel when your job's codebase is well-maintained, extensively covered with unit, integration and full product automated tests, everything is run through continuous integration, and every change has to be scrutinized and reviewed by multiple people; so you have barely anything to devRant about :(
-
Once I maintained one of the most used and fucked up codebases on the market with almost 1M+ daily users. (cannot say more, sorry).
It's written in PHP and is absolutely terrifying,
the first time I saw some lines of code I was about to scream and cry.
- spaghetti code
- no indentation
- random SQL query unoptimized
- unused vars
- Code is split among several files with no logical reasoning
- Mixed procedural and oop programming
- Unsanitised user input (yes, you got it right)
No test environment, no backup database, every commit goes straight to production.
It's a real disaster but the company prefers to keep it as it is without refactoring or anything else.
Just to make it clear:
It's not hatred against PHP, it's against the code's current status and the older programmers which used to work on it.5 -
is the job of being a "software engineer" (code monkey) supposed to be many parts of wannabe archeologist figuring out what the fuck is going on, happened, and reading the codebase , so you can figure out how to implement your jira ticket?3
-
Today, I applied StyleCop Analyzer to our project codebase.
over 40k of warnings sounds like fun :D2 -
First day developing in Rust. First day developing using the actor model in Actix. First line in a new production codebase.
Oh my5 -
Just landed my first "real" software engineering job! Now let me venture the land of messy and convoluted codebase.2
-
Fuck reuse, we should all take our repeatable code and manually repeat it everywhere it's needed so when we have to make a change we have to make sure we remember to change it in all the places and take hours to do a one line change.
...Also...fuck source control...
And they say I don't have fucks to give.2 -
And verily, he looked upon the codebase and cried out, "Who has done these terrible things?".
And there was wailing and gnashing of teeth.1 -
how do you tell a junior dev on your team there code is shit and please don't push to the main codebase without approval first,
without crushing them and and sounding like an ass cause there a good person just a n00b developer8 -
First day at work and after seeing the codebase and how everyone's talking about the code, I'm pretty sure I don't have imposter syndrome, I'm just that bad...13
-
I'm gonna kill him...no don't defend him, you lot are meant to be on my side!
IT'S FUCKING HUNTING SEASON.
I know, I know, you want context but I just can't now. I'm completely annoyed. Fuck data integrity, just duplicate rows randomly cos fuck you.
Work is about to turn into a murder mystery...without the mystery 😒
He doesn't even work here anymore, hope he forgets his password and gets locked out of everything he has.
Woosah....1 -
I just got told that a codebase written in javascript / typescript can't be built to last.
This is the type of rediculous stuff us Web Devs have to put up with.9 -
Made a comparison of a rather large codebase that I did for a client before in flask to perl dancer2 and ror. Obviously the rails codebase is larger. The flask version remains as minimal as it once did, even considering blueprints and the dancer version is small but really expandable and powerfull. It has some great things, it was inspired by sinatra so it has that magical approach to doing things but the code is solid and easy to understand imho. They really make it towards perl code is not the unreadable codebase as it once was and the syntax just clicks. Even for its api capabilities it works amazing with the front end (Vue.js) and I can honestly say that I really enjoy it.
-
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) -
When u converted ur codebase to Kotlin all because you heard about it, but really have no idea what Kotlin is!5
-
When you're working with an unfamiliar codebase where there are tons and tons of compiler warnings to start with... So of course your latest build-breaking mistakes are completely buried.
-
I feel like Git could have come up with a better name than "force push".
It just doesn't seem right... If your codebase doesn't want your commitment, you really shouldn't force yourself on them. No means no god dammit!3 -
man... tons of people are on the bootstrap train here.. I'd only use that if I wanted to double the size of my codebase and get 0 value out of it.5
-
What's your experience with continuous delivery? On every push to the master, the complete current codebase goes to production.
Of course not visible to all the users, but hidden behind feature flags.7 -
Come in, check task list, everything is basically "awaiting confirmation" or "acronyms you've never seen before talking about things that only like 2 people know about" or "check the powerpoint that you've never seen or even knew existed"
Sooooooo home time? Besides, it's POETS day ;).
For those that don't know (Piss Off Early, Tomorrow's Saturday)3 -
Some people are plain worse than a windows update.
Please overcommunicate! And ask questions. Assumptions are leading to nothing but overwork in a project where there are 8 devs contributing on a single codebase.2 -
Red Dead Redemption 2 Day - Awesome
No managers in today - fucking win
Work from home day - Can we get anymore wins?
Remote into computer that works for everyone - TODAY IT DONT FUCKING WORK -_-
Guess its a normal ass work day today and it's raining, fuck you Earth. No one is allowed to play RDR2 until I get home2 -
The feeling when you make some fundamental change in the codebase and thinks "this should make some integration tests fail", but it doesn't 😬😅
-
When the PM has been letting a fresh faced graduate loose on a codebase without any code reviews and you come back to some cronenburg level horror in your now crippled project. But it LOOKS like the mock ups.... * internal screaming *
-
probably when 8 hours before rushed release i pushed my part of the codebase into the wrong branch which fucked up everyone else's rushed release of different parts of that codebase and now a colleague had to spend several hours unfucking the repo on top of finishing the rushed release of his part of the codebase.
oh and in the end my code didn't even work as it was supposed to.7 -
Nothing like having to work on a codebase which has most of the class and variable names in a language you don't speak :/8
-
Found this in our Python codebase:
my_dict[key] = "%s" % str(my_dict[key])
Best way to convert a value to string xX -
When you spend weeks working on a new codebase in Python and you have to jump into the legacy PHP one to fix something nasty
3 -
Saw this in the Python project codebase today:
arg = '\"foo\"'
Which is funny, because '\"foo\"' == '"foo"' -
WOOOOH I HAVE BEEN GIVEN WORK.
.
.
.
.
Think I offended people cos I already finished it and when I got given it i said "Is this it?".
.....AND THIS MOTHERFUCKER TOLD ME TO DO A LOOP IN SQL TO UPDATE A TABLE. I'LL CUT OFF ALL PARTS OF HIM -
Heh, a review of HHKB Pro 2, think someone missed the point haha.
/Offtopic
Anyone got this keyboard and recommends? I mean, if no one responds I'm buying anyway just nice to hear from devs on it
3 -
I work in office block, he works in company next to me, was wondering where he been for the last couple hours. Started thinking he weren't in today hahaha.
Can't lie, might jump into the booth next to him 😂😂😂😂
-
> go into a codebase to add something simple
> rewrite 90% of it, breaking it in multiple different ways then fixing them
> too annoyed to add the simple thing
> leave
thanks for all the fish
https://youtube.com/watch/...2 -
NO! Use the description instead of the primary key because the key might change ................................................................................................................... vs the description .............................................................................................................. the key more likely .............................................. meh2
-
Best feeling?
Just leaving the office with a well-working codebase. And no bugs to fix.... until tomorrow morning. -
A big hurdle I'm fighting for last 1 year, is to convince a bunch of people having 10+ years of experience not to make production released of the same codebase from multiple branches.
-
When you pick up a codebase from 4 years ago of utter dissaray and static/hard coded in nature.
Then later meet said original developer presenting at a conference on re-useable code.
There is a feeling akin to meeting someone whom you have seen naked...2 -
i once explored our codebase and copied every line of commented out code into a text file. that file is over 350 lines long.1
-
Anything related to UIs or data science
That, working with a spaghetti codebase, or unhelpful and not nice teammates -
It's kind of unbelievable to me that whenever I ask my clients to share their codebase with me, their go-to response is -
Let me zip my codebase up and share it with you on Google Drive.2 -
do you have a CV driven software engineer(s) in your team/squad?
if yes, how do you deal with their dramatic changes in codebase every quarter?13 -
You've developed APIs. And they're working locally.
What's the issue in giving that to the front-end team to consume them ?? ( Said in angry raised pitch )
Somebody please let that dumbfu manager know that the codebase needs to be DEPLOYED on a server somewhere. Without that, you just can't magically build code from codebase and give it to people like code fairy !2 -
Just reed a comment in the fucking shitty codebase im working on :
/* temporary fix */
I’m fucking done guys !
1 -
Feel dirty writing in c. How do people even deal with unsafe pointer type casting/memory allocation/free? The codebase is plagued with memory leaks and there is no test.
I will just pretend I can't read c code and play dumb when shit happens12 -
Where can I get fullstack js codebase for small projects?
GitHub search shows humongous ones or otherwise repositories of js frameworks.
And/Or share your repos having the same
Gotta improve coding standards2 -
I'm reading my first Rust codebase after getting familiar with language for a while and I feel like a raw potato.
-
https://github.com/PwnFunction/...
Who led this flattening user input object into the Next.js codebase, also thinking that `runContext` is going to make better companion than `eval`?
Yet another reason to switch over Sapper and other Svelte minimalistic solutions, in my opinion.
1 -
WHY THE FUCK EVERY DAY YOU SEND A NOTE TO THE CLIENT TO TELL THEM A SQL SERVER JOB RAN.....!?!?!?!?!?!?
Seriously....no automatic messaging....FROM THE FUCKING IN BUILT SERVICE...the fuck is this manual life that people love to promote. -
I've a whole new respect for ElasticSearch. It's codebase is so insanely complex, that I'm seriously contemplating tracing out the flow on a big ass chart. Any suggestions on how you people work and debug so many asynchronous flows?
I have been working on a bug, for almost 6 days (to be read as 3 consecutive weekends), and the best I've done is, conceptually isolate where it's happening. I'm an open source noob, but I feel I've learnt a whole lot during sifting through ES' codebase. :)2 -
we were taught separation of concern when getting into webdev, don't write html inside your js codebase, don't write js inside html code base, don't write css inside your js codebase. People who taught us this, are violating this same principles by introducing stupid frameworks.
-
Now as I am refactoring the internal codebase of my company
I understand how important it is to have a good code documentation and writing patterns.
And also how much it is important to help his a junior when someone is in senior position when the junior was given the task of refactoring the internal codebase.
It's such a pain the brain situation these days for me. The documentation is not properly matched here and there and code writings are random. It makes me hates the code.2 -
This is probably the worst place to start my Rant saga but this is recent (this is one of the last few episodes of a 3 series cluster fuck of a job so you're missing out on all the straws that go into breaking the camels back and making him unaccommodating)
TL;DR I do good work, management dont like me and go out their way to try and fuck up my days
So, lets start, I'm a contractor, got funeral Tuesday, book leave, book WFH for day after.
I leave in 3 weeks, woman who is the CIO's right hand bitch takes me into a room the next day or so in the morning to discuss my WFH day. Leave on tuesday is cool but this WFH day...there's only so long until I'm gone so they want me to stay in for more face-to-face time blah blah blah (considering this woman isn't even part of the project I'm working on anymore because she decided to deflect it onto a underqualified junior with no PM experience)
So I sit there, thinking of all the blood and sweat that I have shed, the mountains I've moved just to be told to move the mountain somewhere else and whether coming in would kill me (in other words im fucking burnt out!!! I have built their GDPR database and app backend single-handedly with no requirements, project managers who can't plan and being chastised for asking for documentation/plan/anything written down and having the CIO who is also the fucking DPO ignore any emails/slack I send him relating to the project and having to keep up with a team of devs....).
So because there was a momentary silence, she decided to fill the gap
"Oh, you've done some good work so far and I wouldn't want you to ruin it all in these last 3 weeks. So just come in on the Wednesday so that we can have you here."
Hmm....yeah...i didn't notice what she had ACTUALLY said there, still thinking about can i be fucked? So she decides to add
"...there's only 3 weeks left, wouldn't want you to burn any bridges. Remember, we still have to give you a reference"
....Okay....shots fired. So i respond
"You saying, if I take a WFH day, you'll give me a bad reference?"
"Noooo no no no, not saying that, just that you've done good work and we wouldn't want you to ruin it"
"With one wfh day?"
"We just want you to come in because the developers might be coming here that week"
"Oh... I hear that...what day?"
"I dunno, it's not been booked yet"
".............................I'll think about it"
"There's nothing to consider"
*Start leaving room* "I'll think about it...."
So cool, obviously, had a think, decide to shoot over an email (or more accurately, a collection of bullets). Which basically said, in devRant translation, "Fuck y'all, I'm WFH on that day, I wish a motherfucker would fuck up my reference, we can go that way if you want it. *snaps fingers* I. WISH. YOU. WOULD! "
Woman says "I wasn't threatening you, was just saying...dont ruin your last 3 weeks, wouldn't want you to burn any bridges and that we still have to give you a reference"
What kind of Godfather comment is that?
Come in today, the CIO, who is a prick who don't like me for whatever reason, sends me long email trying to disrespect me and in the midst says "I’m sorry that you have chosen to react like this, I’m sure that [my bitch] was conveying a position that your last three weeks of contract are crucial for a smooth handover. I have made the decision to not require you to work from home on Wednesday. I understand you are on leave on Tuesday and therefore this is now extended to include Wednesday. I look forward to seeing you back in the office on Thursday. I hope this will make the situation better for all parties."
.................................thought you lot needed me in the office to ensure a smooth handover................logic..........people.............where the fuck do you get yours from!?!?!?!? All this just so they can say "We made the decision at the end :cool:" -
I find it really embarrassing how Twitter, whose mission was to give voice to those who are not heard, has become a puppet in the hands of a CEO who overnight changes the codebase to influence the crypto market for his own ends.3
-
Does the perfect codebase exist? Or is it just a myth?
PS. I'm just a new grad with ~3 years of experience, and in my 4th company now.10 -
TL;DR: idiot 'team leader' does mindless merge to master. Precious time wasted in a high pressure deadline environment.
So, i work currently at one of Belgiums largest consulting company's at brussels airport, we are moving their analytics platform to the cloud.
We use puppet to manage the systems.
When i started i noticed immediately that their 'development workflow' is hardly to be named as such, because they simply change stuff directly on server , manual 'temporary' fixes everywhere, hardcoded stuff, non validated code... Basically the way one would develop in their garage, not in a consulting company as this one. But that is just the beginning.
A month ago i did a major effort to equalize all the discrepancies between the codebase and the server. Ensured entire codebase to be validated, syntax checked, parsed, tested... It works. A 'great codebase overhaul' commit was PR'ed to master and got merged.
Yesterday the team lead, i'll call him 'B-tard' from here on, has also 'equalized the discrepancies between codebase, server and the restnof the stale branches on the repo' . i was doing my other work on my branch so no fucks given. This is where i should have given some fucks.
Anyways, today. The day starts every day with merging the master branch into your working branh because you need the latest working codebase, right?
Wrong!
This fucking dipshit smug b-tard has done a mindless merge of the entire codebase, effectively removing ALL validated working code for provisioning servers. Control blocks, lookup functions, lambda's... Basically everything he did not understand.
At the same time the project is already way beyond the allotted budget in pkney and time, so there is a huge pressure to have a working 'production' environment TODAY!
THIS MOTHERFUCKING B-TARD JUST MADE THAT IMPOSSIBLE.
i'm loving this assignment, i'm loving the PM, the collegues, the environment, the location... everything. All but this fuckibg b-tard that somehow got his position by sucking dick or licking ass or both...
I wanna get out asap.
Oh... While typing this and arriving at the room of the office... It is locked, i have no key.
Fucking asshole!1 -
sigh spent whole of yesterday dealing with shitty remote desktop connection, come in today, still shitty...wait what...ahhhhh no way.
*Connect HDMI to monitor and move RDC to monitor* Connection issues gone...ahhh fuck you.
#4KLaptopProblems #WhoKnewThatWasAThing2 -
So you know camelCase. Today I learnt there is a StUdLyCaPs e.g. "tHeqUicKBrOWnFoXJUmpsoVeRThElAzydOG" Imagine that in a codebase.2
-
This is how you grow your web app indefinitely:
1. Strip the codebase of all frameworks
2. Ban DRY principle. Don't reuse the code, period.
3. When feeling the urge to write a unit test, refactor the code instead.
4. When seniors “discover” a new “paradigm” that applies to the codebase and want to make a framework, rotate them.
5. Profit!9 -
My 11k LOC frontend codebase with webpack compiles into a 1.2 MB minified bundle file...RIP mobile users1
-
This is literally a line of code from this PHP codebase. w h y
$_POST = unserialize ( $_SESSION ['nyt_form'] );4 -
Turns out that stuff you commit and remove in later commits stays in git history and is searchable.
That, kids, is why you either squash your commits or just don't put swears in your debug code.
Especially if you have literally dozens of colleagues on the same codebase.
And you work in a large organisation where this sort of thing is frowned upon.
The crime was months ago, I wonder what the statute of limitations is on that.
And yes, in the years-long history of the codebase it's JUST me that's used any of the big three.2 -
The more I refactor a codebase that I have started for 2+ years ago the dumber I feel I have been.
There are too many things that are done completely wrong or in a stupid way.
Currently adding comments like in the picture...
1 -
Have you ever been in a situation where you're assigned to a new project, check the codebase and start wondering you've really made a good choice becoming a developer?1
-
I hate the Laravel community more than Laravel itself because they tolerated it to develop upto version 5.x with Laravel still pointing out errors in framework's codebase rather than a proper traceback to user's code.
Messed up shit.By Laravel.By PHP :)3 -
Fellow coworkers working with 20 years old legacy Delphi codebase.
Whenever I'm stuck on smth all I need to do is open a delphi source file and I instantly feel better for not having to deal with that shit. -
Lol, installing an Abp package literally breaks startup, you don't even have to use the package, just install it and the shit breaks.
God I hate this bloated piece of shit framework, can't wait to move this codebase to Go. -
Sooooo....worked at a place (which i think was my first rant on here lol) a little while back where, to keep a long story short, was treated like shit and still managed to pull out some magic for them before i left my contract (cos work pride).
Come to new company, it is a consultancy company. The project I worked on at the previous company, they had came (while i was there, i went to the meeting) and done some requirements analysis for them (that weren't even relevant, mostly because the CIO was a tard).
Come to find out today, through the grapevine, that these lot have been claiming that they done more than requirements and actually implemented the full solution and even wrote a case study about the shit they weren't involved in. "Oh look at this GDPR project we completed for this £400M turnover company and all the problems we solved".
More hurtful cos this project I done with no help from anyone, got moaned at every day, got my references threatened, wouldn't let me work from home but anyone else could. Serious, a lesser man would have punched the CIO....repeatedly.
What would you do? I'm getting sick of fighting in every job but also getting sick of never getting any credit for the shit I've done. -
TDD shows you just how much "junk" you've added to the codebase before without TDD. Then it becomes TDD refactoring. Wtf, what a mess. 😑4
-
Id probably still end up doing maintenance on our iPad app. No mere machine could ever comprehend that codebase and its *ahem* quirks....
-
Hey guys, I'm new to a dev management role. One of my responsibilities is to write tasks and do code reviews for the team. I keep getting issues in code due to the lack of contextual understanding of the codebase. How much detail should I include in a task? Should I expect my team to understand the context of the task/codebase?3
-
Writing a quality codebase is difficult when the people in team lead roles are the people who don't give a **** and enjoy writing quick and dirty code, rendering the codebase into a perpetual disaster that constantly needs new devs to blow out fires.2
-
Sigh, what is it with these cowboy SQL Devs? Why the fuck is this a pattern for anything?
New contract, new idiots, sigh.
EDIT: Had to change picture because Prod is different to Dev (but no dev has been done since release....smh)
4 -
What are your opinions of single file components in Vue? Will it actually help maintainability down the road for our codebase? Or do you think it’s better to separate the .js, .sass, and .vue?9
-
Sooooo anyway to hide my profile name from the home screen?
Feel that eventually someone from work is going to put 2 + 2 together and check my rants out xD3 -
I’m back for round two!
Anyone else have to use Feature Switches in their codebase, and if you do, what do you think?3 -
Which has an "easier" codebase for someone beginning as an open source contributor, Chromium or Firefox?3
-
"No, the Client doesn't like stored procedures so we have done all our TL parts of the ETL using a bunch of views on top of views on top of views."
Wish I could have been here at the start so I could have pushed back, sigh.
Siiiggghhhh, yet the client is anal about performance and even consistency in SSIS packages.....siiiggghhhhhh but we dont have SHOWPLAN permissions or even sp_who2 access...siiiigggghhhhhh.
If i expanded one of the final views, would be like 1k lines. For the amount of data, we move, there shouldn't be any noticeable processing time but it can take anywhere from 10mins to an hour.2 -
Someone in my programming development class at college asked "is php or c++ lower level" and after having worked with a large php codebase for over a month at work I wanted to laugh in pain1
-
Does anyone have some small projects I can contribute to for Hacktoberfest? I'm having some problems finding anything that doesn't have a humongous codebase or is dead.8
-
Except COVID-19, Airport security is also scanning preflight requests and incoming traffic for CORS with its dated test kit (found this unused gem in an old PHP codebase):
-
"wow, this headless looks pretty cool"
5 minutes of reading further:
"The codebase is written primarily in PHP"
Ah, yes.
So, what is you r favourite headless CMS out there?2 -
You join a new company and you're faced with loads and loads of abbreviations that only you don't understand. As if I'm not confused enough with with the new codebase and process and everything.
-
The first company I developed software for had no coding conventions and it was visible in the codebase of almost all of our products. This is why I follow the coding conventions for every language I use.
-
Why do people refuse to use cli tools development enviroments?
I'm wasting my time cleaning a drupal codebase bc the previous dev committed the modules instead of using composer....1 -
Finally working on rewriting the core of our internal platform on CakePHP 3.
It feels so good leaving the legacy codebase behind!4 -
Duck whoever thought using jruby was a good idea! fuck this codebase, outdated dependencies hell and fuck most of the ruby gems documentation
-
How do you guys deal with working in Monolithic applications?
Think > 200 project in a single solution, each which a hefty chunk of classes.
I've been working in that codebase for almost a year now and still get lost in it.3 -
Ugh trying to refactor a Node.js MUD codebase to use mongodb. It currently accesses/stores it's data in json files via synchronous FS operations. Callback and/or .then hell, here I come!
-
In comes the new developer messing the repository with unreadable two space indentation in our backend codebase. I can understand it being useful to keep code within the horizontal editor "viewport" for stuff like JSX, but otherwise it's really fucking ugly and feels like the code is not indented at all
We're not using any tools for automatically standardizing code style yet, what do you recommend? If it's at all relevant, our codebase is in TypeScript.5 -
My first working code added to the office's project's codebase. It's really an amazing feeling to see my written code along with other dev's code. The senior developers were very supportive and helpful. There is a lot to learn. 😁
-
We've been asked to develop an app, normally we counter-pitch the 'web' prefix because it means one codebase, but they don't want that so...any suggestions for a decent cross-platform framework? App is just text and video, nothing too taxing for the device.10
-
Doing what I dislike... documentation.
and I have to make the readme files for every directory within the codebase.!!3 -
Anyone here familiar with the LibreOffice codebase? Cause I want to modify Math to be used as a formula database.1
-
lol..
man asked me to upload a project and give him the zipped codebase.
I deleted all comments, duplicated files unnecessarily, used complex structures and gladly handed it over.4 -
Code comment in legacy codebase that says "Mr.Foo Bar doesnt understand why this is required but removing it may result in spontaneous combustion"
-
Multitasking is never easy. I can't debug code on one codebase and write new feature for another codebase at the same time.
-
Java and Groovy are like these two daughters, one going to church every Sunday and one listening to Slipknot.
I would not show our JobDsl codebase to any Java developer, (s)he would cry a lot.
Top Tags
Weekly Rant
View