rush job to get my year end review in before vacation

get feedback i need to write more and elaborate

haven't had that happen to me before, almost feel like im back in school

i struggle to remember anything to begin wtih

ticket so large it can be divided into multiple subtasks with their own sizes

also divided into MRs big/substantial enough to be annoying to review

can't finish it all in time for vacation, rip

possible skill issue: i wish java enums were easier to work with

when you made a code change 2 months ago but completely forgot about it and why you did it

there are development and staging environments

the names used to refer to each are swapped between the devops team and development teams

these resources are shared

i struggle to know which one means what

I'm used to IDEs (e.g. jetbrains ones)

visual studio code for web development (recommended tool with open in containers that somebody else set up in my team)

anybody have tips on how they pimped out VSCode to be closer to an IDE?

redoing shit you don't remember and understand which you did once before

fml

not sure what i changed, if anything

but my previously working code calling another microservice now fails because invalid jwt token

fml

Docker gurus: I am not familiar with docker, any immediate problems stand out about the idea of trying to make customized vim into a redeployable docker image for easy portable usage?

Thought I might side step having to save config and reinstall stuff (still got to pimp it out the first time)

excel just apply my formula to rows without empty data

yes i know there's over 100 thousand rows

pls

my query syntax was not wrong in retrieving no results

the table's most recent entries are 2018, nothing in any year after that, which i was querying

fml

when your teammate finds the existing endpoint that returns what you need after you frankenstein some dumbass shit from other existing endpoints that you managed to find

fuck me

i said blacklist/whitelist without thinking about it instead of deny/allow, and got gently reminded about it, oof

browser automated test requiring multiple logins of different accounts

try to logout the legitimate way (automate hitting the button)

or wipe cookies?

we need you to fix a bug you cannot reproduce

but we a 3rd party encounter intermitteningly

fuck u aws

all that money and u can't read idiot proof documentation for me to have SQS connect to a VPC endpoint to read a message

also fuck u search algorithms for not handing me an easy bake solution to what is a not a novel situation

also fuck me for being unable to git gud

make no changes i can recall or see

spring autowire breaks

Add XYZ for foobar

vs

Add XYZ

The first name has that little bit of extra detail so I can have a clue what's going on since these damn jira tickets aren't linked up so I'd know what depends on it.

I'm too dumb to have unpuzzled the architecture document and scooby-doo-ed all this shit together for what I'm doing and why I'm doing it.

i dont know npm

today i learned `npm install` in root project directory doesn't do what running `npm install` in a subdirectory that actually has a package.json

in this case there was no package.json at the root project directory if it matters

shoutout to fucking eslint not telling me to try installing the fucking packages it can't fucking find, as im a monkey who doesnt know what their doing

well i suppose this is irrelevant since there's yarn, gulp, webpack or whatever is the new hot front end package manager thing

Story points aren't supposed to be mapped to time directly.

Spikes and investigations should be timeboxed.

How do you story point spikes and investigations? Just have the same arbitrary story point value for all spikes?

reading test strategy of work done by my senior whom i respect, which goes something along the lines of:

"putting this into production and praying"

i dont know how to feel

no ticket details

not giving me some useful documentation in our first conversation to clarify the ticket, that you have

FUCK U APPLE JUST GIVE ME XCODE, I DONT WANNA MAKE AN ACCOUNT

issue can be reproduced on production only

being asked to fix a bug that cannot be reproduced consistently

difficulty in reproducing bug behavior

think i found a solution to prevent the infinite requests being sent by a react component who's code keeps getting rerun by react's scheduler.development.js

i have no fucking clue what's going on, on top of not having any foundation in react

"you don't seem like you have X years of experience under your belt"

oof

i dont disagree but i wish words could kill so i didn't have to survive that, i suppose i should accept being mediocore

im not laid off (yet?)

but my company is doing layoffs , and it's my first time experiencing this

any tips on coping in such uncertainty and misery

i know when i get some spare time it's going to be time to update resume, leetcode and cold application hell to try and cover my bases

can't use IDE automated refactoring to extract method because we can't figure out the types of parameters and variables

fuck you typescript, javascript, graphql

We need you to fix this important pipeline you are unfamiliar with.

Ugh