Waking up to a mess
-
Here as well. Our cat here likes chewing on the potted palm fronds and then creating mixed media art expressions on the carpet...
-
I hate this. Whether or not I start work right away, I really don't like waking up to a code mess - a project that doesn't build or that I'm in the middle of debugging, etc. I do everything I can to avoid it, but sometimes it happens anyway. Right now I'm facing some indomitable bugs on multiple fronts, multiple projects. In fact, I don't even have a path forward I can make progress on, but for fixing those bugs. And they are confusing. I've been attacking each of them for days, in the past. I put them down and stepped away for quite awhile too. That's a tough spot to be in. But the worst part of all of it is waking up to it. Every day that I do that, I have to be very careful to keep my mood up and not spoil my morning and thus my day, because if I'm not I'll think about it and fret over it even if I'm not actively working on it. The only real out is some sort of mentally immersive activity or meditation that allows me to lose it, but that relief is more temporary than the bugs, so I just try to keep myself occupied until the worst of it passes. Meh. I'm guessing I'm not the only one who has run into this. I get the feeling nobody likes broken builds and hanging debugging sessions - especially say, coming into them on a Monday morning (for those of you that do the M-F thing)
Real programmers use butterflies
Yes it's a very frustrating situation. My salvation is having a side project that I can work on and actually make some progress on. Most of the time đź¤
-
I hate this. Whether or not I start work right away, I really don't like waking up to a code mess - a project that doesn't build or that I'm in the middle of debugging, etc. I do everything I can to avoid it, but sometimes it happens anyway. Right now I'm facing some indomitable bugs on multiple fronts, multiple projects. In fact, I don't even have a path forward I can make progress on, but for fixing those bugs. And they are confusing. I've been attacking each of them for days, in the past. I put them down and stepped away for quite awhile too. That's a tough spot to be in. But the worst part of all of it is waking up to it. Every day that I do that, I have to be very careful to keep my mood up and not spoil my morning and thus my day, because if I'm not I'll think about it and fret over it even if I'm not actively working on it. The only real out is some sort of mentally immersive activity or meditation that allows me to lose it, but that relief is more temporary than the bugs, so I just try to keep myself occupied until the worst of it passes. Meh. I'm guessing I'm not the only one who has run into this. I get the feeling nobody likes broken builds and hanging debugging sessions - especially say, coming into them on a Monday morning (for those of you that do the M-F thing)
Real programmers use butterflies
I keep running notes and leave myself comment markers in the code for where I'm having trouble. It helps. Asana is a good app too - you can make tasks and sub tasks and more and more subtasks, leave notes everywhere (so be careful not to lose them), and organize them by tags and into projects. You can view your tasks in many ways. I like it for personal work as well as team work, but I still keep a notepad open on my desktop called current or running notes. Sometimes just cleaning up and adding comments throughout helps with debugging and is a bit of a break without being an actual break. Best of luck!
-
I hate this. Whether or not I start work right away, I really don't like waking up to a code mess - a project that doesn't build or that I'm in the middle of debugging, etc. I do everything I can to avoid it, but sometimes it happens anyway. Right now I'm facing some indomitable bugs on multiple fronts, multiple projects. In fact, I don't even have a path forward I can make progress on, but for fixing those bugs. And they are confusing. I've been attacking each of them for days, in the past. I put them down and stepped away for quite awhile too. That's a tough spot to be in. But the worst part of all of it is waking up to it. Every day that I do that, I have to be very careful to keep my mood up and not spoil my morning and thus my day, because if I'm not I'll think about it and fret over it even if I'm not actively working on it. The only real out is some sort of mentally immersive activity or meditation that allows me to lose it, but that relief is more temporary than the bugs, so I just try to keep myself occupied until the worst of it passes. Meh. I'm guessing I'm not the only one who has run into this. I get the feeling nobody likes broken builds and hanging debugging sessions - especially say, coming into them on a Monday morning (for those of you that do the M-F thing)
Real programmers use butterflies
Well I hope you have a lot of "ah-HA!" moments soon! It sounds like you need some. Cheers!
-
I keep running notes and leave myself comment markers in the code for where I'm having trouble. It helps. Asana is a good app too - you can make tasks and sub tasks and more and more subtasks, leave notes everywhere (so be careful not to lose them), and organize them by tags and into projects. You can view your tasks in many ways. I like it for personal work as well as team work, but I still keep a notepad open on my desktop called current or running notes. Sometimes just cleaning up and adding comments throughout helps with debugging and is a bit of a break without being an actual break. Best of luck!
-
I hate this. Whether or not I start work right away, I really don't like waking up to a code mess - a project that doesn't build or that I'm in the middle of debugging, etc. I do everything I can to avoid it, but sometimes it happens anyway. Right now I'm facing some indomitable bugs on multiple fronts, multiple projects. In fact, I don't even have a path forward I can make progress on, but for fixing those bugs. And they are confusing. I've been attacking each of them for days, in the past. I put them down and stepped away for quite awhile too. That's a tough spot to be in. But the worst part of all of it is waking up to it. Every day that I do that, I have to be very careful to keep my mood up and not spoil my morning and thus my day, because if I'm not I'll think about it and fret over it even if I'm not actively working on it. The only real out is some sort of mentally immersive activity or meditation that allows me to lose it, but that relief is more temporary than the bugs, so I just try to keep myself occupied until the worst of it passes. Meh. I'm guessing I'm not the only one who has run into this. I get the feeling nobody likes broken builds and hanging debugging sessions - especially say, coming into them on a Monday morning (for those of you that do the M-F thing)
Real programmers use butterflies
I wake up in the middle of the night trying to solve what seems like intractable problems and can't get back to sleep.
-
I haven't woken up to broken builds but have definitely woken up to debugging sessions for days on end.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.I see you have your Windows updates turned off. I've had numerous times where Windows has finally decided to reboot my machine to install "critical" updates. There went a 3 week soak session trying to catch a bug. I'm trying to be more generous this year to the clowns, but I swear, whoever made that decision to force reboots needs to meet my 2x4 multiple times.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I see you have your Windows updates turned off. I've had numerous times where Windows has finally decided to reboot my machine to install "critical" updates. There went a 3 week soak session trying to catch a bug. I'm trying to be more generous this year to the clowns, but I swear, whoever made that decision to force reboots needs to meet my 2x4 multiple times.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Wow. It's been a long time since I worked on software for which 3-week soak sessions were a thing.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Wow. It's been a long time since I worked on software for which 3-week soak sessions were a thing.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Some of the systems I work on only turn off once a year. Things like memory fragmentation become very important. It can be a real challenge to track down some customer issues.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Some of the systems I work on only turn off once a year. Things like memory fragmentation become very important. It can be a real challenge to track down some customer issues.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I used to work on systems like that (telecom call servers). What kind of system are you working on? I still find it amusing when systems are shut down every week or two for "routine maintenance". :-D
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I used to work on systems like that (telecom call servers). What kind of system are you working on? I still find it amusing when systems are shut down every week or two for "routine maintenance". :-D
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Production machines for packaging. Imagine a 200 foot long machine packaging beer or diapers.... you name it. If our product stops running, the entire line goes down. The cost of our machine is insignificant to the cost of the line or the downtime. So, yeah, like telecom switches and the like. :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Production machines for packaging. Imagine a 200 foot long machine packaging beer or diapers.... you name it. If our product stops running, the entire line goes down. The cost of our machine is insignificant to the cost of the line or the downtime. So, yeah, like telecom switches and the like. :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Interesting. I'd have guessed that the line would be regularly shut down for hardware maintenance, which would reduce the uptime expectations on you. Then again, your software wouldn't want to be the cause of a shutdown.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Interesting. I'd have guessed that the line would be regularly shut down for hardware maintenance, which would reduce the uptime expectations on you. Then again, your software wouldn't want to be the cause of a shutdown.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Most of the time there is an annual shutdown. In our case, our equipment tends to be wired into the production line, so it's a REALLY big deal to tell the user to cycle power. Many times, our equipment is parked under the line in protected areas. The only way to cycle power is to do it for the entire production line, and there tends to be a LOT of systems connected to that line. Note that if our system isn't working, they aren't making product, I guess that qualifies as mission critical in a light sense of the word. So, over the years I've learned not to code things in ways we take for granted. For example, malloc's are evil. Skipping the memory leak issue (We'll assume there is a matching free everywhere), this can easily lead to memory fragmentation and a hang down the road. I didn't believe it at first. I'm a believer now.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
