YES!~

[SunnyD]

It's kind of an epic feeling when you realize that you just cleaned up multiple other peoples' code, plugged about 30 or 40 various memory leaks that were causing a rather large customer to be rather irate, test and validate that those fixes worked and also happened to have fixed a few "mysterious" bugs that were plaguing the software in the process as well.

Yes, there is an I as well as a me in team, since this is MY product now, bitches!

/blog

PS - Yes, I miss

 

[Tweak155]

It's kind of an epic feeling when you realize that you just cleaned up multiple other peoples' code, plugged about 30 or 40 various memory leaks that were causing a rather large customer to be rather irate, test and validate that those fixes worked and also happened to have fixed a few "mysterious" bugs that were plaguing the software in the process as well.

Yes, there is an I as well as a me in team, since this is MY product now, bitches!

/blog

PS - Yes, I miss

Sometimes you can fix a lot of that with one root function that is re-used. That also feels epic. Everyone is so impressed but it was just a simple fix

 

[Vdubchaos]

I'm pretty sure your company owns just about anything you create...in some cases EVEN if it's on your own time.

 

[SunnyD]

Sometimes you can fix a lot of that with one root function that is re-used. That also feels epic. Everyone is so impressed but it was just a simple fix

In my case, most of the offending fixes were actually ridiculous things. The one showstopper (the mysterious bug) was an uninitialized pointer that was (rightfully) never getting allocated but always getting deleted. /duh Ironically, that wasn't even the issue I was trying to resolve.

I'm pretty sure your company owns just about anything you create...in some cases EVEN if it's on your own time.

I see you've mastered literary figurative speech...

 

[techs]

I took a really satisfying dump this morning.

 

[Thebobo]

I took a really satisfying dump this morning.

yea but you cant go back and look at it? can you?

 

[SunnyD]

yea but you cant go back and look at it? can you?

Depends... he might be THAT GUY.

 

[vshah]

i just finished up similar work that led to a 10x performance improvement in a basic, often used function in our app. feelsgoodman

 

[highland145]

Cookie left?

 

[Rhezuss]

,8,1?

 

[Jeff7]

Enjoy it while you can. :twisted:


From this day forward, anything that is ever found to be wrong with it is entirely your fault.



But yes, it is good to be able to fix something, especially something that's been a troublesome problem for a long time.

At work, we've got a simple sheetmetal part that gets screwed into an assembly. The process for the longest time had been to put it into place, drill through existing holes in the assembly and into the sheetmetal part, take the sheetmetal part out, remove all the metal shavings produced, and then put the sheetmetal back in and drive in the screws.

Someone finally asked why we did it that way, since the sheetmetal part is cut out by laser before it's formed. I think it was something like this:
"...I guess because that's how we've always done it. Can we get them lasered out instead?"

"Well....yes, actually, we can."


So I updated the design, produced a proper model and drawing set, got a few test pieces made make sure the holes lined up as expected, and put it out to production. I'm told that it was a decent morale boost to not have to deal with that whole process - now the sheetmetal part goes in, and the screw is driven in. Done. (Yes, and it is more efficient, so more $$$ for everyone.)

That was nice to do.

 

[Phoenix86]

At work, we've got a simple sheetmetal part that gets screwed into an assembly. The process for the longest time had been to put it into place, drill through existing holes in the assembly and into the sheetmetal part, take the sheetmetal part out, remove all the metal shavings produced, and then put the sheetmetal back in and drive in the screws.

Someone finally asked why we did it that way, since the sheetmetal part is cut out by laser before it's formed. I think it was something like this:
"...I guess because that's how we've always done it. Can we get them lasered out instead?"

"Well....yes, actually, we can."


So I updated the design, produced a proper model and drawing set, got a few test pieces made make sure the holes lined up as expected, and put it out to production. I'm told that it was a decent morale boost to not have to deal with that whole process - now the sheetmetal part goes in, and the screw is driven in. Done. (Yes, and it is more efficient, so more $$$ for everyone.)

That was nice to do.

Nice until the guy who did the drilling gets fired because he's not needed.

I have improved processes in a team which came close to tripling their output, 6 months later the team went from 15 employees to 8.

 

[Nintendesert]

It's kind of an epic feeling when you realize that you just cleaned up multiple other peoples' code, plugged about 30 or 40 various memory leaks that were causing a rather large customer to be rather irate, test and validate that those fixes worked and also happened to have fixed a few "mysterious" bugs that were plaguing the software in the process as well.

Yes, there is an I as well as a me in team, since this is MY product now, bitches!

/blog

PS - Yes, I miss

I don't see any cooking in this post.

 

[brianmanahan]

In my case, most of the offending fixes were actually ridiculous things. The one showstopper (the mysterious bug) was an uninitialized pointer that was (rightfully) never getting allocated but always getting deleted. /duh Ironically, that wasn't even the issue I was trying to resolve.

this is why you use memory managed languages with automatic garbage collection, lol

 

[zinfamous]

It's kind of an epic feeling when you realize that you just cleaned up multiple other peoples' code, plugged about 30 or 40 various memory leaks that were causing a rather large customer to be rather irate, test and validate that those fixes worked and also happened to have fixed a few "mysterious" bugs that were plaguing the software in the process as well.

Yes, there is an I as well as a me in team, since this is MY product now, bitches!

/blog

PS - Yes, I miss

Exactly how large is this customer?

300, 400 lbs?

:hmm:

 

[olds]

It's kind of an epic feeling when you realize that you just cleaned up multiple other peoples' code, plugged about 30 or 40 various memory leaks that were causing a rather large customer to be rather irate, test and validate that those fixes worked and also happened to have fixed a few "mysterious" bugs that were plaguing the software in the process as well.

Yes, there is an I as well as a me in team, since this is MY product now, bitches!

/blog

PS - Yes, I miss

LTS

 

[lxskllr]

Nice until the guy who did the drilling gets fired because he's not needed.

I really liked José :^(

 

[SunnyD]

this is why you use memory managed languages with automatic garbage collection, lol

The code base predates most managed languages.

Exactly how large is this customer?

300, 400 lbs?

:hmm:

Obese. Morbidly obese. And yet the population at large continues to throw them wads of dollars whether they like it or not (either willingly or via tax dollars).

 

[Jeff7]

Nice until the guy who did the drilling gets fired because he's not needed.

I have improved processes in a team which came close to tripling their output, 6 months later the team went from 15 employees to 8.

I will say that that is never my objective - I'd of course prefer to have that person now be able to spend more time doing other things that need doing, particularly more profitable things, and there's more than enough work to go around. (There aren't a lot of people there who have just one job, except perhaps for some people in the office.) Though even then, you might have someone who prefers the job duties they've got, so they might not like to be assigned to install Pop rivets, after doing drilling for a few years.

I guess the trick is to do the changes gradually, so that people can acclimate, and so that management can (hopefully...but not likely:\) find suitable new tasks to make use of the available labor hours.
But, everyone's always focused on short-term goals, ignoring the long-term. Experience doesn't show up directly in balance books, so it is often seen as devoid of value. Not everywhere, but this is the case far too often.

 

[brianmanahan]

I have improved processes in a team which came close to tripling their output, 6 months later the team went from 15 employees to 8.

same thing here. wrote an app that turned a completely manual process into a %90 automated one. the people who we wrote it for were ecstatic at first because it made their job so much easier... but obviously too easy because %75 of them got canned

managers were happy though, and this leads to good bonuses :awe:

 

[brianmanahan]

Though even then, you might have someone who prefers the job duties they've got, so they might not like to be assigned to install Pop rivets, after doing drilling for a few years.

that would be the most boring job in the universe

funny thing is, my job is so stressful that about most of the time i would rather have a job like that

 

[lxskllr]

same thing here. wrote an app that turned a completely manual process into a %90 automated one. the people who we wrote it for were ecstatic at first because it made their job so much easier... but obviously too easy because %75 of them got canned

managers were happy though, and this leads to good bonuses :awe:

The benefactors of the app blew it by working too fast. You need to find creative ways to slow production so a 50% increase is only 15%. Everyone still looks good, but not good enough to get canned.

 

[Gillbot]

and yet you post instead of working more? lazy.....

 

[Jeff7]

that would be the most boring job in the universe

funny thing is, my job is so stressful that about most of the time i would rather have a job like that

Boring, yes. But for some people, they're just glad to have a steady job where they know what to expect, every day, and have come to prefer it.

I know that I had a much easier time sleeping back when I worked at Walmart. I didn't have anything on my mind for the next day. "Gee, I wonder if I'll be pulling pallets and then putting things on shelves again tomorrow? Hmm....."
Not a whole lot to think about there. At all. Ever.

Now, far from Walmart, the problems at work are more complex, more layered, and more unpredictable, so my mind never wants to simply shut up when it's time to sleep.

Always good and bad to everything.

 

[lxskllr]

Boring, yes. But for some people, they're just glad to have a steady job where they know what to expect, every day, and have come to prefer it.

I know that I had a much easier time sleeping back when I worked at Walmart. I didn't have anything on my mind for the next day. "Gee, I wonder if I'll be pulling pallets and then putting things on shelves again tomorrow? Hmm....."
Not a whole lot to think about there. At all. Ever.

Now, far from Walmart, the problems at work are more complex, more layered, and more unpredictable, so my mind never wants to simply shut up when it's time to sleep.

Always good and bad to everything.

I've done both, and I'm not sure what I prefer. I think I'd like a low impact thinking job, where I got to use my brain, but it isn't a tragedy if I fuck something up. Nothing like jerking awake when you've just about gone to sleep, wondering exactly what it was you did that that day, and if you did it right :^(