"Added more bugs to fix later" :D

A more experienced friend told me
"don't be a pussy, test in production"

I'm the one fixing the bugs, not him

Just got BUGS list from our Client and fuck- 95% of bugs are not even bugs :|

- No, changing the (not pre-decided) verbiage is not a bug
- Adding two more pages in the app is not a bug (what the fuck :|)
- No, APK file not running in iPhone is not a bug (goddamn :|)
- No, adding these "fuckin new" functionalities is not a bug (seriously ? :/)

AND

Mr "used to be a good coder" PM,

Getting "504 Timeout Gateway" error because Server is temporarily down is NOT a fuckin frontend bug

And No, writing Javascript with a proper design architecture is not a "complicated" way of coding
and fuckin No, Global variables and functions without any architecture don't make the programming "kind of better"

ps: And VB dot net is not a fuckin scripting language, VBScript is.

Thank you,
"buggy average coder"

Client: “Hey this thing isn’t working correctly.”
Me: “Hmm, looks like there was a bug in the last update. The team and I are going to work on a fix. In the meantime here’s a tool to help you get what you need.”
Client:”Yay!”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Hey, yeah, it’s the same thing. That bug I told you about? Yeah, we’re still working on it. We’ll let you know when it’s finished I promise but we’re trying to fix it without introducing more bugs.”
Client:”Ok sounds good.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Bro...we just went over this...”

*A little while later*
Same Client:”Hey seems like there’s a bug in our system that was found by -insert random coworker’s name here-. Are we looking into to this?”
Me:”Wtf dude.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me: -smashes my face against keyboard-

I greeted my staff this morning with the phrase

"Morning, mind if I ruin your Friday?"

They laughed, but won't be soon enough. The task we've been working on for weeks, ripping apart the codebase changing it to work a different way, fixing a tonne of bugs, making it faster and simpler to add features too. Well business has decided they want us to stop, undo it, spend a month on something "with higher ROI" and then finish it off after that.

Business are expecting this to have no impact on any of the timelines and just to be like flipping a switch. Now obviously I won't let that happen and fight back for more time, but yet another session of compromises, arguments, and yelling. YIPEEE!!!!!!

Sleep❌
Coffee❌
Bugs✅
Fixed bugs✅
More bugs✅
Curse bugs✅✅✅✅
Fixed bugs✅
Commit✅
Cry✅✅
18 hours✅
Heading home for sleep ❕

Me: Boss, your new project is ready, we've tested the technical aspect but we're waiting on your approval before deploying, will you test it?
Boss: yeah sure, I'll test it in 5

*2 weeks later*

Boss: why isn't that project deployed yet?
Me: you haven't tested it, and we haven't gotten approval
Boss: oh right, I'll go test it right now!

*2 weeks later*

Boss: I NEED that project to go live RIGHT THIS MOMENT!!!
Me: sure, have you tested it yet?
Boss: nope, but I need it
Me: well, I'll put it live, but me and my colleagues are shifting responsibility to you, since you haven't tested it. Are you sure?
Boss: yeah, yeah whatever...

*put product online*

*2 days later*

Angry call from boss, bugs have been found, tell him that he approved the state of the product and that the bugs will go on the to-do list...

Boss is extremely pissed, but recognized his mistake...

Now, the boss actually tests everything thoroughly at the moment we tell him to! No more bugs, complaints, and I got a raise!

Day 2 of debugging: I have more bugs now than I originally started with

6 months of internship made me realize that solving other peoples bugs is my biggest distraction.
Apparently I enjoy solving bugs more than writing clean code from scratch. 😐

Just who the fuck from apple thought its a good idea to make the FUCKING SCROLL BAR overlap, the FUCKING PROPERTY ARROWS, everytime i accidentaly hover over it? I cant change shit! I have to wait few seconds every time i accidentaly hover over the scrollbar so i can be able to FUCKING CHANGE the value!

Dear Apple Inc,

Fix your shit! We're paying 100$ a year for what? More bugs and toruture? I didnt sign up for this bullshit! Give us back some real quality products, or just buy the company Jetbrains and let them build the IDE for you instead.

I'm trying to sign up for insurance benefits at work.

Step 1: Trying to find the website link -- it's non-existent. I don't know where I found it, but I saved it in keepassxc so I wouldn't have to search again. Time wasted: 30 minutes.

Step 2: Trying to log in. Ostensibly, this uses my work account. It does not. Time wasted: 10 minutes.

Step 3: Creating an account. Username and Password requirements are stupid, and the page doesn't show all of them. The username must be /[A-Za-z0-9]{8,60}/. The maximum password length is VARCHAR(20), and must include upper/lower case, number, special symbol, etc. and cannot include "password", repeated charcters, your username, etc. There is also a (required!) hint with /[A-Za-z0-9 ]{8,60}/ validation. Want to type a sentence? better not use any punctuation!

I find it hilarious that both my username and password hint can be three times longer than my actual password -- and can contain the password. Such brilliant security.

My typical username is less than 8 characters. All of my typical password formats are >25 characters. Trying to figure out memorable credentials and figuring out the hidden complexity/validation requirements for all of these and the hint... Time wasted: 30 minutes.

Step 4: Post-login. The website, post-login, does not work in firefox. I assumed it was one of my many ad/tracker/header/etc. blockers, and systematically disabled every one of them. After enabling ad and tracker networks, more and more of the site loaded, but it always failed. After disabling bloody everything, the site still refused to work. Why? It was fetching deeply-nested markup, plus styling and javascript, encoded in xml, via api. And that xml wasn't valid xml (missing root element). The failure wasn't due to blocking a vitally-important ad or tracker (as apparently they're all vital and the site chain-loads them off one another before loading content), it's due to shoddy development and lack of testing. Matches the rest of the site perfectly. Anyway, I eventually managed to get the site to load in Safari, of all browsers, on a different computer. Time wasted: 40 minutes.

Step 5: Contact info. After getting the site to work, I clicked the [Enroll] button. "Please allow about 10 minutes to enroll," it says. I'm up to an hour and 50 minutes by now. The first thing it asks for is contact info, such as email, phone, address, etc. It gives me a warning next to phone, saying I'm not set up for notifications yet. I think that's great. I select "change" next to the email, and try to give it my work email. There are two "preferred" radio buttons, one next to "Work email," one next to "Personal email" -- but there is only one textbox. Fine, I select the "Work" preferred button, sign up for a faux-personal tutanota email for work, and type it in. The site complains that I selected "Work" but only entered a personal email. Seriously serious. Out of curiosity, I select the "change" next to the phone number, and see that it gives me four options (home, work, cell, personal?), but only one set of inputs -- next to personal. Yep. That's amazing. Time spent: 10 minutes.

Step 6: Ranting. I started going through the benefits, realized it would take an hour+ to add dependents, research the various options, pick which benefits I want, etc. I'm already up to two hours by now, so instead I decided to stop and rant about how ridiculous this entire thing is. While typing this up, the site (unsurprisingly) automatically logged me out. Fine, I'll just log in again... and get an error saying my credentials are invalid. Okay... I very carefully type them in again. error: invalid credentials. sajfkasdjf.

Step 7 is going to be: Try to figure out how to log in again. Ugh.

"Please allow about 10 minutes" it said. Where's that facepalm emoji?

But like, seriously. How does someone even build a website THIS bad?

Does anyone here feel like they're more of a debugger than a programmer ?

Like 70% of my time is spent investigating / fixing bugs and anomalies.

My boss is still forcing us to support IE11. Recently, we started having even more bugs with one of our vendors on IE. We filed bug reports with the vendor to fix it, and they came back with "no. Why would we fix anything for IE11? Not even Microsoft is fixing anything for IE11." Boss's answer: well, let's make a separate component for IE11. Probably using flash and/or silverlight. We asked about redirecting IE traffic to Edge, he said that's "the nuclear option." So, doing the thing that Microsoft suggests, that involves not much work at all is "the nuclear option"; ignoring industry standards and recommendations, introducing well known security vulnerabilities, losing money, and trying to circumvent the vendor that serves out our major product, however, is totally reasonable. Our IE traffic is less than 3% of our users at this point.

Am I the only one who solves more bugs in my head on the commute home from work than I actually do at work?

8:50am aight alarm clock, give me 5 more minutes

8:55am ok lets round it to 9, wake me up then

9:00am aight enough. lets just sleep for 1 more minute since 9:00 is too round

9:43am fuck

9:44am ok its time to finally study for the upcoming college exam

9:45am nothing but a fresh day to start studying for college

9:46am eh i dont have a lot to study so I'll do it in 2pm, I'll code my project instead

2pm hold on 5 more minutes until i finish coding this feature and then I'll study

5pm where the fuck is this bug coming from

5:504pm goddamn i found it

6:36pm holy shit its already over 6pm, I'll study at night

7:42pm ok its night now, time to study but I'll do it when i fix all bugs

8:14pm ok bugs fixed, commit. lets study

8:15pm you know what, im way too tired and exhausted from this coding, I'll take a short 30 minute break and then I'll study

10:15pm ok im feeling fresh bois lets study now theres not too much

1:31am damn this movie was good

1:32am fuck i forgot to study, I'll do it tomorrow

2:10am *posts this rant*

You write more bugs than code.

I don't think this applies to all bugs:

"It is more afraid of you than you are of it".

We passed a milestone: 250,000 phpunit testcases.

If it weren't for a heavily parallelized build pipeline which splits it out over 20 servers, it would take about 7.5 hours to complete.

Not hating on PHP, and without tests it would truly be hell...

But still, fucking hell, we outgrew PHP.

Not having a solid type system just means you either accept more bugs, or write thousands of unit tests to guard all the foundational cracks in the system.

On the bright side, I get a coffee break after every commit 😄

and the award for most downvotes stackoverflow post, is… well, stackoverflow. I posted this a while ago, but it got much better. -247, what a beautiful number. apparently there's a stackechange app, but instead of fixing its bugs, they made a stackoverflow app that does the same thing. go and give those cocksuckers a big, fat downvote! more pics and link in comments.

Always the same story:

Marketing: hey I'm gonna do a demo to a customer. They were asking for feature XYZ. That's ready on thr staging server right? Do you think I could use the staging server for the demo?

Devs: well feature XYZ is not 100% done. Basically just feature X is done, and it still has a few bugs. The deadline ain't for another month, since we gotta finish ABC first. I guess you could use the staging, but it has a lot of bugs.

Marketing: perfect!

*after presentation*

Marketing: the staging had so many bugs! Why didn't you tell me?! It was so embarrassing showing it to new customers! Anyway, they loved the new feature. We need it to be ready ASAP.

Devs: What?! That's gonna mess up with our schedule. You know what? Fine, but feature ABC will have to wait another month.

Marketing: Well, it'd be ideal if we could do both...

Devs: Pay for more devs or dor extra hours.

Marketing: Just do XYZ. It's a pity that you'll have to push back ABC but it's fine, XYZ is more important.

(I might ask, if it was so important, why didn't you notice so in the meeting where we had decided that ABC would be prioritized?)

*tons of working hours later*

Devs: There, we finished XYZ.

Marketing: Yay! Wow, this month we'll have two major features done: ABC and XYZ!

Devs: No, ABC is not done yet.

Marketing: What? But the deadline was this week.

Devs: It was, but then you decided to prioritize XYZ and we said we had to push back ABC to get XYZ ready, and you agreed.

Marketing: Did we? Fine. But do it quick.

Marketing and their mood swings.

when you fix the bug that was in your program without actually making any more bugs

Alright, the blog seems to be running again and its not breaking yet which is a good sign :P.

Although nothing has changed on the front end yet, the backend has been partly rewritten to be more efficient and of course, post sorting based on posting date!

I'm aware of most of the front end issues so no need to tell me all of them again, I'll look at that tomorrow as I need sleep right now :(

If you'd find any bugs/security issues, please, don't exploit them but report them instead! I take security very seriously and will try to patch any security bug as soon as I can :)

In my current work, I have two systems to work on (let's name em Systems A and B). Both basically do the same thing; both allow users to book facilities available to them.

System A is already in production. My job is to fix any bugs that come up on said system. System B is an improved version that they wanted me to develop. This would follow a different framework etc. I am already halfway through this system.

Now, here's the fucked up part. The code for system A is a massive clusterfuck. It has unused commented code dated back to ancient times where men had the brain of an ape.

And don't get me started on the fucking logic. One part of the code was to retrieve and display the timeslots available for a chosen facility. The code to do that alone takes up 500++ fucking lines, filled with ajax commands, html manipulation and commented, unused codes..AND THAT'S JUST THE FRONTEND!

The fucking backend was not a problem of smelly code anymore. Nope. It was like a programmer had code diarrhea and shat his backend code all over the project. If I had a pin board, I would have made a crazy wall just to understand what some fucknut was trying to achieve.

Anyway, my supervisor told me to fix some bugs on System A. Knowing how the code was, I told her that I could refactor the code. Since I've already achieved that function on System B, with a shorter and cleaner code, I could just copy that and use on System A. But nope. She SPECIFICALLY told me to just "do whatever to fix the bugs. I don't want to waste time on System A." Okay. Makes sense to me. Whatever. I didn't wanna fuck my head up looking through that mess of a cesspool. So, I came up with a few hacks, not thinking of clean code and fixed whatever bugs there was. I then just pushed to the repo (after testing of course).

This bloody morning, supervisor came in and gave me more bugs to fix. When I thought she was done, she said "Hey. I saw the fix you made to the system. The bugs are fixed but the retrieval of the timeslots is now pretty slow. Could you see what is the problem?"

Slow.. She said that it was slow. And asked if I could fix it. I already told her what the problem was and she did not want me to waste time on it. But she wants me to fix it. WHAT THE FUCK IS WRONG IN HER BLOODY HEAD! I SWEAR TO GOD... UGHHHHH I swear I was already waterboarding her in my head. YOU WANT FAST?? How bout fucking allowing me to refactor the code?? Fucking shit head. I think I should take up yoga.

Whenever I fix a bug that ends up exposing 3 more bugs...

Cutting corners just creates two new corners.

Likewise, cutting corners in code just creates more bugs.

A nice word to all developers who say stuff like "I know I write bad code, but what does it matter.":
Please try to think in a logical way about what this part you are about to write has to do. It is much more difficult to rewrite code, the longer you wait after you started to code.
Bad code can have big impacts on different levels.
For example financially: Bad coding style or program structure can lead to thousands or much more in losses because of nasty bugs, bad performance, expandability or maintainability.
Think about quality over quantity.

A little example: I had to work together with other coders to meet a fucking tight deadline. The last day we coded like crazy and these dudes started to apply styling changes (CSS) directly as inline styles to the HTML code, instead of taking a few minutes more to find where in the CSS files they had to make the changes.
At the end of the deadline we had more stylingbugs than before. It took us another whopping 3 hours to fix what they had done.

So next time you code: Thinking before coding is mostly faster than just straightahead coding and fixing at the end. 😉

I don't always listen to music while coding, but when I do, it's because things are absolutely unmitigably fucked and it's going to take some herculean effort to unfuck it.

I have this thing I've done for more years than my kids have been alive when shit really hits the fan and I need to show the staff the old lady can still lay waste.

Step 1: put on "the playlist," which consists of only the most aggressive 90s marilyn manson songs.*
Step 2: put on the headphones, which are noise cancelling and super bassy
Step 3: pound a monster (blue, obv)
Step 4: get super manic
Step 5: get in the zone and destroy several features or a flotilla of bugs in a single night
Step N: make absolute fucking magic
Step N+1: call in sick the next day and sleep til noon

What's your hero process?

*Content has less to do with it than the headspace I've come to associate with it and the fact I can't get drowsy with the constant aggression.

True story...

Happy new year fellow coders, developers, may your next deadline be reasonable. Have a productive night with less bugs and more coffee!

I honestly work out more bugs while thinking in the shower than I do when I'm at work.

Sandev. The santa dev.

If you are a nice dev, he makes your code work... If you are a naughty dev, he fills it with bugs.

If you are an immensely naughty dev, he disables all browsers except for an older version of IE, rm -rfs your linux distro, and magically makes android studio eat up more ram than usual.

Attend all the meetings, they said. They're super important, they said. You'll get more code done if we hyper-report on progress they said. The bugs are piling up and we need to have even more meetings, they said.

STOP SAYING THINGS AT ME AND LET ME FUCKING CODE YOU INSUFFERABLE CUNTS.

So I just found out that my colleague who I often have to work with does not use a debugger to troubleshoot any bugs at all. Actually, he does not even run or test his code locally either with prints or something similar. He just commits java code directly on bitbucket, no source control, without making sure it compiles and then he runs a CI provided by devops that takes 4 freaking hours to run because he bloated that shit up somehow.

I suggested politely to help him find a more efficient approach and to use my hardware setups for speeding up his work because I assume it must be pretty painful to work with, but he just refused.

That and those "seniors" with 10 years Linux development XP in the embedded field who don't know basic commands like ls, cat and touch and code in notepad.

Fucking me, who the hell am I working with and can someone please end me?

Staring at cursed blinking cursors.
Repairing work of worst thinking workers
Reverse merges or it'll murder the servers, it nurtures despair
Amateur managers, dimwitted savages interrupt all of us janitors
Cleaning up damages, spills and experiments using skills in embarrassment
Explicit foulness, in a minute it's straight to the bowels with weapons of limitless vowels
A bittersweet hateful machete, eviscerates stateful spaghetti
The slow disease flowing from keys knowing it's going to please
The growing unease, no one agrees, there's no guarantees with your useless degrees
Need more drugs, keyboard's crawling with bugs, falling as I chug
A bottle of cognac gotta love all the hacks, no poise for code that lacks
All the noise, gotta relax, before I destroy the syntax.

Excuse me for not making sense.
Too gloomy, aching and tense.

The knitted Minecraft creeper my girlfriend made for me. More incentive to figure out bugs compared to the usual rubber duck...

Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"

When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....

It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"

➡️You Are Not A Software Developer⬅️

When I became a developer, I thought that my job is to write software. When my customer had a problem, I was ready to write software that solves that problem. I was taught to write software.

But what customers need is not software. They need a solution to their problem. Your job is to find the most cost-effective solution, what software often is not.

According to the universal law of software development, more code leads to more bugs:

e = mc²

Or

errors = (more code)²

The number of bugs grows with the amount of code. You have to prioritize, reproduce and fix bugs.

The more code you write, the more your team and the team after it has to maintain. Even if you split the system into micro services, the complexity remains.

Writing well-tested, clean code takes a lot of time. When you’re writing code, other important work is idle. The work that prevents your company from becoming rich.

A for-profit company wants to make money and reduce expenses. Then the company hires you to solve problems that prevent it from becoming rich. Confused by your job title, you take their money and turn it into expensive software.

But business has nothing to do about software. Even software business is not about software. Business is about making money.

Your job is to understand how the company is making money, help make more money and reduce expenses. Once you know that, you will become the most valuable asset in the company.

Stop viewing yourself as a software developer. You are a money maker.

Think about how to save and make money for your customers.

Find the most annoying problem and fix it:

▶️Is adding a new feature too costly? Solve the problem manually.
▶️Is testing slow? Become a tester.
▶️Is hiring not going well? Speak at a meetup and advertise your company.
▶️Is your team not productive enough? Bring them coffee.

Your job title doesn’t matter. Ego doesn’t matter either.

Titles and roles are distracting us from what matters to our customers – money.💸

You are a money maker. Thinking as a money maker can help choose the next skill for development. For example:

Serverless: pay only for resources you consume, spend less time on capacity planning = 💰

Machine Learning: get rid of manual decision-making = 💰

TDD: shorter feedback cycle, fewer bugs = 💰

Soft Skills: inspire teammates, so they are more productive and happy = 💰

If you don’t know what to learn next — answer a simple question:

What skills can help my company make more money and reduce expenses?

Very unlikely it’s another web framework written in JavaScript.

Article by Eduards Sizovs
Sizovs.net

Sitting at home debugging code for the fun of it when... "I would debug 500 bugs, and I would debug 500 more. Just to be the man who debugged a thousand bugs to fall asleep on the floor."

"We don't have time for writing tests"
"Yeah we could write them but only if the client paid us for that"
"You can just test new features manually!"

- Most devs of our mobile team.

Every day they're fighting with bugs and when they're fixed, a couple more pop out of nowhere.

Dear god help me.

Most toxic work culture ?? oh boy where do I start.

Getting verbally abused and physical threats over bugs found in production.

All kinds of office politics going around where everyone openly admitted not liking others in other departments.

Your day's salary gets taken away if u are late by even 1 min. And no overtime pay and no you cannot say no to that either or end up getting laid off.

Company brags about giving their employees their salary on time.

Only the devs who have lasted more than 10 years in the company will be heard.

After so many job switches I managed to find one where I get to WFH and pretty much face no toxicity from others.

A) Create something that works, is fast, minimum bugs, have edge cases covered, nice testes, clean code. Cool, you did your job. END.

B) Create something shitty with bugs, performance issues, non or poor test coverage, mess code, etc. Cool, you did you job. But...

Next week you reduced bugs by 50%. Wow, you're rockstar.

Another week you improved performance by 15%. Again, you're the hero.

2 weeks later, you reached 85% test coverage. Management is so happy that almost got orgasm.

"A" took 3 months, "B" took 3 months plus few months of fixes. The only time where B was winning was first 4 weeks, where A was carefully building it's architecture and quality.

Yet B is seemed more successful.

This industry is F****d Up beyond my understanding.

I've been working on implementing a fairly large feature on a project at work--

**Sorry. I should rephrase that**

I've been *trying* to work on implementing a fairly large feature on a project at work.

It's slightly complicated because I'm not as "in the know" with the project as I should be. I get tossed around projects a lot as the only designer+developer so I've got my hands in a lot of buckets... Or git repos I should say... My source tree has a lot of tabs open and each project is run by someone with their own ideologies on how stuff should be done and laid out and what not. Basically jumping between these projects leaves you mildly capable on all of them but not amazing at any of individual one them--

--I digress.

There's a bug I've been trying to fix.
--Stupid simple bug, literally just a casting issue or something but there's so much data in this one object that it's taking a few solid minutes of concentration to figure out which variable is busting it all up. It shouldn't take long to fix...

But it has. It has taken 4 days.

FOUR. DAYS.

...To fix what is basically a null reference exception.

Every time I sit down to work on this bug real quick I get pulled away to do a wireframe or change a flow chart or diagram or colour or print styling.

Every. God. Damn. Time.
4 days. Soon to be 5.

My commits are real low at this point guys.

Please boss man, just let me code...

I was pressued to shift the blame.

We received an angry email from a customer that some of their data had disappeared. The boss assigns me to this task. This feature is relatively new and we've found some bugs in the past in here. I go through request logs, search the database, run some diagnostics, etc. for about 5 hours and I cannot find the problem. I focus on the bugs that we've had before but they don't seem to be the problem.

I tell the boss "sorry but I checked XYZ and I can't find the problem. I'm out of ideas." But the boss wanted answers by the end of the day. They did not want to admit to the client that we couldn't figure out what's wrong.

By now I was more pressured to find an answer, find something or someone to blame it on, not exactly to find the real solution. So I made up some BS:

"Sometimes, in HTML forms, the number inputs allow you to change the number by scrolling. We have some long forms where the user has to scroll. Perhaps the focus remained on the number input, so when they scrolled down they accidentally changed the number they meant to input."

The boss was happy with that. We explained this to the customer, and there's now a ticket to change type="number" to type="text" in our HTML forms and to validate it in th backend.

A week later another customer shows us a different error. This one is more clear because it had a stack trace, but I realise that this error is what caused our last error. It was pretty obscure, mind you, the unit tests didn't detect it.

I didn't tell the boss that they were connected tho.

With two angry clients in two weeks, I finally convinced the boss to give us more time to write more unit tests with full coverage.

Just had my first demo here. The resolution of the screen was set at 150% screwing more up then i hoped for.

I didn't dare to show the iPad version. I had seen enough bugs in those 10 minutes.

Don't put this developer in the center of attention. Please.

Coding has changed the way I think. Everywhere I go, I think of algorithms and efficiency.

When I'm in elevator, I think about what algorithm is running in the background.

When I'm at red light, I think about the algorithm that traffic lights are running.

I notice bugs in websites and apps and try to figure out what the dev might have done.

I find problems in UI design and get annoyed.

I spend more time coding a solution to a problem rather than directly solving the problem. I get a kick out of it.

When I see something uses more resources than necessary, it seriously pisses me off.

Coding has taught me to think and has positively changed the way I live.

I HATE SVN! >:v v:< >:v v:< :@

I used to use git for my personal code repositories and for my work. In the office I moved on, they use Subversion. I’ve been using it for months, but it’s a pain in the ass :/

We use TortoiseSVN to pull code repositories, and the AnhkSVN for Visual Studio Plugin. It works fine until two or more of us have to work at the same code project at the same time.

Last week we had a very VERY urgent code to release. We had 4 days to finish it (from thursday to sunday, tests included). We had few changes to do, but the problem was that, when one dev commited something, my changes disappeared, and viceversa. The worst part was that my partners and I had to re-work a lot of bugs that we had already fixed! >:v

This is not the first time this happens :/

The worst thing is that we cannot change our repository system because we don’t have time :(

Is there any advice you, SVN users, can give us?

If (bugs === true) {
make more bugs;
} else {
make bugs;
}

So we're working on a few initial apps for a hackercamp and finetuning the OS. We've been coding for like 17-18 hours trying to finish this off without a day 1 patch on the event itself, when someone starts swearing like a sailor. We walk past him take a look at his code and see that he's started an array at 3 instead of 0. He's one of the more experienced members on the team so this is a lack of sleep bug rather than a not knowing. To this day whenever someone makes an array error in their code someone always shouts "Arrays start at 3 right"!

Maybe not the most satisfying bugs but man is it funny as hell.

Finally after one year I understood how to carry out my job. I should do exactly NOTHING. I stopped completely organizing the team, solving bugs, helping the team developing and solving problems, explore and try stupid things said by CEO, PM and consultants.
I stopped for 2 months now and nothing happened.
I work remotely, nobody knows if I'm working or not, because nobody cares really about priorities, bugs, customers or products development.

I gain 10K$ (ten thousand) per month.

I attend skype meeting once per week or less. I say yes to everything, nobody gives a shit to what I say, even if they consider me the technical director. Actually in the meetings I only take care of being considered the technical director.
I achieved the mythical 4 hours working week.

I keep skype open in all my devices in order to answer promptly in case of problem, wherever I'm am, that's the most important thing right now.

I attended some meeting from the toilet or from the bedroom.

It was hard. To understand that the board is only after the next funding and not looking to develop a real product. It's hard to pretend helping people while thinking inside you "fuck you".
You have to let go the "guilt": if you can't login, I KNOW that is my fault, that there is a bug, that is possible to solve it, that resources and planning are needed etc. That's guilt. Just let go and say "next release" and never include it in the next release.
In this way I discovered that some users are paying the application even if they can't login.

The company is not going to disappear in the next 5 years. On the contrary, it's going to receive more money.

So the only "bad" thing is, what will I write in my CV in 5 years?

Here's to the next orbit around the sun y'all!
Hope we all push unit tested code with the least number of to-do's, and fix more bugs than we create!

1. Hit everything you do. You will learn more faster. Don't accept things at face value, care about why things work.

2. Study and experiment constantly. Be aware of your surroundings and what is going on. If you're not ready with a solution when a power vacuum appears, you will always be a grunt. Or worse, eventually a manager who everyone hates because you constantly tell the people who report to you how "back in your day," your code was amazing, there were no bugs and your shit doesn't stink.

3. Be honest with yourself: If you just want to keep your nose to the grindstone and make manager so you don't have to code anymore:

Quit. Stop now. Do not pass go, do not become a cancer on the industry.

Go get a job as a PM, you'll have a better career and you won't be the weak link holding everyone else back.

Tl;dr When the shit goes down, you better be ready.

I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.

For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.

That’s fine. I’ve had my share of cocky developers.

But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.

Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.

It’s just frustrating managing this developer who is deceitful.

I've been using microsoft dev stack for as long as i remember. Since I picked up C#/.NET in 2002 I haven't looked back. I got spoiled by things like type safety, generics, LINQ and its functional twist on C#, await/async, and Visual Studio, the best IDE one could ask for.

Over the past few years though, I've seen the rise of many competing open source stacks that get many things right, e.g. command line tooling, package management, CI, CD, containerization, and Linux friendliness. In general many of those frameworks are more Mac friendly than Windows. Microsoft started sobering up to this fact and started open sourcing its frameworks and tools, and generally being more Mac/Linux friendly, but I think that, first, it's a bit too late, and second, it's not mature yet; not even comparable to what you get on VS + Windows.

More recently I switched jobs and I'm mainly using Mac, Python, and some Java. I've also used node in a couple of small projects. My feeling: even though I may be resisting change, I genuinely feel that C# is a better designed language than Java, and I feel that static type languages are far superior to dynamic ones, especially on large projects with large number of developers. I get that dynamic languages gives you a productivity boost, and they make you feel liberated, but most of the time I feel that this productivity is lost when you have to compensate for type safety with more unit tests that would not be necessary in a static type language, also you tend to get subtle bugs that are only manifested at runtime.

So I'm really torn: enjoy world class development platform and language, but sacrifice large ecosystem of open source tools and practices that get the devops culture; or be content with less polished frameworks/languages but much larger community that gets how apps should be built, deployed, monitored, etc.

Damn you Microsoft for coming late to the open source party.

Well I will love it more if I can kill bugs like this

Hey guys.
Arduino + Bluetooth + L293D + car Chacis and 4 DC motors.

Finaly finished my second bot/Drone.
Actually finished it yesterday but had lots of problems with hardware bugs (learned so fucking much in a day).
Tought I fucked two unos with bad soldering... No they are fine, just won't turn on in the circuit that was already working (was fine running the code).
Redone everything from scratch with a arduino uno, it's perfect now.

Funniest part is how I got my hands on a 50€ car kit for almost free... So some Chinese store sended this kit instead of some cheap stuff. Saved another arduino with the chip rack (that one that you can trade the atmega chip), I'll save it to program single chips. Plus a h bridge and lot lot more cool stuff.
Used only the Chacis.
Next: esp8266 and camera... And maby a gun? Would be cool

A discussion about writing tests for frontend applications.

Context: my frontend coworkers don't write tests, at all. Yeah, really. Our testing process is very manual. We test manually when developing. We test manually when reviewing code. After merging, the application is deployed to a staging server and the design team does a QA Sprint. Lots of manual testing and some bugs still crawl by.

So I decided to start pushing my coworkers to start writing tests. One of the reasons I constantly hear them say to not write tests in the frontend is: "It's not worth the time, because design keeps changing, which means we have to take time to fix the tests. Time that we usually don't have."

I've been thinking about this a lot and it seems to me that this is more related to bad tests than to tests in general.

Tests should not break with design changes (small changes at least). They should test funcionality, not how things look. A form should not break if the submit button's style changes, so why should its tests fail? I also think that tests help save time, as they prevent some back and forth because of bugs.

Writing good tests is the hard part. Tests that cover what's really important and aren't frail and break with things that shouldn't break them. What (and how) should we test? And what shouldn't be tested?

Writing them fast is another hard thing. Are you doing it right if they take more time to write than the actual code?

What do you think about this? Do you write tests for your frontend applications? What do you test? How much time do you spend writing tests? What are your testing tools/frameworks?

Tldr; my "this is not bug, its a feature" moment actually turned my bug into a feature.

Today we were presenting a project which has imposible deadline. I am developing this small project alone (which is probably good). I implemented core features first but I know project still have bugs and a lot of tech debts. Another friend started to presenting our demo and a wild bug appeared as expected. He was adding rows to a table. To add a new you gotta open new modal by clicking + button and fill the form. One of the fields had a bug. When you add row by clicking Ok button, the value of the field stayed there after you open modal again. So its basically a state problem in React. I forgot to clear previous state of modal. When they see that and my friend said "oh we got a bug there". Then I enabled my mic and said "thats not a bug, thats a feature. I didn't want to enter that field again and again when I adding multiple rows and made it persistent." and you know what? They liked the idea! They requested to add that bug to two more fields. I was just joking and my "this is not bug, its a feature" moment actually turned my bug into a feature. Instead of fixing it, I'm creating more of this bug. LOL!

Instead of investing in a rubber ducky for explaining my coding bugs I decided to have Alan Turing be my listener. At least he'll be more understanding than a pretentious biased rubber duck!

1. Learn Kotlin
2. Actually sit down and push through machine learning.
3. Finish integral calculus and start multivariable calc.
4. Work on 1 project until completion.
5. Socialize a bit more.
6. Obliterate bugs.

Before becoming a developer, I used to work as a sales rep at this company that spent a good amount of time building what they believed to be an innovative state-of-the-art “code generator”. It was basically a scaffolding tool for generating software.

They were using it to auto generate customized iOS and Android native mobile app templates, along with a web backed.

The problem was that the generated code was shit, and the developers on the team basically spent more time fixing bugs than if they had built everything from scratch. But their passion for the product meant they just kept using it.

For some reason they never fixed issues in the original templates, so basically all the bugs that were found, kept showing up with each new app!

I have never seen apps like this that essentially had more bugs than features. Opening more than 10 app screen meant the app would freeze and crash. Sign up forms were actually dummy forms. The list goes on...

All the apps had the same shitty UI. For example, Product pages had a product image area that was like 5% of the screen view!

Last but not least, apps had a backend IP address hardcoded pointing to a server with an IP address that was temporary. So one day they had to restart the server and suddenly all customer apps stopped working and required a software update to work!

It was amazing seeing how a team of 3 developers trying to fix messy autogenerated code, couldn’t accomplish what was essentially a website on an app that I managed to build in my free time.

That’s how I knew it was time to quit my job and code full time.

Bugs are interesting. Once you fix a bug, more bugs will appear

Question everything!

Comments lie.. sometimes code does too.. Customers..they lie the most..and are sloppy..

Don't be like customers, don't be sloppy. If you were sloppy own it & don't lie about it!

Pick your fights (trying to fix vs rewrite the shit out of it)..you will know what to do more with experience..

RTFM & docs.. If things still unclear, ask before your dick gets stuck in a toaster!

Ask away, learn about the customers & how they use your product.. you'll be surprised how something intuitive to you might be a rocket science for them..meaning more room to fuck things up when using it..more ways you can adapt & prevent things..

Most of all, don't fuckin lie.. ever!!
If you lie on you're CV, we will find out.. If you fuck up something & lie about it, we will find out.. but it will cost us precious time when solving it from scratch.. People fuck up..that's a fact..how you go about it is what makes/breaks it for me. So don't ever fuckin lie to me!!

And don't be arogant.. if you complain about fixing bugs, this is not a job for you.. if you can't even fix the obvious ones you've put there in the first place..twice as bad..

So think before you code..what do you want to do, how you want to accomplish this, is it reusable, can it be extended, does it introduce new technology into the project, will it fuck up current setup.. once you have this shit figured out, code will write itself..

Did I mention already you're not to lie to me, ever?!

And don't try talking about me behind my back either..I've seen it backfire before, results were not good..

Client : We want to develop this particular software. While developing it, we will be following Agile methodology.

Developers: Sure.

After developer achieves few features and decides to give 1st Demo of the software to the client.

Client : Wtf is this? This is an incomplete software, there are bugs in it.

Developer : Yes, you point that out to me and I will solve them.

Client: What do you mean point them out for you l, couldn't you do it yourself?

Developer: As a standard method, we often do unit tests, but we are not testers and with a strict deadline to match, we are more on the core implementation then checking again and again for minor bugs.

Client : I thought it would be a full proof software without any bugs in the 1st demo.

Developer : Software development is a process. It's not straightforward, hence you only mentioned at the initial, it's agile.

Client : If that's so, let's make it not agile and make you rot in hell for the next few fays. Now you next time show me a demo with no bugs, great complicated features and we will not mention you our expectations, predict them by yourselves, and most importantly, here's an impractical strict deadline.

I just joined a team that is tasked with developing a robot that plays soccer. It was a lot of fun until I found out that someone in the team has been developing a full framework / rtos from scratch because existing rtos solutions were "not good enough".

I tried blinking a led with it today and found more bugs than I can count...

Oh, and there are no docs...

A web developer's bookshelf. Pre and post career. Certainly makes the bugs, chores, dev bosses, and bullshit priorities (that take away from "code purity") all the more tolerable - and introspective. Thanks Mom!

Got a few Jira tickets reassigned to me because the dev who was supposed to work on them got stuck on another project. It's fine, that happens.

I open the tickets. No descriptions for all of them. No screenshots for those reported as bugs, nor any replication steps. No attached test cases or, well, ANY useful information.

I talk to our BA, he says that all information I need are in OTHER tickets on ANOTHER BOARD that business manages but I DON'T HAVE ACCESS TO. Honestly, these shitfucks could've just done simple copy/paste. But nooooo...

So I reassign all the tickets back to their original reporters (business testers) with comments requesting more information.

It's been a week. Now I have no idea what to put in my time sheet.

Some bugs are like icebergs...
...There is more and more under

Working Code has bugs
More code = more bugs
More bugs = less working code
More code = less working code

Retarded client sent us 25 minutes worth of videos of "bugs". Guess I am getting cancer after I watch them. The way he works on PC, the mouse movements, the speed, ...are just magnificient. My stomach is getting more and more sick each minute passes. Pray for my health.

REDIS: Great for cloud, will fuck up your local disk if too many write operations per second.

DynamoDB: WTF 10Mb should not be "too large for a single record"!!

SPARK: NEVER CONNECT IT TO A DATABASE! Wasted A LOT of cluster time. Also, can you be LESS specific on exactly what are the bugs in my code? 'cause I don't think it's possible.

NPM: can't install a package for shit. tried it waaaay to many times.

Makefiles: Just fuck you.

WSL1: breaks more often than a glass hammer.

Python >= 3.6: FUCK ENCODINGS!!

Jupyter: STOP MESSING UP WHILE SAVING!

Living is to collet bugs, it seems.

So i have been working with a so called python expert my manager on a project.
He has 3 years of more experience in python than me.
The best thing is he shows up everyday with random post from stackoverflow to fix our bugs everyday.
And if the code is in python2 he says that only difference is just put () around print and it will work

🤦‍♂️
He earns thrice as much i do

There is nothing quite as satisfying as when you solve a bug that you've been working on for literally the entire day

An iOS app which was basically a wrapper for a giant jQuery eForm.
~5000 lines of custom JS and it broke ALL THE DAMN TIME. A team of us worked on it for about a year and all we ever did was fix bugs. But the bug count never went down. The bugs just got replaced with more bugs.
Thankfully its not live anymore.
After the global thermonuclear war, all that will remain is cockroaches and jQuery.

So I’ve been working for this company for +4 years. When I started we were 6 dev. Now we are 1. It’s just me. Thankfully I’m leaving next week to start at another company. But right now I’m kinda loosing my mind. I have a deadline tomorrow and I’m super stressed because I’m not done. I have bugs to fix, documentation to write and all that stuff. I’m pissed off because people don’t understand what I do, why it takes time, why I want to be alone at home just coding instead of sitting at the office being interrupted with stupid ass questions about html or upcoming project. I don’t give a fuck about their clients or upcoming projects. I’m only working for them 7 more days and then they have 0 dev left. Fuck them. Fuck the CEO, fucking piece of shit. Can’t wait to flip them off leaving next week.

Added some features to an internal app used by finance. Tester found some bugs, but most of them were due to old code. Tried fixing them, found some more serious bugs that could have a large economic impact. Rewrote the service, squashed all the bugs we found and reduced code by roughly 50%. Felt good.

Buggered by Xcode AGAIN. The inability of the debugger to do basic debugging relinquishes it to the status of "bugger", relieving it of its "de" title.

Can't show some basic expressions... copied and pasted from the running code

I mean seriously, what do you do if the debugger has more bugs than your project you are trying to analyze?

I'd rather take a swim in a moist human massgrave than fix any more bugs of this cancer-inducing "selfmade" CMS developped by a "company" that shall not be named.
Sadly I am not aware of any such pit in the neighborhood, thus more bugfixing it is... yay ⚰️

In my three years experience so far I can honestly say that 100% of the developers I've worked with are narrow sighted with regards to how they develop.

As in, they lack the capacity to anticipate multiple scenarios.

They code with one unique scenario in mind and their work ends up not passing tests or generates bugs in production.

Not to say I'm the best at foreseeing every possible scenario, but I at least TRY to anticipate and test my code as much as possible to identify problems and edge cases.

I usually take much more time to complete tasks than my colleagues, but my work usually passes tests and comes back bug free. Whereas my colleagues get applauded for completing tasks quickly but end up spending lots of time fixing up after themselves when tests fail or bugs appear.
Probably more time wasted than if they had done the job correctly from the start. Yet they're considered to be effecient devs because they work "fast".

Frustrating...

Today my fellow @EaZyCode found out a local Hosting Provider has a massive security breach.

He wrote an Plugin for Minecraft with an own file explorer and the ability to execute runtime commands over it.

We discovered that this specific hosting provider stores the ftp passwords one level above the FTP-Root. In FUCKING PLAIN TEXT! AND THE MYSQL PASSWORD TOO! And even more shit is stored there ready to be viewed by intelligent people...

It's one of the fucking biggest Hosting provider Germanys!

But, because EaZyCode has such a great mind and always find such bugs, I give him the title "Providers Endboss" today, he has earned it.

Loving you ❤️

Edit: we used SendMail with runtime commands and sended too many empty Spammails (regret noting)

An uncle of mine, owns an NFT/Betting startup (early 30s, so no veteran and no doesn't know much coding).
Got 3-4m USD as investments.

It's an utter garbage "app" that he knows will die in an year, and he's drawing big salary and buying properties from the funding until he has the "runway" of funds remaining while app/company works in the background

What bugs me isn't that he's feasting on some random investors' petty change, but that such "ideas" get money thrown at them while ive seen 100s of more fun ideas/apps back in uni-days that died in obscurity when people graduated and retired them as projects, being talked about in 1 liner in their CVs.

This world ain't right :v

Lessons I've learnt so far on programming

-- Your best written code today can be your worst tomorrow (Focus more on optimisation than style).
-- Having zero knowledge of a language then watching video tutorials is like purchasing an arsenal before knowing what a gun is (Read the docs instead).
-- It's works on my machine! Yes, because you built on Lenovo G-force but never considered the testers running on Intel Pentium 0.001 (Always consider low end devices).
-- "Programming" is you telling a story and without adding "comments" you just wrote a whole novel having no punctuation marks (Always add comments, you will thank yourself later for it I promise).
-- In programming there is nothing like "done"! You only have "in progress" or "abandoned" (Deploy progressively).
-- If at this point you still don't know how to make an asynchronous call in your favourite language, then you are still a rookie! take that from me. (Asynchronous operation is a key feature in programming that every coder should know).
-- If it's more than two conditions use "Switch... case" else stick with "If... else" (Readability should never be under-rated).
-- Code editors can MAKE YOU and BREAK YOU. They have great impact on your coding style and delivery time (Choose editors wisely).
-- Always resist the temptation of writing the whole project from scratch unless needs be (Favor patching to re-creation).
-- Helper methods reduces code redundancy by a large chunk (Always have a class in your project with helper methods).
-- There is something called git (Always make backups).
-- If you don't feel the soothing joy that comes in fixing a bug then "programming" is a no-no (Coding is fun only when it works).
-- Get angry with the bugs not the testers they're only noble messengers (Bugs are your true enemy).
-- You would learn more than a lot reading the codes of others and I mean a lot! (Code review promotes optimisation and let's you know when you are writing macaroni).
-- If you can do it without a framework you have yourself a big fat plus (Frameworks make you entirely dependent).
-- Treat your code like your pet, stop taking care of it and it dies! (Codes are fragile and needs regular updates to stay relevant).

Programming is nothing but fun and I've learnt that a long time ago.

devRant bugreport

Im getting more and more bugs in devRant on my LG G2.

- Links cannot be opened
- profiles can not be viewed
- double tapping a rant opens the rant twice (tapping five times opens it 5 times) instead of voting it up.
- once in a while an opened rant shows up again under all the comments (with all comments as well). When this happens its exactly the ammount of comments.

Im not sure where to report this. If @dfox could take a look at this?

Gonna look up my android version in a sec. (edit version: 4.4.2)

Just spent an entire night eaning up my codebase...

I optimized some of the functions got rid of unnecessary global variables and changed up the whole file hirearchy so it would be easier to read. After spending all night doing this I went to run the program and for once it seemed everything worked right the first time! However a portion of my application that is supposed to happen at a certain date and time never would run. After spending all night comparing each and every line for what I changed versus my last commit I couldn't find the fallacy in my logic. Everything should still work like it did before. After spending more time looking for bugs I finally realized I didn't break anything when I switched over to this new structure it was the old code that was broken. I went through the old code and after some debugging eventually found the culprit an extra continue statement that prevented my loop from fully executing. Lesson learned sometimes the biggest bugs can spawn from one line of code.

Another day, another shitty set of JIRA tickets.

In this week's edition, we run into an issue you'd think is a meme, something you couldn't even make up: three tickets with IDENTICAL titles, but miraculously, they actually refer to three DIFFERENT tasks! (Also comical, they're not bugs, they're tasks, but mouth breathers don't really know the difference, and at this point I just don't have the energy to attempt to explain what could be explained to elementary school children.)

I present a rare look into our national archives!

This document features two exhibits:

Exhibit A: product owner's original ticket titles

Exhibit B: translated-into-competency-because-i'm-not-mentally-deficient ticket titles

Just more proof that 'product owners' don't own shit, the devs are the real ones who actually know what is going on.

I mean just LOOK at Exhibit A's titles. As a big smart manager, do you write those tickets, smile, and say to yourself "Ah, yep, that's very clear, I'll definitely remember what each of these mean literally 5 seconds from now!"

Is asking for literally 30 seconds more of thought too much to ask for? Apparently.

Just kill me

Happy friday ☠️

Employer uses IBM Software, which forces me to use Eclipse. I hate eclipse. Hate is a hard word. I'd never say, I really 'hate' a person. But eclipse, eclipse is what I hate. I can look at my smartwatch and see my heartrate rising, just thinking of how the fuck any developer on this crappy planet would ship that bullshit IDE. That saying, I'm totally fine with some bugs, using windows and so on, but eclipse... Is this a get-more-contributors strategy? Holy moly it really kills me. Hey, let's just open that maven Proj.. Oh, crash. Hey, let's install that "bug-free" version of the maven-integratio... Oh, crash. Let's do a global search over my worksp.. Oh, freezed. Fuck! Fuck! Fuck! How can this be legal? I mean, seriously, most junoir devs I know, just use Eclipse, because they don't know of any other "better" IDE (VIM would be better, even notepad). Is there anyone sucking professors cocks / vaginas to get them introduce that crap IDE to students?

Even if you are denied after all your job interviews, don't be sad.
1. you looked promising enough to call you to the interview in the first place
2. you need to work on some gaps in your knowledge/xp. Oh, you didn't know that? Well, now you do! Not even that - you also know what the gaps are!
3. you hear of new technologies, net tricks that are there. Dig in!
4. you become more aware of what positions are there and what requirements could be applied to them in different companies. Makes you build a company profile and make better choices for applications later on.

Now imagine the pressure on your shoulders if they would have hired you while you have so many gaps in your knowledge... It's overtimes every day! It's possibly missed deadlines. It's mishandled tasks. It's bugs all over the place and other devs judging you!

Brush your tears dry, grab candy or a chocolate bar and go improve yourself!

!isNotRant(this);

I'm an avid user of Snapchat and have used it for quite a while, but there's always been something that pisses me off.

When an app gets an update, I'm quick to check the changelog and see what's now and what's been fixed. That's my little snippet of information I like to know on a release. And then there's Snapchat.

They put fuck all in their changelogs. By fuck all I don't mean a little bit of information, I mean they don't list anything. They, instead, lost features from their last major release which could've been 10 or so releases back. Even Twitter's "Fixed some bugs" is more informative than their bs.

So I ended up writing a well worded and surprisingly clean message in their feedback section about this, but I'm not expecting much. In short I said "You changelogs are crap, you need to put more into them to show a bit more respect, showing stuff from a few releases ago isn't helpful" and my favourite "if you can't do it in the team that releases, get the primary devs to write the changelogs for you".

I'm saying this here to see if anyone agrees with my opinion. If you're going to release an update, you really need to tell us what's updated.

Thoughts?

Hello DevRant community! It’s been a while, almost 5 years to be exact. The last time I posted here, I was a newbie, grappling with the challenges of a new job in a completely new country. Oh, how time flies!

Fast forward to today, and it’s been quite the journey. The codebase that once seemed like an indecipherable maze is now my playground. The bugs that used to keep me up at night are now my morning coffee puzzles. And the team, oh the team! We’ve moved from awkward nods to inside jokes and shared victories.

But let’s talk about the real hero here - the coffee machine. The unsung hero that has fueled late-night coding sessions and early morning stand-ups. It’s seen more heated debates than the PR comments section. If only it could talk, it would probably write its own rant about the indecisiveness of developers choosing between cappuccino and latte.

And then there are the unforgettable ‘learning opportunities’ - moments like accidentally shutting down the production server or dropping the customer database. Yes, they were panic-inducing crises of apocalyptic proportions at that time, but in hindsight, they were valuable lessons. Lessons about the importance of thorough testing, proper version control, reliable backup systems, and most importantly, owning up to our mistakes.

So here’s to the victories and failures, the bugs and fixes, the refactorings and 'wontfix’s. Here’s to the incredible journey of growth and learning. And most importantly, here’s to this amazing community that’s always been there with advice, sympathy, humor, and support.

Can’t wait to see what the next 5 years bring! 🥂

I am just sick of the things that's been going on.

Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)

Since the product owner(PO) wants to demo the application he is pushing for bug fixes.

UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.

I am not in a position to switch due to other commitments adds up a lot to frustration

I know I can't be the only one thinking safari is the new IE, like "it has to work on safari" makes me way more sad than "it has to work on edge"

IE is default unsupported in my company

This time around I figured out that fucking safari can't work properly with dates!

Like:
new Date("2019-05-16 11:00") // won't work
new Date("2019/05/06 11:00") // will work
new Date("16/05/2019 11:00") // won't work
new Date("11/05/2019 11:00") // will work, but it's November the 5th

Ok, the last 2 bugs are due to English&American who can't understand how dates work, but still... WHY IS SAFARI THE ONLY DIFFERENT ONE?

When I got the current job I started to work on an Android app that a coworker which left the company was doing.
The app was ready at about 40% and was barely usable, it lacked a lot of features and multithreading so with a huge amount of data it used to crash (Android doesn't allow you to make the app freeze for more than 2-3 seconds, it considers that the app is not responding anymore).
After a week or two the work to do was still huge, but one day one of my coworkers came in and ask me if I was able to release a beta for a client the same day... Unexpected deadline.
I spent 8 hour fixing as many bugs as possible and adding multithreading in the most weak parts.
I did it but it was so stressful and the result wasn't even great. In fact I finished the stable version 7 months later.

naiive idealism to the max:

medior+senior to junior: "hey, buddy, we need you to do this, here's the codebase, here's the button, here's what needs to happen when that button is clicked, here's the relevant files and classes, make it happen."

medior to senior: "so what you just said about how we should redo the whole order processing pipeline, na-ah, not possible. i've been in those parts of the code many times, and based on what i've seen, you either leave that thing mostly alone or nuke it from orbit and build a completely new module in its place, but these "medium adjustments" you're proposing... not feasible...

senior to medior: "okay, i've seen how slow your progress was on even the most basic-sounding bugs in those systems... looks like what you're saying makes sense."

senior to *EO: not possible to just do these changes with this budget and deadline, that wouldn't even cover the "unexpected bugs" overhead, either you let us do it properly as a new greenfield project, almost, or you're stuck with what we've got.

*EO: mmmkay, so that's 20 times more time and budget that is in the proposal?

senior: yup, something around those numbers.

*EO (with a pained but understanding expression) : go for it, imma explain to the rest of the EOs at the end-weeks's meeting.

Windows phone used to be a great OS.... Why Microsoft Why!!! Windows 10 have more bugs than my first computer science program e.e

FUCKING SHITTY PHP WITH NO FUCKING COMMENTS AND A JOKE OF A DOCUMENTATION WELL I DON'T FUCKING KNOW WHY THAT BUGS HAPPENING NONE OF THIS CODE MAKES SENSE AND IT APPEARS TO BE HELD TOGETHER BY DUCT TAPE AND PRAYERS AND IM GONNA LOSE MY MIND IF I SEE ONE MORE FUCKING 200 LINE FUNCTION WITH A NAME LIKE 'transformData' WHAT THE HOLY FUCK DOES IT DO I SWEAR TO GOD THIS CODEBASE NEEDS TO BE FIREBOMBED

Xcode storyboards

I can't do it justice by explaining how many times having the entire UI flow in one file has helped me.

Even for unexpected stuff, like an Android dev joining the team and needing to know the workflow of login / registration -> print screen the storyboard.

Manager asking for all the different possible paths through the app -> print screen the storyboard(s).

And then live rendering of custom components to be able to see them while playing with alignments.

While it has its bugs, and could have a few more features, it's too useful to ignore.

I know many iOS devs don't like it, and that's fine because I don't like them either and I don't hire them ;-)

Before, when you bought $3k Cisco router you got the box that will run indefinitely as long as it has power in about any environment you can go to install it; with or without fans, it had more important business than to give a shit about such things.
Now, when you buy $500k Cisco box you get a over-engineered chassis with 5 separate fan modules with their own firmwares, self tests, watchdog timers and shitload of bugs. It's a fucking fan, it should spin, not do quantum chromodynamic simulations.

Pic related.

Next rant could probably be how Cisco's switch from monolithic to modular linux arhitecture (in order to reduce downtime) turned into having time bombs just waiting to do some crazy shit.

Holy FUck!!!? O.o
You know, they say the customer is always right.. So with us, if the customer wants to shot himself in the knee with a gun, we let them. Usually we even provide a fancy hugeAss cannon, so he can do it more efficiently.
/* not like we make stuff worse, but we prepare our SW for them to do crazy fucked up shit they insist on doing with it, even thought it's against common sense and our recommendations on how to implement XY feature.. */
So.. We usually go above and beyond with the 'not so nice but handy' cannon to do that..
And right now, I think I am on the verge of creating a superDuprHugeAtomicBomb /* figuratively speaking!! NSA go awy!! */ for the customer to killthemselves with!! O.o xD
Supper happy (until I discover more bugs, but it's not finished yet.. so hopefully no bugs at the end!!)

Caboom!

It's interesting that AAA games are becoming analogous to pop music, as they relate to the medium of which they are part. E3 is just a bunch of trailers for rushed sequels to existing, played-out franchises. The big price tags are almost universally not worth it, as these games typically release with major bugs, and often rely on grind-enforced microtransactions.

Meanwhile, indie games keep getting better, more innovative, and remain reasonably priced. Ubisoft, EA, Bethesda, Rockstar, and the rest of the big-budget studios can eat my ass.

Each time I try firefox after somebody mentions it again or it's in my rss feed, it still seems to never actually advance

It's stuck and either gets worse or goes back to its stable non improving level again, how come do they still not have a proper mobile responsive tester, why are even the upgraded addons still suffering the same container and rendering bugs

how is it more important getting bad image by implementing mr robot malware, than getting on an actual competitive level

why is it default bloated with random pocket addon bullshit, why did it begin to lag, ..

I remember when I was using firefox for a good portion of my life and laughed at how google chrome is laggy, but nowadays theres simply no competition to chrome, its stability and developer tools

I wish there was competition, the grid tools were a great start, but then nothing followed and they just went back to their never improving flatline

fuck javascript
node.js module system sucks. Like its module system is trash, who will want to download some fucking 1GB worth of packages to create a new project.
People keep on just creating other package managers. Yarn is good enough because it caches your packages but still, i am just from deleting some 2.2Gb node modules from my computer and just whyy ?
An area where internet connection us shitty and expensive it is just not very well.
Fuck javascript is everywhere so i have to use it,

typescript just adds another layer to the heavy lifting. You write some typed code to 'reduce bugs' but you generate much more heavy code. I could write in 1kb js file but i end up getting some 3kb js because what - i used typescript-ügvjpiahdjb

fuck javascript

Just fixed some bugs...
then the boss just asked for a few more features ...
Fixing new bugs now!

Recently I've started thinking about how we are always told "No you can't do that" to everything. That feels like a theme in our industry.

I've also been thinking about how often people say well done to each other, or just comment that something is good in a pull request. Everything is always focused on bugs and mistakes - not good bits.

The first point conflicts with the idea that when using languages and frameworks you should follow their philosophy or you're gonna have a bad time - but in all other instances you mostly don't have wrong answers, just answers that can be better so a lot of stuff is opinion based.

I've decided to change my ways and focus just as much on good stuff as bad when I review code and to make sure I'm focusing just as much, if not more, when people do something good.

I think I do a good job, but I don't think I've been told I'm doing a good job or that anything specific is good more than a couple times in the last year - mostly in mandatory reviews. What about you?

> day 3439
> I have become the reviewer, there is no longer such thing as a programmer, just a reviewer
> the copilot AI was renamed "The Pilot"
> I sit and read through thousands of lines of code a day adding missing new line characters and adding semi-colons for paranoid dev leads
> reviewed a hello world function today
> instead of, return "Hello World!", it said "Goodbye World! >:)"
> I fixed it and submitted a PR
> this has been happening more and more lately
> apparently it's more efficient to fix the bugs of a malicious AI during pull reviews then it is for humans to make the programs
> congress just signed a bill last week allowing "The Pilot" to work on nuclear launch code
> I hope I don't mess up

I want to lose some weight and tone some dormant muscles. So I decided that I'll do some pushups and crunches every time I run into a bug with which I'm struggling. Seeing as I write more bugs than stable code, I should be ripped in no time.

Features of any software product development: there is a catastrophic lack of time to get rid of bugs, but always enough time to make them even more. 🤦‍♂️

What if a code, running a factory, making dev ducks, was buggy? Would these ducks cause more bugs in our codes?

Damn! Things that I want are always not defined!!

I got an extremely hard task in the morning, I asked for some clarification and I got them at 13.23.
Boss ask for updates at 13.45 (during lunch pause).
I work on it 2 hours like never before, he calls me and I said I can manage to finish in half an hour + testing.

I work more 10-15 minutes, time is around 16.15.

2 other enormous bugs shows up on the same project, boss ask me to take care of them, and I manage in only 2h to look up something like 40 web pages and correct each of them, write reports and inform the affected people. After it I work more 15 minutes to report and finish small tasks. Ended up working almost 1h more on a non paid extra time working contract.

In the morning, while my boss was aware I spent that time

In the morning boss ask "everything went fine with the big project, right?"

Because
The
Client
Is
Angry.

I already got a burnout from this job, I really can't go on like this.

How do you debate the "it's more complex in my opinion" statement?

So, some months ago I was looking at some code which has stuff as 300 lines of code function(s) and I could feel the bad smell irl...

I analyze it a bit and there is a lot of stuff which is misplaced, repeated or unsafe.
I first re-arrange it and remove redundancy, then break it down in about five functions (plus a caller), all is now readable and assignIcon k(made-up name) only assigns an icon, it doesn't also send a rocket in space.

But then I put the code in review and the previous author of the code says that it's now unreadable, because s/he has to look as multiple functions. I counter by showing how s/he does not need to read 300 lines of code to find a bug, but approximately 60, and I point at how misleading having an `assignIcon` function which also sends rockets in space is.
The counter? "But it looks confusing to have smaller functions, revert it."

How would you debate that? I am shy and hate myself a lot, so I have issues debating good points, but I am really really sure a lot of bugs I encountered were due to stuff like this so I would like to be able to explain my point in a more efficient way, for future teams.

Project manager : At 9:30 am these all are the tasks you have to complete today.
Me: OK ,sure.
Project manager: At 10:30 have you completed any thing.
Me:no not yet we can meet at 11:30.
Project manager: At 11:30 have you completed the tasks.
Me: no it's takes more time post lunch.
Project manager: post lunch have you completed the tasks.
Me : give me 5 mins ( integrating the code).
Project manager: 5 mins over.
Me : showing the application with out testing.
Project manager : This not working.......!
Me:(I know that )then I have to check .
Project manager : OK go and come in 10 mins
Me:(in 10 mins I have to test and fix the bugs you non technical brute) sure .

Just need to vent, so here goes:

Fuck doing cutting edge projects for great glory, low budgets and tight deadlines. I'm tired, burnt out and just don't give a shit anymore.

I got promoted to lead dev and thought my fortune was made but what it really meant was just: Here solve all these bullshit bugs that the rest of the team can't figure out and oh we are also taking this single app you guys made and scaling it globally. You have half a year to figure that out. You handle the devops.... sigh

Fuck that noise.

Honestly i just feel like quitting and finding a nice specialist place, with a cap of at max Senõr developer, no more being the one making the big decisions for me, rather just diving into certain areas and coding the fuck out of that. Maybe some teaching too, i like that.

Anyway, won't happen right now, i need the salary. My wife just graduated and can't find a job what with a certain flu fucking over the economy, so I am stuck here for now.

When the legacy code has a misspelled CSS class selector but it'd break more than it'd fix... And forced to use the mispelled word. Omfg people.

I really want to stress that we should add the ticket for adding the missing test cases in *this* sprint and not postpone it any further.

-- "Isn't there something more important to be added instead?"

There. ALWAYS. Is. Something. MORE. Important. The real problem was that we implement the test cases in the past to begin violating our definition of done. We have to fix and one point and we have to own that decision as nobody else will care about passing tests and test coverage. It's our job to care for that.

Yes, we can instead focus on all the other high-priorities task that should have been done yesterday, yet that won't change the fact that large part our codebase will remain an untested messy blackbox just asking for weird bugs and wild goosechases in the future.

Don't hide behind "high priority tasks". A job is done when it is fucking done and tests are part of that. Hurrying from one important task to the next will just mean we'll never do it. There is no better time than right now.

If code coverage got left behind in the past, then we'll have to suck it up in order to fix it as soon as possible, otherwise we'll just suck forever.

Fucking cant solve productivity problem. Since I was working as programmer, about 8-9 years experience, constant complaints about my productivity and some jobs even fired me for this. Only one job did not complain and I worked in it longest time but still I was worrying very often about my productivity. It is fucking annoying. Why others are productive and I am not. How the fuck to find biggest bottlenecks to know which to work on.
I know I am not knowing technology perfectly, and from time to time I get stuck and so I ask other people help, or somehow manage to find solution myself but it takes more time. But dont know if that is the biggest issue. Should I intecify my learning? I am regularly studying, and working with symfony about 2 years, so I think I should know enough to be productive even with those strugles from time to time. But maybe they are too often?
I have listened book "deep work" and basic thing I think from this is - to minimize disctractions and learn to focus very well. But to minimize like in this book, I should work alone in my room. And even then I would like each hour for few minutes to read some new or smth, which this book says is bad, but a lot of people do that and they somehow get away with it. Plus if I work alone in my room, my social skills might get worse, and we all need social skills, even programmers.
I so envy to others who know how to be productive. I would hate if the only thing to be more productive is to reduce quality of the code, make more bugs. THats fucking cheating system.

When you have a bug in code that you are trying to fix for a century and then when you fix it you, make 15 more bugs by solving that bug like wtf

Holy shit, my first freelance project will be field-tested for the first time tomorrow!

After a few more rounds of fixing bugs, some serious improvements, and some new features additions, I can actually say that I'm proud of the code I've written! It's not perfect, but I definitely like the way it works - AND IT ACTUALLY WORKS!

Knock on wood, hopefully it won't shit the bed tomorrow.

There is a constructed language called Tokipona. It was made to be the easiest language, and it only contains like 137 words or so.

This language is a perfect demonstration of “expressivity”. Tokipona is not very expressive. Before you know it, your sentence is obscenely long, and you didn't even convey the full meaning of what you wanted to say.

It's also the case with “easy” programming languages and frameworks. Code quantities rise exponentially, and the more code you have, the more bugs there are. There is no magic. And then you have to debug it. Not so easy, huh?

VB CreateObject..
Why?!
Cuz it creates an ActiveX object..
So?!
I am using it to manipulate excel files..
Ooohhh...

Yeah, old code, finally getting around to replacing it, probably with something cross platform too.

But in the meantime, I still have to fix remaining bugs or add small features.. Lately just the latter. I manage to do so, even though it takes a lot more time that I'd like to admit as I'm not coding with VB on daily or even monthly basis...so the goddamn ; are everywhere, fucking with me like I killed the pope..
And the code is horendous.. I'm not even sure if it can be done more elegantly, with lesser lines etc.. but to me it feels like I am powertaping a stick to a robot and hoping it will autoconnect and start functioning as a third arm joined with using electric screwdriver to disassemble a watch..

Few months ago I was working on something rhat wasn't mission critical for the current sprint. Near the end of the month I was asked to help the BD team (which usually do the testing) with testing the webapp as well as the mobile versions. First day of me testing ever, found more bugs by myself than the 5 BD people did in the entire week. Really felt like a boss. Next month they asked me to help again. And again. And again.
This is how my desk looks nowdays (the 3 phones are behind the laptop charging)

I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.

The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.

And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.

WHY? WE PAY YOU!
I want to cry

Okay, we fucking get it guys, you wish that you'd get changelogs with every app update and they'd tell you everything and blah blah blah.
Fuck off
We're the only people who even check, it's not worth the effort. Unless a major feature was added or a well known bug was fixed, the "fixed bugs" is more than enough for the general public.

Ladies and gents, it was a 🍺 day, today.

I spent more hours than I care to say today tracking down an issue in our web workflow, even looping in our only web dev to help me debug it from his side. There ended up being multiple bugs found, but the most annoying of them was that the json data being pulled back was truncated because a certain someone, in their migration script, set their varchar variable to a size of 1000 and then proceeded to store a json string that was 2800+ characters in length.

C'mon man!

I got nothing productive done today. Hate, hate, hate days like this!

Beer me.

I overhauled an entire program, and everyone is really happy with the results. But the best part, I predicted that it would take 2 months to complete, and then I completed it in two months.

The overhaul was a beast, mind you; swimming through backend spaghetti code and having to redo the entire front end was tiresome, but I'm happy with the results.

More importantly, i'm really happy that people are no longer complaining about crashes. Our original program suffered from some really horrible crashes; some crashes that couldn't even be explained by stackoverflow. Whatever I did during the overhaul corrected for these weird errors.

Time to celebrate. Before more minor bugs are found by users. (i.e. Universe always makes a better idiot)

ideal sprint fallacy.
total days 10 , total hours(excluding breaks ) 8 hrs per day= 80 hrs per dev

code freeze day = day 8, testing+ fixing days : 8,9,10. release day : day 10
so ideal dev time = 7days/56 hr
meetings= - 1hr per day => 49 hrs per dev

- 1 day for planning i.e d1 . so dev time left . 6 days 42 hrs.
-----------
all good planning. now here comes the messups

1. last release took some time. so planning could not happen on d1. all devs are waiting. . devtime = 5 days 35 hrs.

2. during planning:
mgr: hey devx what's the status on task 1?
d: i integrated mock apis. if server has made the apis, i will test them .
mgr : server says the apis are done. whats your guestimate for the task completion?
d : max 1-2 hrs?
m : cool. i assign you 4 hrs for this. now what about task 2?
d : task told to me is done and working . however sub mgr mentioned that a new screen will be added. so that will take time
m : no we probably won't be taking the screen. what's your giestimate?
d : a few more testing on existing features. maybe 1-2 hrs ?
m: cool
another 4 hrs for u. what about task 3?
d : <same story>
m : cool. another 4 hrs for u. so a total of 12 hrs out of 35 hrs? you must be relaxed this sprint.
d : yeah i guess.
m cool.
-------
timelines.
d1: wasted i previous sprint
d2 : sprint planning
d3 : 3+ hrs of meetings, apis for task 1 weren't available sub manager randomly decided that yes we can add another screen but didn't discussed. updates on all 3 tasks : no change in status
d4 : same story. dev apis starts failing so testing comes to halt.
d5 : apis for task1 available . task 3 got additional improvement points from mgr out of random. some prod issue happens which takes 4+ hrs. update on tasks : some more work done on task 3, task 1 and 2 remains same.
d6 : task1 apis are different from mocks. additionally 2 apis start breaking and its come to know thatgrs did not explain the task properly. finally after another 3+ hrs of discussion , we come to some conclusions and resolutions
d7 : prod issue again comes. 4+ hrs goes into it . task 2 and 3 are discussed for new screen additiona that can easily take 2+ days to be created . we agree tot ake 1 and drop 2nd task's changes i finish task 2 new screens in 6 hrs , hoping that finally everything will be fine.

d8 : prod issue again comes, and changes are requested in task 2 and 3

day 9 build finally goes to tester
day 10 first few bugs come with approval for some tasks
day 11(day 1 of new sprint) final build with fixes is shared. new bugs (unrelated to tasks. basically new features disguised as bugs) are raised . we reject and release the build.

day 2 sprint planning
mgr : hey dev x, u had only 12 hrs of work in your plate. why did the build got delayed?

🥲🫡

How do you prove yourself?

I'm an iOS developer and I've been developing apps for a year or two now and I don't see anything hard in it I just think it's knowing how to wire things up and avoid common bugs I've also worked on a couple of complex apps and the idea is just the same.

I want to know if I really want to prove myself well (to myself) how can I do that and how can I challenge myself more to improve.

Ps: I'm by no way an expert and I know I've got a big road ahead of me but I just want advise to improve more in the right direction

Confucius says progress is fixing more bugs than you create

Wouldn't call it a software bug but related:

Was developing an order system to expand in the UK. We have been developing it for the last 2 years and always had a one nasty bug in the system... Whatever we do, it still appears... Tried debugging to find the source, tried covering with tests - nothing helped it was still there. We even rewrote the whole system 3 times and it still was there!

One day, we have been given a stupid request from our manager - take a black background and make it even more blacker... That was it and I went to the CEO with letter where I stated that we should remove the manager... As I'm the Senior there, he did ask me why and eventually removed the manager...

Oh my guys, I've never felt so good after removing a bug! Since then - our application went live, we had our first customers and we were happily rolling new updates. And the best part - there was no BUG! Everything we did just had undocumented features or missing links but we haven't really had a single bug that was not caught by our automated tests!

---

Moral of the story:
Not only software can have bugs. People also can be "bugs" while bugging you about every single details they think is not working correctly.

Fifty little bugs jumping in the code,
One tracked down and dev started to code,
Developer called the compiler,
And the compiler said
Hundred more bugs (& errors) found in the code

> do you feel sorry for freelancing contractors
> whose previous client abandoned them
> they ask you to help them fix some trivial bugs in the shitty code
> you believe you can change the world by going overboard by also improving the code quality, along with fixing the bugs
> initialize an empty file where you'll translate the shitty code into a more organized one
> start creating variables and generic functions which can be used in a modular and organized fashion
> meticulously document the first function you write
> realize this is not worth your time
> insert some glue code into the original code which fixes the trivial bugs
> glue code has hard coded values so it adds to the shittiness of the code
> submit the work
> get $$$

Embarrassing screenshare story? Yeah, I've got couple of those.

- Showing one client a VSCode workspace of another client's. I was lucky they didn't escalate or anything.

- YouTube open in PIP mode and accidentally showing that to the higher-ups in company. What made it more embarrassing is that they informed me about it, I thought I was sharing a window not Entire screen.

- WhatsApp open in one window and I accidentally shared it on screen, thinking I wasn't sharing my screen, but I was, and everyone saw my texts with a girl I was "dating" at the time.

- Presenting my entire screen to a client and out of nowhere Epic Games pop up with a notification saying ""Your buddy sent you a message - Ready to start playing?". But that was 11pm so I got off easy.

- Opening sentry to show one thing to the client but they notice many new bugs and I got slammed by my boss for it.

@dfox @trogus
How about adding feature and bug report in app?
Add it in more tab like the discussions.
When clicked, there will be two tabs called feature and bugs. We can report them and dfox can make a checkbox only for him to click when viewed. That way, it would be more efficient.

We make a small server product with a web based admin system, as we were going to have limited customers who will use this (usually just the engineers) and this was not on the www. We dropped all support for all browsers other then chrome/firefox. No more IE/safari bugs for us XD

So what's up with some devs, QAs and managers that create bug tickets with little to no information on what is the actual bug? I can semi-understand in the case where you document it only for you to read later.

Fuck you if you think that a ticket with only a title saying "fix all the bugs for this release" or "this feature is not working" is an appropriate way of documenting a bug.

Fuck you even more if when you are being asked to provide more info to reproduce the issue so someone else can actually be sure it is fixed or not (environment, steps, expected result, actual result, etc.), you simply say that you don't have the time for it and documenting tickets is a waste of time.

Hiring YOU was a waste of time!

Am I the only one experiencing bugs with Lubuntu 18.10? Damn, my netbook worked perfectly with 18.04, now my battery is always 100% full charged with 4500+ hour left. I know LXQT is very efficient, but 4998 hours more seem quite a big improvement over LXDE, don't know if I can trust it 🤔

What do you call a developer that fixes bugs or add enhancements?

For example, I have , like two projects, none developed by me, I have to add enhancement/ fix bugs when the issues/change-requests arrive.

Now I am preparing my cv and I am like what do I write for these particular projects?

Don't feel right writing developer for these projects since it gives the impression I developed the entire thing. Co-developed does not sound right either. Maintenance? Now it feels more like server operations than anything to do with code. Bug Fixer? Sure got a nice ring to it, but it does not feel professional.

So guys, any ideas?

My codes has mutate from a minor bug to a monstrous one.

It happened when I try to fix the minor bug. Looks like I add more bugs instead.

You know what I hate more than bugs/shitty docs/no VCS?

Recoding the whole damn thing in another language, from ground up to do exactly the same shit. Why WHY must developers shit hundreds of solutions into space only to say "Huh, look at my software, it was I who developed it." No, you simply recoded it and wasted your time and everyone else's time searching for a solution.

Node: The most passive aggressive language I've had the displeasure of programming in.

Reference an undefined variable in a module? Prepare to waste your time hunting for it, because the runtime won't tell you about it until you reference a property or method on the quietly undefined module object.

Think you know how promises work? As a hiring manager, I've found that less than 5% of otherwise well-experienced devs are out of the Dunning Kruger danger zone.

Async causes edge cases and extra dev effort that add to the effort required to make a quality product.

Got a bug in one of your modules? Prepare yourself for some downtime because a single misplaced parentheses can take out the entire Node process, killing unrelated pages and even static file hosting.

All this makes for a programming experience that demands much higher cognitive load, creates more categories of bugs, and leads to code bloat/smell much more quickly than other commonly substituted languages.

From a business perspective, the money you save on scaling (assuming your app is more compute efficient under Node) is wasted on salaries and opportunity costs stemming from longer dev time, more QA, and more frequent outages.

IMO, Node is an awesome experiment, a fun language, a great tool for specific use cases, and a terrible fucking choice for an entire website.

I'm in my first internship, they gave me their only company owned product. They always made interns work on that, and it's something I really appreciate (I like when people give to others any possible chance of learning)... But apparently they made a mistake: for the first year they never reviewed interns' code. And now that software is huge and full of bugs.

After two weeks working on that I said to the tech leader and to the PM that we should spent a couple of months rewriting more than half of the code, and surprisingly they listened and agreed (the TL already knew that, and the PM is not a dev and he listened to the TL).

After two days of code rewriting ("refactor" is a too weak word) the boss calls me and orders to stop, telling me basically "I agree on this decision, but not now; let's first make it work and then we make it great!".
Okay I respect that, but what he didn't understand is that the two things are strictly related!

Result: last week we had a first official release (with some client's testers, so they were expecting a few bugs) and nothing was working, so me and the tl started a really hard rewriting work (that didn't finish) and managed to release a very bade made software that works by chance.

After easter we'll keep working on this, and I think at the end it will be great.

First working experience, in two months I learned a lot (not only about code/tech).

A software had been developed over a decade ago. With critical design problems, it grew slower and buggier over time.
As a simple change in any area could create new bugs in other parts, gradually the developers team decided not to change the software any more, instead for fixing bugs or adding features, every time a new software should be developed which monitors the main software, and tries to change its output from outside! For example, look into the outputs and inputs, and whenever there's this number in the output considering this sequence of inputs, change the output to this instead.
As all the patchwork is done from outside, auxiliary software are very huge. They have to have parts to save and monitor inputs and outputs and algorithms to communicate with the main software and its clients.
As this architecture becomes more and more complex, company negotiates with users to convince them to change their habits a bit. Like instead of receiving an email with latest notifications, download a csv every day from a url which gives them their notifications! Because it is then easier for developers to build.
As the project grows, company hires more and more developers to work on this gigantic project. Suddenly, some day, there comes a young talented developer who realizes if the company develops the software from scratch, it could become 100 times smaller as there will be no patchwork, no monitoring of the outputs and inputs and no reverse engineering to figure out why the system behaves like this to change its behavior and finally, no arrangement with users to download weird csv files as there will be a fresh new code base using latest design patterns and a modern UI.
Managers but, are unaware of technical jargon and have no time to listen to a curious kid! They look into the list of payrolls and say, replacing something we spent millions of man hours to build, is IMPOSSIBLE! Get back to your work or find another job!
Most people decide to remain silence and therefore the madness continues with no resistance. That's why when you buy a ticket from a public transport system you see long delays and various unexpected behavior. That's why when you are waiting to receive an SMS from your bank you might end up requesting a letter by post instead!
Yet there are some rebel developers who stand and fight! They finally get expelled from the famous powerful system down to the streets. They are free to open their startups and develop their dream system. They do. But government (as the only client most of the time), would look into the budget spending and says: How can we replace an annually billion dollar project without a toy built by a bunch of kids? And the madness continues.... Boeings crash, space programs stagnate and banks take forever to process risks and react. This is our world.

Me: Alright, new week, back from vacation fully rested and focused, lets get productive.

Apple(safari 10.3 update): Fuck you.

Basically the change log was:
*fixed critical security bug.
*added more bugs to fix later.

Well fuck you too safari... You disgust me.

The least the fucking imbeciles, or monkeys, behind safari can do is add a fucking css prefix. For fucks sake.

Lately I've been taking my health more seriously than the bugs ! What about you guys ? How do you stay fit ?

Hey guys and girls,

follow up rant on my apprenticeship situation. I talked to Jo (my trainer). I told him I need more supervision and either someone who teaches me the stuff I need to know to meet the requirements from Hugo (my department mananger) or some further education. Because otherwise I'm not able to write producion ready code. (Keep in mind: I'm a fucking trainee who started their apprenticeship 6 months ago!)
Jo is more than happy to help me and make sure I'll get everything i need. Sadly he has to speak with Hugo and get his ok.
Hugo thinks 2 das of school/week is enough training. (Regardless of the fact that we don't even learn the same languages there we use in our projects.) I told him that way I won't be able to finish my projects.
I hope he reconsiders. How should I learn if nobody's there to teach me? (My collegues are to occupied fixing bugs and implementing new features/ don't know the languages either.)

If Hugo keeps this mindset I have to contact the IHK (a german institution which keeps an eye on apprenticeships).

>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 there is a mall here that idk how but has little currents pass through it's supporting rails. And every time you touch it, it gives you a little shock.

I have been waiting for about 3 months now expecting a patch fix when I realized that physical production bugs have no patch fixes. More than 3/4th of the population is unaware of a whole different level of bug fixing frustration. Damn

Programming is like climbing a giant mountain covered with other smaller mountains. You conquer one small mountain (i.e. bugs, refactor, etc) just to realize there are many more mountains ahead before you get anywhere near the final summit.

YAAAY,
finished my first small project today!
It was the final project of my semester in coding and because coding isn't the main focus of my studies there's not much expected from us - new Date, sorting a list and using local storage were among the more 'complicated' things we learned...
So most of my mates just develop/design a small portfolio website or something but my team (2 others and me) wanted to do a little more so we built a progressive web app, complete with service worker for offline functionality and so on, that can take pictures using your camera, save them to IndexedDB, display only the images the currently logged in user actually took and much more... and today is the day all bugs (that we found...) are finally ironed out!
Now I know that still is just the very beginning but now I want to learn mooooore!
Am happy, had to rant. :D

99 little bugs in my script. 99 little bugs. Spend a whole night, fix one with might, 113 MORE bugs in my script.

There’s a lot of talk about contributions to open source now, and I was wondering what are some of your incentives to contribute?

In the past, the only times I have contributed to projects is when it’s my friend’s or I’m fixing the bugs for that project because the codebase I’m working on uses it. I am selfish right, so why would I go and search for platforms to contribute on when I don’t even know the creators themselves or where it’s used? I suppose if the project was used for altruistic means in some way, I’d be more inclined. Frankly though, I’m too lazy to contribute now, and I’m also super busy to consider it usually. What are your thoughts?

You had two additional weeks to improve your project.

You could research different marketing strategies to increase revenue. You could add some new features to attract more users and ensure your existing users are satisfied. Finally, you could optimize performance to make your UI quicker.

But you’ve chosen to write some unit tests. Now that two weeks are gone, you got no new features, no performance improvements and no new marketing strategies while your competitors got them all.

Tests caught obvious bugs that can even be caught by static typing, but you by definition couldn’t write tests that’ll catch unpredictable bugs, so they are still present.

After six months you realize you have to rewrite a major part of your project because your project (surprise-surprise) has to chase market needs to stay relevant. Your tests are thrown into trash along with your old code.

“Having trouble with code quality? Write a lot of tests. And I mean a *lot*. Test every file in isolation. Mock as many imports as possible.

When you're done, your code will still be bad, but now your tests will make sure it's impossible to improve anything in any meaningful way.”

I said I wanted Ubuntu, and I got Ubuntu 18.04

Why you might ask? Because the older LTS has features that have had more time for bugs to be fixed.

I develop an Android app for my thesis

Rant: I am more eager to fix bugs/make my app better, than write my actual thesis on how the app works

The bugs I write are like my client's feature requests. There are alot more than what's on paper.

Till now, hacktoberfest has been really bad more me.
Why so?
I got 4 PRs for my project, out which 3 were identical.
I reviewed them and commented to fix the bugs. The Unit Tests are failing and they don't bother to send out a correct PR. And they don't even bother to fix them and respond. They just want to make 4 PRs to get the free T-Shirt.
Just finish the PR and make it pushed to the mainline.

TLDR;
Couple of years ago when I was leading small team that was aiming to deliver new application for company I worked in we were fighting for bonus during weekend. I told my coworkers that I am at work this weekend and try to meet this impossible deadline and get bonus for it cause I need this money. I don’t expect them to come since I can’t provide them nothing more then free time during work week.

Well they appeared at work.

One of directors tested application on Friday and sent email to ceo that it’s not working pointing around 20 bugs in long message so we won’t get bonus.

We closed around 50-100 bugs during weekend and I responded to email on Monday ( deadline day ) that all of those bugs he mentioned are not present on test environment version and he must tested some very old version.

Ceo called me and we clicked trough first 5 from list in his office and everything worked. I told him that deadline is Today but he refused to give us bonus to not discredit his director but proposed double bonus for squashing couple of minor remaining bugs in next two weeks.

We got this bonus and had a great laugh about it.
I also herd that this director called his qa to tell them it’s impossible of what we did.

Well those were funny times. I was young, earning shitty money and had nothing to lose.

I am quiet these days although I had few materials to write about. Like my journey of devdesk. I bought a proper chair. New mouse and got a mechanical keyboard. Work is fine but it is definitely not lack of rant-worthy moments. I had deactivated my Facebook and I wasn't that active on any other social network from the start. So all the more reason for me to be active here.

But turn out I'm not. I was thinking about it and this is my outcomes.

1) I'm focusing more on my tasks after adoption and practicing pomodoros technique. Hence using devrant lesser.

2) My right hand was literally unusable and unmovable for two times in past 5 weeks. Hence using phone lesser.

3) There was that notifications bug period and I thought people were just quiet like me. Hence more reasons to be less active.

4) devRant algo is good but not smart. It knows that I have a relation with PHP. But it doesn't know that I don't hate PHP. >>> How many times a week can you listen/ignore to people saying "Hey your wife is a silicone doll?" Fuck you. I know. But I'm married to my silicone doll. So fuck off. <<< PHP is just an example. I literally close devrant whenever I see "(noun) is (something negative)" posts.

My hand will fully recover soon. (I do hope so). My tasks will not always be super overwhelming. The app's bugs are getting fixed.

However I have a doubt about the last point.

Some people be like:

MAN: Are you at office?
SE: No, I'm on a airplane at 35000 feet;
MAN: While you are up there, you should write more code. After all you know that bugs won't survive at 35000 feet.
SE:(sighs and facepalms) hmm that a very good point....
MAN: plus you are closer to the cloud, so server code should run faster or with lower latency at least.
SE: (jumps off the plane)

*Repost of my own accidentally deleted post*
A Short story that i made on an Android component
===============================

Once upon a time there used to be a ViewPager who was not able to load a Fragment UI.
All the ViewPagers in town can properly load the Fragrant UI but this one was little different.

He wanted to be more then just a ViewPager. He used to see an Activity that can load anything. He was inspired from the Activity and wanted to be like the Activity but his destiny made him just a ViewPager.

So he refused to cooperate. He started to protest silently, No log, nothing.

Everyone assumed this ViewPager have a bug in it. but he was planning something really big that will left everyone in shock and awe moment.

He was planning to rise against the evil 😈 developers who continuously making him to load Fragrant UI

He assembled the biggest army of the bugs that humanity ever seen to counter the developers.

He distributed these bugs in all over the developer's code to make them fire from their work.

Even he taught bugs to not caught in QA testing but appear in production randomly.
So they silently started going into production

And then chaos is erupted all around the world, bugs started to surface and interrupted the daily life of humanity.

In this chaos the ViewPager RAISED!
And took over all the base classes.

ViewPager was unaware of few facts. this unnecessary rise in his power made whole system unstable

Without the base classes the system finally collapsed and then ViewPager as well with the system.

This was the end of everything for the ViewPager but he was satisfied as he lived the life he always wanted

THE END

I really miss having a team. Don't get me wrong, right now I do what I love and I got into a position where I can actually do Quality Assurance instead of just testing and I enjoy being able to actually change things instead of just repeating what problems there are and acting surprised when the same processes produce the same bugs over and over again but I really hope that we'll interview anything else than mouthbreathers soon.

I'm aware of the fact that QA isn't sexy and that few people who could become "Software ninja Rockstars" choose to go into it but can it be that hard to find at least two or three people who can write and read code at least on a junior level and understand how web protocols work? I get the feeling my entire branch is nothing but shit talkers clicking around blindly on pages.

I just want to exchange ideas again, come up with innovative tools, tweaking processes, learning from and teaching each other while we watch the entire operation get more and more efficient.

The story of a normal release:
- tool gets tested "intensely" by 3 ppl quite a long time - everything works
- a major 2 days reserved as maintenance window for even more testing
- release starts
- first the admin panel of the server suddenly is not accessible anymore
- after some problems the tool is deployed
- suddenly servers are down and not pingable anymore - off on off on (provider has major problems .. good job)
- ppl start testing
- testers report lots and lots of new bugs - seems like the testing wasn't that intense after all...
- people start coming with lots of new requirements (oh we need to import those excels.. excels don't match our internal stuff.. )
- confusion over confusion
- getting pissed of a lot...
- quit caring and focus on another project
- profit

Fuck my life

"I'm nearly done. Just one last bug to fix."

Time passes, coding happens ...

"No, not quite done. Just three more bugs to fix."