Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Sounds junior or intern-level to me.
kgbemployee238474dAnother example of seniority by time spent and not by level of knowledge.
I genuinely wonder how these types get past the technical interview.
C0D44269874dDay 1 - set up environments
Day 2 - understand workflows (git, releases, ect)
Day 3 - understand work load and feature / task flows (jira boards, Trello. What ever you use and how you use it in your team)
Day 4 - actually start doing work unless the above is a complex snowball that takes more then 3 days to get done.
This is "new job 101" 🤷♂️
jeeper514974d@C0D4 in government:
Day 1-5: apply for access
Day 5-15: wait for interim clearance
Day 15-20: wait for access card printed, then play certification games
Day 20-30: struggle with abused, repeatedly orphaned code, and try to understand processes.
Day 30-35: meetings about the meetings.
Day 35-40: finally start to get some work done.
Day 40-45, somebody fucks your access, request access again
Day 45-50: get access, but learn that its interim pending some new certification somebody heard about somewhere that’s not even relevant to writing code
Day 50-55: study during work cause fuck em.
Day 60-65: get the cert. maybe get some work done for like 3 weeks til somebody fucks the ops side again.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job