The worst bad practice I do is I keep going to work.

Many years down the road I will probably look back and say I should have spent more time with my wife (who are you?) and children (wow, you are tall).

Worst bad practice..

Manager: I need code today
Developer (thinking) : let me give it without unit test. Anyways tester will test it.

Manager to tester: complete testing fast.

Tester(thinking): developer must have unit tested it. Let me skip it.
Enjoy testing completed.

God help clients.. 😊

After I spent 4 years in a startup company (it was literally just me and a guy who started it).

Being web dev in this company meant you did everything from A-Z. Mostly though it was shitty hacky "websites/webapps" on one of the 3 shitty CMSs.

At some point we had 2 other devs and 2 designers (thank god he hired some cause previously he tried designing them on his own and every site looked like a dead puppy soaked in ass juice).

My title changed from a peasant web dev to technical lead which meant shit. I was doing normal dev work + managing all projects. This basically meant that I had to show all junior devs (mostly interns) how to do their jobs. Client meetings, first point of contact for them, caring an "out of hours" support phone 24/7, new staff interviews, hiring, training and much more.

Unrealistic deadlines, stress and pulling hair were a norm as was taking the blame anytime something went wrong (which happened very often).

All of that would be fine with me if I was paid accordingly, treated with respect as a loyal part of the team but that of course wasn't the case.

But that wasn't the worst part about this job. The worst thing was the constant feeling that I'm falling behind, so far behind that I'll never be able to catch up. Being passionate about web development since I was a kid this was scaring the shit out of me. Said company of course didn't provide any training, time to learn or opportunities to progress.

After these 4 years I felt burnt out. Programming, once exciting became boring and stale. At this point I have started looking for a new job but looking at the requirements I was sure I ain't going anywhere. You see when I was busy hacking PHP CMSs, OOPHP became a thing and javascript exploded. In the little spare time I had I tried online courses but everyone knows it's not the same, doing a course and actually using certain technology in practice. Not going to mention that recruiters usually expect a number of years of experience using the technology/framework/language.

That was the moment I lost faith in my web dev future.

Happy to say though about a month later I did get a job in a great agency as a front end developer (it felt amazing to focus on one thing after all these years of "full-stack bullshit), got a decent salary (way more than I expected) and work with really amazing and creative people. I get almost too much time to learn new stuff and I got up to speed with the latest tech in a few weeks. I'm happy.

Advice? I don't really have any, but I guess never lose faith in yourself.

My worst bad practice:

Saving my Linux Root SSH Keys on a Cloud Storage company.

Have them there, so I wont loose them ever. I password protected them, but you never know what the NSA/FBI/CIA can do 😉

Confessions: Worst things you do which are 'bad practice'

My worst practice is trying to reinvent the wheel.
I will spend hours trying to write a function that's already in string.h

This was not exactly the worst work culture because the employees, it was because the upper level of the organization chart on the IT department.

I'm not quite sure how to translate the exact positions of that chart, but lets say that there is a General Manager, a couple of Area Managers (Infrastructure, Development), some Area Supervisors (2 or 3, by each area), and the grunts (that were us). Anyway, anything on the "Manager" was the source of all the toxicity on the department.

First and foremost, there was a lack of training for almost any employee. We were expected to know everything since day-1. Yes, the new employees had a (very) brief explanation about the technologies/languages were used, but they were expected to perform as a senior employee almost since the moment they cross the door. And forget about having some KT (Knowledge Transfer) sessions, they were none existent and if they existed, were only to solve a very immediate issue (now imagine what happened when someone quit*).

The general culture that they have to always say "yes" to the client/customer to almost anything without consulting to the development teams if that what was being asked to do was doable, or even feasible. And forget about doing a proper documentation about that change/development, as "that was needed yesterday and it needs to be done to be implemented tomorrow" (you know what I mean). This contributes to the previous point, as we didn't have enough time to train someone new because we had this absurd deadlines.

And because they cannot/wanted to say "NO", there were days when they came with an amount of new requirements that needed to be done and it didn't matter that we had other things to do. And the worst was that, until a couple of years (more or less), there was almost impossible to gather the correct requirements from the client/user, as they (managers) "had already" that requirement, and as they "know better" what the user wants, it was their vision what was being described on the requirements, not the users'...

And all that caused that, in a common basis, didn't have enough time to do all this stuff (mainly because the User Support) causing that we needed to do overtime, which almost always went unpaid (because a very ambiguous clause of the contract, and that we were "non-union workers"**). And this is my favorite point of this list, because, almost any overtime went unpaid, so basically we were expected to be working for free after the end of the work day (lets say, after the 17:00). Leaving "early" was almost a sin for the managers, as they always expected that we give more time to work that the indicated on the contract, and if not, they could raise a report to HR because the ambiguous clause allowed them to do it (among other childish things that they do).

Finally, the jewel of the crown, is that they never, but never acknowledge that they made a mistake. Never. That was impossible! If something failed on the things/systems/applications that they had assigned*** it was always our fault.

- "A report for the Finance Department is giving wrong information? It's the DBA's fault**** because although he manages that report, he couldn't imagine that I have an undocumented service (that runs before the creation the report) crashed because I modified a hidden and undocumented temporal table and forgot to update that service."

But, well, at least that's on the past. And although those aren't all the things that made that workplace so toxic, for me those were the most prominent ones.

-

* Well, here we I live it's very common to don't say anything about leaving the company until the very last day. Yes, I know that there are people that leave their "2-days notice", but it's not common (IMHO, of course). And yes, there are some of us that give a 1 or 2-weeks notice, but still it's not a common practice.

** I don't know how to translate this... We have a concept called "trusted employee", which is mainly used to describe any administrative employee, and that commonly is expected to give the 110% of what the contract says (unpaid overtimes, extra stuff to do, etc) and sadly it's an accepted condition (for whatever reasons). I chose "non-union workers" because in comparison with an union worker, we have less protections (besides the legal ways) regarding what I've described before. Curiously, there are also "operative workers", that doesn't belong to an union, but they have (sometimes) better protections that the administrative ones.

*** Yes, they were in charge of several systems, because they didn't trust us to handle/maintain them. And I'm sure that they still don't trust in their developers.

**** One of the managers, and the DBA are the only ones that handle some stuff (specially the one that involves "money"). The thing that allows to use the DBA as scapegoat is that such manager have more privileges and permissions than the DBA, as he was the previous DBA

Oh boy, finally something to rant about.

I got hired in a "small" company (not even 2000 people in it), then got "shipped" to a way bigger company. Basically, I work for this company (the french biggest internet / phone service provider) but in the name of my own. And this since last wednesday.

First off, I'm fucking stupid. After leaving the big company that I was in before, I swore to myself that from now on, I would work for smaller companies, mainly because I couldn't stand the inertia that big company have. You ask for something, you get it a month and a half after. The old company has about 6000 employees... This company has 98k people in it. Fuck. My. Life.

Now, to the rant: Orange (the company) decided that they had to move their office somewhere else. They set up a lot of things so that all we needed to do was to put things in boxes, to work somewhere else until next monday, then we could go to the new office on tuesday morning.

Keep in mind that I have been there for 8 days: I keep learning how they do their stuff. For example, if I need a specific docker image, I can't get it from the Docker Hub, the download will fail. However, if I hit an Orange subdomain's registry, I will get this image from a mirror. Because fuck logic.

When we join the company, they give us a Windows laptop ("yeaah we have useless but required Orange softwares that don't run on Linux" "Yeeaaah fuck you") that have a specific VPN allowing us to use the Orange network and, in theory, you can download docker images or clone orange repositories from that network.

In practice, you can simply just go fuck yourself. Why? Because whenever you want to curl, wget or pull anything (or even pip install), your connection keeps being shut down while it waits for the response's header.

The worst part? According to my (new) boss's evasive answers, the way to fix that works with glue, sticks and the power of the Force.

WHY THE FUCK DO YOU ENFORCE US A SHITTY OS FOR DEVELOPMENT, WHEN THE TOOLS YOU SHOVE IN IT WITH A FAKE SMILE DON'T EVEN WORK, AND WE HAVE TO HACK OUR WAY TO FUCKING WORK?

If this isn't the worst thing.

I was asked to develop a WordPress plugin as an intern developer and I've been on it since last week. I got stuck when i finally had the loops running but couldn't find a way to format the output without overwriting the existing values on each iteration.

For the last one week I've been showing the progress on my code to the CTO and this is how it has been.

Me: Hello. Everything is coming along fine, I have most of the functions running properly, do you mind looking into the algorithm?

CTO: Oh not at all, let's see what you got. Omg great code for an intern. I think you should add a new variable there and maybe clean up that function over there because it's deprecated now and yeah HaHa, Great work.

Me: Thanks xD I'll have it finished latest next week.

CTO: Oh great. I can't wait to see what you'd have by next week so we can install it on our WordPress.

*Next finally week comes and I'm done with the code.

Me: Hello, I'm done with the entire code! Want to take a look? The plugin works just exactly as described.

*CTO takes a look

CTO: Omg?

Me: Omg?

CTO: This is completely bad programming practice, so you are running 4 nested loops that all send queries to our data base and make changes to data. This would have a very drastic effect on the server considering the traffic we get.

Me: But you saw this exact code last week and said it was okay, I only changed some CSS since the last time.

CTO: Omg, we can't accept this, you have to develop it again from the scratch without using those loops and queries.

Me: What? Okay, fine. Any hints?

CTO: Yes.

Me: What?

CTO: Just start. That's the greatest hint I could ever give. And also, always have a plan before you begin.

Me: Yeah, thanks for those. It's the first time I'm hearing them and they would totally be applicable to building this thing.

A (work-)project i spent a year on will finally be released soon. That's the perfect opportunity to vent out all the rage i built up during dealing with what is the javascript version of a zodiac letter.

Everything went wrong with the beginning. 3 people were assigned to rewrite an old flash-application. Me, A and B. B suggested a javascript framework, even though me and A never worked with more than jquery. In the end we chose react/redux with rest on the server, a classic.

After some time i got the hang of time, around that time B left and a new guy, C, was hired soon after that. He didn't know about react/redux either. The perfect start off to a burning pile of smelly code.

Today this burning pile turned into a wasteland of code quality, a house of cards with a storm approaching, a rocket with leaks ready to launch, you get the idea.

We got 2 dozen files with 200-500 loc, each in the same directory and each with the same 2 word prefix which makes finding the right one a nightmare on its on. We have an i18n-library used only for ~10 textfields, copy-pasted code you never know if it's used or not, fetch-calls with no error-handling, and many other code smells that turn this fire into a garbage fire. An eternal fire. 3 months ago i reduced the linter-warnings on this project to 1, now i can't keep count anymore.

We use the reactabular-module which gives us headaches because IT DOESN'T DO WHAT IT'S SUPPOSED TO DO AND WE CANT USE IT WELL EITHER. All because the client cant be bothered to have the table header scroll along with the body. We have methods which do two things because passing another callback somehow crashed in the browser. And the only thing about indentation is that it exists. Copy pasting from websites, other files and indentation wars give the files the unique look that make you wonder if some of the devs hides his whitespace code in the files.

All of this is the result of missing time, results over quality and the worst approach of all, used by A: if A wants an ui-component similar to an existing one, he copies the original and edits he copy until it does what he wants. A knows about classes, modules, components, etc. Still, he can't bring himself to spend his time on creating superclasses... his approach gives results much faster

Things got worse when A tried redux, luckily A prefers the components local state. WHICH IS ANOTHER PROBLEM. He doesn't understand redux and loads all of the data directly from the server and puts it into the local state. The point of redux is that you don't have to do this. But there are only 1 or 2 examples of how this practice hurt us yet, so i'm gonna have to let this slide. IF HE AT LEAST WOULD UPDATE THE DATA PROPERLY. Changes are just sent to the server and then all of the data is re-fetched. I programmed the rest-endpoints to return the updated objects for a very reason. But no, fuck me.

I've heard A decided (A is the teamleader) to use less redux on the next project and use a dedicated rest-endpoints for every little comoutation you COULD DO WITH REDUX INSTEAD. My will is broken and just don't want to work with this anymore.

There are still various subpages that cant f5 because the components cant handle an empty redux state in the beginning, but to be honest i don't care anymore. Lets hope the client will never find out, along with the "on error nothing happens"-bugs. The product should've been shipped last week, but thanks to mandatory bugfixes the release was postponed to next week. Then the next project starts...

Please give me some tips to keep up code quality over time, i cant take this once more.
I'm also aware that i could've done more, talking A and C about code style, prettifying the code, etc. Etc. But i was busy putting out my out fires, i couldn't kill much of the other fires which in the end became a burning building (a perfect metaphor for this software)

Once again I have loads.

My best teachers were...

The contractor that taught me C#, ASP MVC and SQL Server. Dude was a legend, so calm and collected. He wanted to learn JQuery and Bootstrap so at the same time as teaching, he was learning from me. Such an inspirational person, to know your subordinates still have something to teach you. He also taught me a lot about working methodically and improving my pragmatism.

The other, in school I studied computing A-Level. 100% scored at least one of the exams... basically I knew my stuff.

But, as a kid, I didn’t know how to formulate my answers, or even string together coherent answers for the exams. This dude noticed, first thing he did was said “well you’re better at this bit than me, practice but you’ll be fine” (manually working out two’s complement binary of a number).

Second thing he did was say “you know what man, you know what you’re on about but nobody else is ever going to know that”.

He helped me on the subjects I wasn’t perfect on, then he helped me on formulating my answers correctly.

He also put up with my shit attendance, being a teenager with a motorcycle who thinks he knows it all, has its downsides.

As a result, I aced the hell out of that course, legendary grades and he got himself a bit of a bonus for it to use on his holiday. Everyone’s a winner.

Liam, Jason, if you guys are out there I owe you both thanks for making me the person I am today.

The worst, I’ve had too many to name... but it comes down to this:
- identify your students strengths and weaknesses, focus on the weaknesses
- identify your own and know when to ask for help yourself
- be patient, learning hurts.

You can always tell a passionate teacher from one who’s there for the paycheck.

What are your thoughts on working for a company that give their devs jira tickets that don't have any descriptions? I work for a big organisation (It's actually in the top 3 biggest companies in the country I live in) and I work in a team that has quite possibly the worst agile practice I've ever seen. We get tickets without any descriptions at all. The worst bit is then we get pressure from project management for not delivering things on time. Do they actually realise how difficult it is to deliver something without any business requirements? I have to have a million meetings before I even know wtf the ticket is about. It's incredibly annoying.

Petition to ban vague naming, e.g. "Logo.jpg". Whose ****ing logo is that!?

Worst practice -- our application isn't built to properly handle threads and I just added a Sleep statement to wait for the backend process to replicate its data. I feel so guilty and dirty.

Wouldn't call it a feature. More like worst practice. Data manager (and my boss at the time) kept using our website as a way to host large files 3rd party vendors/partners could download instead of using one of the many secure transfer methods out there to send them data. This was sometimes extremely sensitive data. No authentication or security that I could find. I went ballistic on him after seeing that.

Worst: lost my job due to the pandemic, and struggling to get interviews! Yes in spite of how well i did at my previous role (and please don’t give me crap about how they never would’ve laid me off if I was good, you’re just saying that to stroke your golden e-penis, you fucking reptilian scumbag) and with all that “experience” on my resume, I’m apparently not smart enough for these companies to even bother with. Yes if i kept failing tests a blind monkey would pass i would question my ability but that’s not the case. Yes my stack may be old but learning these newer tech stacks that recruiters love is a total cakewalk for me! They do so much cognitive lifting for you that I worry that if I don’t practice lower level stuff my mental capacity will diminish which is why I still solve leetcode problems lol.
Let’s not forget, I lost my dog this year too ☹️

I just spent an hour researching about how to do this thing in a particular JavaScript framework when I remembered I can do it in CSS 🤣 I'm so embarrassed I really need to practice my vanilla
Worst of all I did find StackOverflow answers with the framework solution but it's so easy in CSS

My worst common practice:
I do almost everything as root. Even programs which tell me not to run as root, I do run them as root.

What are yours?

Confession:
I've been working as C# programmer for an entire year, and I wrote desktop app as well as win services, but when it comes to practice (cause I moved to PHP about 7 months ago) on Codewars I go completely wrong, and it's even worst on Hackerrank.
Have to admit, feel so dumb and lost

I crash and burn during coding interview questions. Every. Time.

I just do. It's terrible. It doesn't matter how much I tell myself to slow down and just think it through first before coding...I end up coding first after a short period of thinking about it. Don't get it right, freak out...and well I crash and burn.

It bums me out. The worst part is that I'm so distraught about it that I take a break, and sit down and solve it in like 10 minutes...of course it doesn't matter since it happens after the interview.

I just need to practice solving these things to get that mindset right.

today has been one of the worst day of my life

- the parking situation went out of hand : i bought a new car 2 days ago, nd since last 2 days i have been just taking it out to practice for 1 hr in morning with the trainer. today one of our pesky neighbour took this opportunity and parked in our spot. i had to call my friend in the early morning to get it parked in a place far away from home . my new car is parked in an unsafe place , just because the neighbour wants to make me mad 😭

- office announced that since cto is coming, you must do wfo fod next 2 days. our office is tuesday nd Thursday, now i will have to go on friday too. plus our team lead is coming, so next weekend is going to be 4days wfo. they are giving random surprises, why not just tell us that its full wfo?

- one of our neighbour's bike got stolen in plain sight. our road is usually having a lot of people going around whole day, as its opposite to park. nd those neighbours have a hon ground floor, so they are almost always outside. we have installed a camera just 2 days ago, nd that caught the incident live. i am 100% sure that if my car had been parked here today, then it would have been my car 😭😭😭

- we friends went for a night stroll in my car. the car was mine, but my friend was driving it as he's experienced. we stopped at a food joint. i took the key from him for sometime because i was having fun playing with it . then when we were heading out, our key was gone!
i almost had a mini heart attack. my friends were not messing up with me. fortunately the restaurant had cameras , so we requested for cctv footage. in the footage we found that i accidentally put the key in the restaurant menu. and that fucking guy had taken away the menu!!!
imagine if he had given that menu to someone else 😭😭😭. our car would have been gone in a moment, as we were not even seeing the car from the window. imagine if the restaurant didn't had the fucking cameras 😭😭😭😭😭😭😭

life fucks super bad in a moment of truth

I'm not experienced in VB Forms. So can someone who is, tell me if I'm just too inexperienced or if Im right about this?
Im tasked with fixing some bugs in a VB Forms project that a privious employee wrote some years ago. When I opened the project and checked it out, there was over 5600 lines of code in the codebehind for the form.
I feel like this is somewhat bad practice, no comments, no documentation... Nothing. And to top it off, among the worst naming of Subs and variables ever. Stuff like: "Run", "Stop", "Feeder", "When Load".
Oh, and the best part? The guy forgot some test code in the software, so when he left, the software stoped functioning. For real, he coded in a dependency to his own account in The AD.

How can a novel emerging challenger software (written in Rust) take me 4 hours to install (still ongoing)?

Today I have decided to give Pijul a go. Pijul describes itself as a theory-sound alternative to Git, which I have wanted to get away from for a while now, due to various reasons -- many of which I saw Pijul advertise to have solved on design level.

So I set away a day to learn Pijul, today. Well, 4 hours after I sat down -- after a number of hilariously wonky failures of "Rust ecosystem" to do the right thing as I had to install Rust with some shell one-liners those insane wizards recommend for installation process (all in the name of "stability but not stagnation") -- Pijul has now been installing with the blasted `cargo` for an hour now (that's after 3 hours of getting to the point where `cargo install pijul` stopped exploding in my face) -- telling me I only have 40 crates more to install. Are they throttling me, perhaps? I don't care -- I should have been installing Pijul from a repository in accordance with my Linux distribution, or -- at worst -- download a BLOODY COMPILED PROGRAM IMAGE.

What is it with the hipster developers today? Everything they get of tools, they subsume and churn out intricate complexities the likes of which we hadn't seen yesterday. Tell me fellow developers who think installation of your software has to require three and a half novel "installation solutions" to which I can't be arsed to be made privy -- do you think your life today is easier than, I don't know -- wrangling with a Makefile and a C compiler (which today thankfully can do rather good job of standards compliance)?

I mean I wouldn't mind Pijul being written in Rust -- but it turns out Rust's advertised elegancy in practice is wrapped in so much "giftwrap" I feel like what desire I had to learn Rust myself, I'll stear well clear.

Here's an advice for developers in general -- an advice continiously ignored for decades -- stop blowing your original scope of delivery in auxilary packages you think you need to reinvent just because you can or because your mom is out of town! For programming languages like Rust this most certainly entails NOT writing your own package manager, with its own package delivery mechanism that has its own configuration file format and virtual machine to configure dependency resolution or what have you!

You wanted to write a programming language that has novel features you think we need? Fine -- write one and stop there. Watch it grow, and watch people who are busy working on other parts (scopes) of software to integrate your offer.

What a shitshow. Stop smuggling alternative package managers, installers, and discombulators with your actual product -- I only want the latter, I don't want the rest of your damn piping, walls, roof and a cathedral on top of it!

Don't be that guy starting with a pin, and ending up with a fucking diorama miniature of a pig farm in Netherlands. Jesus.