Thinking about asking a colleague if they remember how they tested some code they wrote over 10 years ago according to source control.

nervously waiting to see if you get the layoff email

unfortunately also need to continue working in the meantime

tax, pension, etc deductions increased so my recent paychecks are less than previous ones, if this stays this way i guess i'll hopefully get a bigger tax refund later

still sadge

the stress of I don't want to lose git history by renaming whitelist allowlist in existing code but i also don't want to get in trouble from people if they catch me using whitelist for new additions to match what's already in the file

i dream of having a working dev and test environment

or being good enough to have my own stuff working

i don't go out of my way to fuck around with any of it, i just want to do my work, clock in, clock out

acquiring ownership of the bitchwork disaster recovery nobody wants to do

There's a petty problem that you're being told to fix, either some other teams to copy sixty something files and update that many filepaths or you can build job to send over sixty million requests.

when the service endpoint only takes in 1 item to update at a time

fml

fix bug

test production

can't reproduce bug

support tickets and people still bitching they have the bug

i think the shit's been merged and deployed long enough it should've rolled over considering the timestamps on follow up cases

needing to fix a bug that may be present in react/typescript when you don't know the tech stack

unsure if update to button broke the form

don't know nuance or difference between FormEvent vs synthetic events

test environments and local development environments broken

let me die peacefully in my sleep

forgetting to undo config changes for your local settings for development on monolith

then months later having to debug and undo them so you can login locally

i fucking hate svn

Being stuck on bitch work like getting infra to decommissioning AWS stuff and figuring out test plans for emergency cutovers

i fucking hate trying to debug microservice certs

i fucking hate react and don't understand react

Is it cleaner to have useContext to pipe in override test data for storybook and write an outer context for that code only? Real production code can ignore and not set this.

Can child component onHover update parent's stateful variable to unpause the urql/graphql datafetch in parent data wrapper component. Parent pipes queried data to child component to properly display on hover that kicked process off.

gitlab pipeline fails because it apparently has the wrong credentials

i don't recall doing anything to the credentials on my merged feature branch

worked fine last week

i am not familiar with the pipeline, i don't see any recent changes to it

Product can't keep track/understanding of how they want things sorted

but we implemented their original spec, provided feedback they approved , and as the implementer of the algorithm need to diagram it out for them to confirm they're happy with their decisions

Wondering why and being confused looking at code you apparently wrote a month ago.

Never made or can't remember making UML diagrams, what are your opinions on them?

snowflake used to tell me seconds if i did something syntactically wrong and it can't run my query

now it takes 2 minutes to intialize the UI first? what the fuck?

I'm reading some react/typescript code and I haven't work much with any other language or paradigm where I might have a function return multiple objects that are different types

e.g.

const { sna, foo, bar } = useWhatever();

I mean I guess it's just unpacking properties from the actual return object but that isn't apparent to a newcomer at a glance (if I remember correctly)

https://softwareengineering.stackexchange.com/...

Looking for additional insights from the wise devrant community

integration test passes on IDE and remote repository pipeline

but it fails locally when run with gradle

i don't understand spring (boot) and i fucking hate it

error stack trace so fucking long you can't see the relevant part that matters of the unset environment variable you need to set

fuck you spring (boot), and gradle

even with the info flag on it doesn't show me the relevant part , fuck you

gradle

I barely remember what I did or why I did

but if you need to comment it in, does that mean I don't understand enough, or gradle sucks , both or somethign else

Reading a note from yourself a few weeks ago that had an idea of how to do something, and wondering what the fuck it means or if we even have a simple viable solution to our problem.

Trying to figure out what the fuck and why I did some stuff in gradle dependencies to get shit to work

joke is I didn't understand it back then anyway and was just following some documentation to get shit to work

ah stackoverflow , the good old get downvoted and voted to close with no explanation why

at least back in the day I'd at least get told why while they did that

java

@ValueImmutable

I have used this to generate code

I try to use this to generate code again for a new class

it doesn't work, doesn't generate anything, can't tell what's different outside of new class being in a test package

thanks obama

yes i'm too retarded to figure out the problem from googling and trying to read some documentation

- divide large refactoring and architecture changes into multiple small pull requests

How do you go about getting code reviews? Wait till you have all the pieces so people have the big picture?

architecting non-trivial code for the first time and doing poorly

returning to it and having trouble building on top and around it

fml

bicycle stick comic meme