Looney Tunes fans looking at Bugs all day
Project managers // ER doctors: “Looking at a room full of people coding”
Fixing bugs all day for work can be rewarding though. Fixing bugs at 3am for the assignment that’s due that day, not so much.
It’s not real computer science unless it’s 11:45pm with an assignment due at midnight that keeps seg faulting for no apparent reason.
Better to leak that to segfault, take this:
at which point you turn on all symbols/debugging, bloat your binary 10x and submit it …cuz it seems to work sometimes then.
It says looking at bugs all day. That state where you slowly realize that you have no idea how to fix them or what even causes them.
Cave divers looking at bugs all day:
Ah, Google Lens certified photo.
I am a lazy pirate
some wish computer science was that simple
I’d be much happier fixing bugs. New features drive me mad. Takes so much effort to get people to figure out what they want.
Data Analyst: So what do you want to measure? What question do you want to answer?
Customer: Can you do a column chart, where I can see how many Orders we have?
Data Analyst: Column chart? What’s the Axis? Per day?
Customer: No, per month.
Data Analyst: Right, so new Orders per month?
Customer: No, how many we have in general, new and old.
Data Analyst: Do you mean the old ones still open at the start of the month?
Customer: That’s a good idea, yeah. Actually, can you add the ones we complete in that month too?
Data Analyst: The amount of completed orders? That would double-count them.*shared moment of confusion*
Customer: Don’t make it so complicated, I just want to see how many orders we had.
Data Analyst: Let me ask again, what question do you want to answer?
Customer: I want to know how much our teams are working.
Data Analyst: As in, how many orders they’re completing?
Customer: I also want to see if we need more people.
Data Analyst: Like, if they can’t complete all their orders? So basically, the rate of completed versus new ones?
Customer: Ooooh, good idea, can you put that rate as a line over our chart of new, old and completed orders?Customer: Oh, and the warranty returns too! They need to be processed as well, that’s also work.
Customer: Actually, we have this task tracking for who does which work for the order or warranty return.
Data Analyst: Shouldn’t we use that to track how much work the teams are doing?
Customer: Yes, put it in the chart too.
Epilogue: The Customer got a separate chart for the tasks - turns out I’m not charging by the chart, so you don’t need to cram as much as possible into a single chart. They also were persuaded to stick with “Old” and “New” to show the total workload, with the “Old” bars providing an indicator for how much stayed open and whether the backlog was growing.
🐈🐈🐈🐈 you’ve got your cats in a row!
The only cats I’ve got are con-cats, unfortunately, but they do put things in a row.
I’d love to work more with animals - pythons, anacondas, pandas, cats… Alas, I am stuck with SQL and Power BI, for better or for worse.
One (af)fixes bugs all day, one fixes bugs all day - “we are not the same”.
Epidemiologists weep.
ppl who majored in bio but later went to med school looking at bugs: dark image
Ya like worms?
