Details
Joined devRant on 9/13/2018
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
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.1
-
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 work3 -
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 that3 -
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 documentation5 -
- 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?2 -
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 meme1 -
Mess up explaining a pull request working backwards from the why of the issue, instead of explaining what my code changes would do in the order the machine would execute
welp
should've clarified on what/how they wanted me to clarify what I did -
Follow documentation, copy supposedly working example, follow advice of tech lead, try to implement a bug fix, it isn't working and the recommended way to test it from SMEs elsewhere is inconsistent
fml1 -
Thoughts on the idea of including links/query starters for debugging or where the fucking logs are in AWS, grafana etc in repository READMEs?1
-
when you get response to AWS command `Credential should be scoped to a valid region.` but your coworkers don't so you have something different to debug on your end
fml1 -
recruiter internal to a company reaches out, I think I have a good screening call with them, get a rejection afterwards
welp4 -
Anybody have any easily searchable sync-ed notes apps that are free or one time fee they'd recommend or do I need to get better at google drive?
I've been thinking about trying to cheat and have a git repository to imitate it but imagine the automation to be a pain in the ass or infeasible if anybody has already walked down that road.5 -
New to AWS, is my best option for having a integer value (maximum number of items to process) that I can override for a lambda step function
to read a value from an S3 bucket where I can overwrite the value if I want to change it. This seems silly and I feel silly as I expect my situation should be simple and not novel at all.
For some reason I expected I could use an environment variable, but didn't see an option to overwrite it in the web GUI https://docs.aws.amazon.com/lambda/...2 -
asked to estimate size of ticket about adding test data, but no details about what test cases or what kind of data
welp6 -
When the IDE doesn't show a scrollbar so you need to know/see to stretch it to find the settings you need.
fml
fuck u jetbrains1 -
get bug
find slack context
senior describes some stuff as magic and it's unfortunately not working as expected
fml2 -
the bittersweet relief/despair when your veteran senior tells you that it's a legacy mess you're dealing with here, and that's the basis of the tips/strategy/context given in a task1
-
when docker desktop lies to you it updated when you looked to update to latest weeks ago
so you try again and realize there's no fucking progress bar to get any sense of progress -
fuck up some code and the mistake gets noticed later
add tests to cover up my fuck up
get asked to add tests for other existing presumably correct code i did not add or change in the nearby area
so be it4 -
i am an unskilled pussy without strong opinions
sometimes you get conflicting feedback on code reviews from seniors
i'll do whatever you guys want (haven't encountered anything egregious enough that I do have a strong opinion on yet), but y'all may need to sort out how you want me to slice this cat4 -
team lead/senior telling you that you're probably going to break prod and have to patch it for the next couple of weeks when working on one of the first migration epics on legacy monolith, but we'll get good data from it doesn't make it any less terrifying5
-
we need you to do migrations in a legacy codebase which includes changes against a tool you will not have access to test against1