A rare bug appeared. It was my duty to finish it.

SH = Manager

SH: So when do you think you can finish the task?
Me: I still have to analyze the problem. Give me a moment and I'll get back to you.
SH: Alright.

*An hour later*

SH: *Approaches my desk* Have you found the source of the problem?
Me: Not yet. Please give me some more time.
SH: Ok.

*An hour later*

SH: *the approach* You found it yet?
Me: Yes, I've found the the source of the problem, But... *explains the problem and thus concluding that it's a complicated bug*
SH: Can you finish it by tomorrow?
Me: I'll do the best I can but I am not entirely sure if I can finish it by tomorrow.
SH: OK great!

*The next day*

SH: *Le approach* Hey I have a colleague here that may be able to solve the problem, he has skills with XYZ. Ok, I will leave you two at it then. *the leave*
Helper: So can you tell me about the issue here?
Me: *explains the bug and the source of the problem*
Helper: Have you tried solution A?
Me: Yes sir, but it yields a different output... *explains what happened with solution A*
Helper: Well, that won't work. What about solution B?
Me: I've tried that, too. *Another lengthy explanation*
Helper: Welp, ok. I'll get back to you on that.

(...But he never came.)

*A few hours later*

SH: *A.P.P.R.O.A.C.H.* Hey I have this team lead from another department. I think he can help you out on this one. *L.E.A.V.E.*
Helper 2: What seems to be the problem?
Me: *Explains again with all the solutions I tried but failed*
Helper 2: Wow. That really seems to be a complicated problem.
~~
Me (In my head): -_-
~~
Helper 2: Listen, I need to get back to my team. I'll keep you posted if I happen to find a solution for your problem alright?
Me: Alright thanks.

*Towards the end of the day*

SH: *APPROACHHHH* Have you resolved the bug yet?
~~
Me (In my head): You made me spend half the FUCKING day explaining to these people who didn't even give a piece of FUCKING SHIT to contribute to the problem and you are asking me if I am done with this FUCKING BUG? FUCK YOU, YOU SON OF A -
~~
Me: No, it is not finished yet..
SH: You have to finish this because we don't have tomorrow.
~~
Me (In my head): SHDIFHWISGSIFGSISBAUDBEIQBDIWGFIEBWIDHWIQBDOSBCISBDOSHDIAGSUSVDIFBDKDJWIQKDBDIDGSUWVDIABDIXBSIDBDIDBWUWGUSVDUWVDJQBDUDVWISHDUWVFG
~~

I went home for the day.

All the possible help is good to find a bug...

Bugfixing on production.

Is this a skill? Should I put it in my CV?

Devs : Lets pick library X, it is well know piece of open source technology, actively maintained by community for over 10 years.
Architect : NAH, it is an overkill to use it in our project , lets build our own solution.
*2 Months later*
The code base is hundreds of thousands lines of code, we basically started to look at library X on GitHub to copy features or get inspiration from that code. In that time we delivered 0 business value, it is horrible to use it and we constantly adding something or bugfixing because no one thought about something in first place.

1) bugfixing
2) bugfixing
3) bugfixing

No, seriously, I love finding & fixing bugs.. it never gets old..frustrating at times yes, but it is never boring..

Waking up with a nice solution for a problem you have struggled with for hours... More sleep for developers!

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 ⚰️

Do you ever feel like you developed a sixth sense for hunting the source of bugs on your or other people's code?

If got to do some bugfixing at work today.
Looking through code:

if (x !== undefined || x !== null){

I want the person who wrote this to wear the ugliest and scratchiest christmas sweater with "i write bad code" written on it

Bugfixing is like whack-a-mole... For every one you squash, 3 more pop up.

Programming, suck on my covfefe

bugfixing quiz:
What is wrong in that Java code:
I would say that happens when developers frequently switch between Java and JavaScript

var _self = Object.create(Rant);

Hello devs I'm back

A few months ago I joined a software development company and I was pretty specific that I wasn't going to do support or maintenance only feature development, well, this past 3 months I've been doing dev helping stablish good practices and a better architecture for the app, but guess who is joining a support team tomorrow, they sold me the idea of a refactor team, I was trilled and accepted, now they tell me it's a legacy bug fixing team, damn I hate this crap, hope y'all doing better

Debugging in real life

Our family is working on the house. We have an integrated floor heating system, which is connected individually for each room. (we have three rooms, only two are connected yet)

Today we changed the main water boiler. At first it seemed like it was working, but then we lost pressure. It dropped fairly fast so we checked every sink, every water outlet.

We just missed the unconnected floor heating pipe, that was connected to the main pipe...

Its a fucking mess down here, so dont complain about you bugs, I have experienced worse!!!

dear fucking client, why are you giving me only the "???" as an answer to my well written documentation and explanation about the latest bugfixing.
WHY? What could I possibly get out of this shitty answer? #fml

One day a week should be for improving the quality of the code, not just bugfixing and rushed implementation of new features.

Last year i had to resolve a really annoying bug, and figuring out how to fix that was a HUGE PAIN IN THE ASS.
Now i have to make some adjustment to that fix, and the only comment on that piece of code is: "this is a huge mess, good luck if you need to modify something".

FUCK YOU MYSELF FROM THE PAST

If i always would say what i think during programming or Bug fixing some code, i probably get fired and moved to a anti Aggression Therapy

Had to fix all bugs of my colleague this night because our client was not happy.
Before he joined us he worked as a database admin and now he wants to learn web dev and coding. But he did so bad mistakes like endless loops or requesting api 5 times.
In so tired now, happy when its christmas

Bugfixing is the art of unfixing bugs while eliminate other bugs

!rant

Today I finally found a randomly appearing bug that prevented our nightly backup on our production servers! Finally!
Now I can go to sleep in peace.

Pixel perfect layout bugfixing doesn't even feel like development, it only proves that some people got their priorities terribly wrong if they worry about a 2 pixel margin anywhere. And I do say this as a front end dev who does respect a respect a good design. But still, pixel pushing sucks!

Bugfixing makes me insanely annoyed and moody tbh

Finished the weekend with 2 really productive debugging and bugfixing evenings and nights. It always is impressing me how productive I am at weekend nights. I literally found all major bugs of an software we developed and I also fixed them. It feels so good and powerfull. Looking forward to customers positive feedback

I'm 22 years old and 1.5 years into my first Startup Job. (and second Dev job)
I feel kind of uncomfortable now and I would like to ask your opinions.
I'll start with the work related description of my situation and later add a bit of my life situation.

I develop as hobby since I can think. I'm pretty engaged and love to do things right. So I quickly found myself in the position of the de-facto lead fullstack Developer.
Although, to be clear, were only a few devs - which are now replaced by not so many other devs. I feel often like the only person able to design and decide and implement in a way that won't kill us later (and I spend half of my time fixing technical debt).

I mostly like what I do , because it's a challenge and I feel needed. I learn new things and I am pretty flexible in work time. (but I also often work till late in the night, sacrificing friendship time)
But there are so many things I would love to do and used to do, but now I have no motivation to develop outside of my job.
I don't really feel that what my company is doing is something I find valuable. (Image rights management)

I earn pretty well - in comparison to what I'm used to: 20€/hour, Brutto 2.800 / month for 32 hours a week. In Berlin. (Minus tax and stuff it's 1.800€). It's more than enough for what I need.
But when I see what others in similar positions earn (~4.000), I feel weird. I got promised a raise since nearly a year now. I don't feel I could demand it. I also got the hint that I could get virtual shares. But nothing happened.

Now what further complicates the situation is that I will go to Portugal in April for at least half a year, for joining a social project I love. My plan used to be that I work from there for a few hours a week - but I'm starting to hesitate as I fear that I will actually work more and it will keep me from fully being there.

So, I kind of feel emotionally attached - I like (some of) the people, I know (or at least believe) that the company will have a big problem without me. (I hold a lot of the knowledge for legacy applications) .
But I also feel like I'm putting too much of myself into the company and it is not really giving me back. And it's also not so much worth it... Or is it?

Should I stick to the company and keep my pretty secure position and be financially supported during my time in Portugal, while possibly sacrificing my time there?
Should I ask for a raise (possibly even retroactively) and then still quit later? (they will probably try to get my 1 month of cancelation period upped to 3).

Also, is this a risk for my "career"?

I fucking hating working as a subcontractor (hopefully the right term). The interesting things are always given to locals and we just do the fucking day-to-day bugfixing shit.

And due to the fact that we are not in the same city, we are suspected to cheat on the billing just because I made some presentations for the company I'm directly working for (and for which I have an internal budget)

Just go Fuck yourself. Maybe some Indians want do the boring shit (no offense to India)

Today I had to fix a bug and it took me about 2 hours to find out that it related to a bug in a component which doesn't belong to the bugs component. In development everything where fine. But after deployment the bug occured. Found out that when running Vue webpack projects in dev it handles errors different, kind of a global try catch block. After deployment the application breaks.
This teached me again that we should not ignore any red error line in console.

1 hour of bugfixing
2 hours of fighting with git
Ah, yes...

That moment when your code finally works after hours of bugfixing

So when you are fixing bugs you are like exorcist:

you: "tell me by some sign your name!"
bug: (demonic voice babbling)
you: "and the day and hour of your departure!"
you: "The hour of your departure!"
you: "The hour of your departure. CANNOTGETPROPERTYNAMEOFUNDEFINED!"

Saw code in one of my files at a WIP merge request.
Wanted to add something to fix a bug.
Added, tested and committed.
Pushed.
Wondered why my change wasn't listed in the "changes" section of the merge request.

Turned out that I accidentally edited a file that had the same piece of code where I wanted to add something.
Well, lucky me! If I wouldn't have been editing the "wrong" file accidentally, i probably would have spent hours of debugging only to find out that I am actually in the real wrong file.

How do you deal with code/project burnout?

I've been refactoring and bugfixing my script for a week now. The project seems simple on the surface but the edge cases and methods to handle certain subsets of data are breaking it because handling them is vague and takes time to figure out and every day something is fixed and something else ends up as the issue preventing completion.

On the surface the idea seems sound so I'm also under pressure to get something "this easy" done.

Starting to feel some burnout on this.

Hi there!

I've been worrying about the following problem for months now and I don't find any solution. Maybe anybody of you can lead me the way.

We are developing a software suite which consists of a number of desktop applications:

* 12 applications written in C++; all over 20 years old; further development by 5 or 6 guys (one man armys) - mainly bugfixing, changes of law implementations, small features
* 2 applications we are currently writing in C#; completely new developments of existing C++ applications; scrum teams with at least 5 guys; this is, where we put our focus in

These applications (C++ and C#) are sharing some core assemblies and are interacting with each other. So they are not independent.

We organize them in a mono repository in one huge solution, which consists currently of about 500 projects.

Advantages:

* With all projects in one solution and through project references, Visual Studio takes care of the right build order
* Code navigation is superb - every single line of code is accessible - this makes refactoring easy
* Every developer can map the branch and build the whole suite locally
* Debugging on the local machine is easy
* DevOps pipeline is straight forward - it just have to build a single solution

Disadvantages:

* The huge solution is extremely slow.
* If you want to build the solution or you want to debug (which does essentially the same as a pre step) Visual Studio is building a lot of projects, although they haven't been changed. Their detection is buggy. So sometimes you wait 2 minutes until it starts the app. That slows us down a lot.
* Full builds need about an hour, because its building the same projects (even if they haven't been changed) over and over again (with ready made nuget packages this could be improved a lot I think)
* If a core team member changes some core apis, he is changing the calling code too, although he doesn't know the calling code, because another team has written it. I don't think, that's best practice and it doesn't scale.
* Often, a C# developer has to mess around with C++ building problems, because the C++ projects are in the same solution
* It gets more and more confusing and frustrating, because there is no clear organizational seperation between apps and nobody can't just focus on his app alone.

Idea:

I was thinking about putting the whole framework and core projects in a new solution (around 100 projects). Then we could take all old C++ projects and put them also in a new solution (around 200 projects). This would leave the newer projects (new applications - C#) in the existing solution.

This should speed up things, and would be a first step to better seperation, BUT:

How should the integration process look like?

Scenario: Core team is changing an API in our framework

Current process: Because all projects are in the same solution, they change the calling code too. So it's immediately integrated and the app developers just have to do "get latest".

New process (?): Core team is providing the changes through a nuget package (new version). So does every developer now has to keep track of if there is a new package version and if yes, do the integration? And how can we coordinate the different teams, so they are upgrading all at the same time? Because we ship our applications as a suite, all apps has to use the same versions. Or should we automate the integration process? Is there a best practice?

I have to add, that our core team is making changes very frequently, so the integration process will have to happen often.

Any ideas/feedback/inspiration?

Thank you so much in advance!

I had to write a js bpmn flow designer for a huge bpmn app on request and my crazy brain said fuck it I can do it in 2 months, let's just say I made my deadline with school and all. And it actually worked very well it needed only a bit of bugfixing when it hit QA.

I have a changed a project that has many many many bugs because of outdated code that kept it from working. In the process, I changed the structure of some feature implementations in order to get the application to work again. Can this be considered refactoring, or is it just a special kind of bugfixing?

Also, can I call something a rewrite even though I'm not actually writing anything, just using a GUI environment to create the same functionality again?

I need this because I'm writing about what I'm doing for my university and I can't find it on google - I guess it's opinion based.

Typical monday... the new funcionality I have to implement on frontend requires additional changes on backend (out of my reach). So I wait. And in the meantime I switch to bugfixing and suddenly some tester changes the data in the scenario (a very specific one) I was working on.

Aaaaand another sprint full of bugfixing legacy code.

What music do you like to listen while writing tests, implementing feature, bugfixing, refactoring, coding, scripting?

Nobody ever tells me i’m not good enough. They always say: Maybe you should talk to X, or maybe you should ask Y. Well both of X and Y are either too busy, not in the office at all and ofcourse just as incompetent as myself, so they give a short excuse instead of being helping in a pro active way.

Also 3D transform has it’s limitations and can’t actually twist a 2D form in a “organic way”. Now i’ll focus on things that do matter like the header thats decided to change colour on a smaller screen.

Bugfixing 101

When it comes to work, I wouldn't say that I get low motivation. In every single job that I have been in I have seen some terrible coding, or when I review my previous stuff I find it was also terrible. Always wanting to improve/refactor stuff is always a motivation as it'll in turn make me a better programmer. Also I hold that belief that you have to do the shit out of your job since you can be replaced!