jbrechtel/willfullyobtuse.com
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Reformatting job description

Browse Source
This commit is contained in:
James Brechtel
2024-10-10 20:36:12 -04:00
parent e1c595f482
commit 360a4af22d
1 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
one.org
View File

@@ -277,8 +277,7 @@ My formal job title is (I think) "Director of Engineering"
My reponsibilities include My reponsibilities include
** Actual responsibilities **** Software design
*** Software design
I don't design all of the software here by any means, but I am either I don't design all of the software here by any means, but I am either
doing the design myself or I'm involved in the design conversation of nearly doing the design myself or I'm involved in the design conversation of nearly
any non-trivial component. any non-trivial component.
@@ -287,7 +286,7 @@ We're starting to outgrow this but it's proving a little difficult for
both me to let go of being involved in everything and for others to both me to let go of being involved in everything and for others to
let me be less involved. let me be less involved.
*** Keeping production from breaking **** Keeping production from breaking
At the end of the day, if the system is on fire then I have to make At the end of the day, if the system is on fire then I have to make
sure it gets fixed. sure it gets fixed.
@@ -305,7 +304,7 @@ ensure that the software we're building is not falling over on
itself. Thankfully, our tech stack is faily reliable compared itself. Thankfully, our tech stack is faily reliable compared
to many others I've used in companies prior. to many others I've used in companies prior.
*** Business goal prioritization **** Business goal prioritization
Providing technical input to and vetting of business goals. Providing technical input to and vetting of business goals.
This is basically a combination of saying This is basically a combination of saying
@@ -314,31 +313,31 @@ This is basically a combination of saying
- "We can get 90% of the benefits of A if we do B - at half the cost - instead" - "We can get 90% of the benefits of A if we do B - at half the cost - instead"
- etc... - etc...
*** Writing stories and technical plans **** Writing stories and technical plans
Many (but not all) of our "tickets" "cards" "stories" what-have-you Many (but not all) of our "tickets" "cards" "stories" what-have-you
end up getting written directly by me. This is, in some sense, an easy end up getting written directly by me. This is, in some sense, an easy
job to delegate out but it's risky to do so because getting this part job to delegate out but it's risky to do so because getting this part
wrong can lead to a lot of re-work amongst other costs. wrong can lead to a lot of re-work amongst other costs.
*** Iteration planning **** Iteration planning
Deciding what the team will actually do in a given week. Deciding what the team will actually do in a given week.
*** Ensuring timelines get met **** Ensuring timelines get met
While we don't have a lot of "hard dates" on deliverables compared to While we don't have a lot of "hard dates" on deliverables compared to
[[#/large-companies/][large companies]], we have them sometimes and it's my responsibility to [[#/large-companies/][large companies]], we have them sometimes and it's my responsibility to
either ensure we hit them or to understand why we didn't so we can either ensure we hit them or to understand why we didn't so we can
better [[#/managing-expectations][manage expectations]] in the future. better [[#/managing-expectations][manage expectations]] in the future.
*** Discuss story details, expectations, changes, etc **** Discuss story details, expectations, changes, etc
[[https://en.wikipedia.org/wiki/User_story][A user story is a promise for a conversation]]. Very often I am the one [[https://en.wikipedia.org/wiki/User_story][A user story is a promise for a conversation]]. Very often I am the one
keeping that promise and this puts me in the middle of a lot of keeping that promise and this puts me in the middle of a lot of
conversations. conversations.
*** Adjudicate technical disagreements **** Adjudicate technical disagreements
Fortunately this doesn't happen all that often - and usually when it Fortunately this doesn't happen all that often - and usually when it
does it's around more trivial things (bikeshedding affects us all), does it's around more trivial things (bikeshedding affects us all),
but it does happen. but it does happen.
*** Maintaining technical quality **** Maintaining technical quality
When we have code quality issues I feel personally responsible. When we have code quality issues I feel personally responsible.
It's my job to either prevent them in the first place, or plan an It's my job to either prevent them in the first place, or plan an
@@ -346,7 +345,7 @@ execute work to alleviate quality issues.
Balancing that work with business deliverables is a skill unto itself. Balancing that work with business deliverables is a skill unto itself.
*** Primary interrupt **** Primary interrupt
This responsiblity is a hold-over from my tech lead days and it's one This responsiblity is a hold-over from my tech lead days and it's one
I need to get rid of. I need to get rid of.