LogFAQs > #953261803

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, DB5, DB6, DB7, Database 8 ( 02.18.2021-09-28-2021 ), DB9, DB10, DB11, DB12, Clear
Topic List
Page List: 1
Topicgod, i hate writing software
grimhilde00
04/26/21 7:46:16 PM
#9:


PunishedOni posted...
what is your job like? my experience has been that even when there's an interesting problem, most of the actual work is the same boring stuff ive been doing for 6 years

Some example projects that were more interesting (I've had boring stuff too but that's like less than one quarter out of the year otherwise I'd hate my job more)
  • needing to rework how we query for some data. Multiple endpoints needed to be more focused, make use of better indices or add some. Break up a query into 3 parts to optimize things, account for older databases that you can't just update an index on, to reduce row size. Brought queries down from p90 40 sec to 400 milliseconds.
  • doing a migration from one data model to another, but having to support both at the same time...and needing to add a lot of validation there to make sure that's going as planned. Multiple parts of the system.
  • investigating an algorithm that had many different weighted reasons for different decisions and figuring out why some decisions were too flakey and fixing that once you can do some data analysis
  • figuring out different components attributing to latency to identity the main pain points, and how to address each of those. Some of that was tricky to measure because part of it is hardware connection issues, which could come out of order and firmware isn't tracking it exactly and you don't know which device is having the problem, so I had to make assumptions from various parts of our system and keep that in mind
  • having to deal with out of order things in general is annoying / not boring. Customers are often in offline areas and we have to keep things in order even if later events come in before earlier events and account for that
  • just more complex systems in general. make some assumptions about sparse data coming in vs regularly timed data, but then timestamps affect many different parts of a system and have different repercussions
  • basically customers saying they have a problem, and figuring out why, and it can be difficult to investigate and not obvious and usually their pain point is just an indirect effect of the cause. Then being able to figure out how widespread it is and the root issue
and visualizing the business impact on all of the above

being vague. But things can get interesting? it's not just crud work.

I do not consider my job the most interesting available, also. It's not boring, but if I wanted to there are even more interesting things out there.

---
aka kriemhilde00
... Copied to Clipboard!
Topic List
Page List: 1