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
-
"I know right, it's so annoying, there is this other team who we have had to clean up after 10+ times this year. Are you going to fix it or will we need to do another early reset?"
If he is vague again, just reset it. "Your instructions didn't work, we have reset it, it seemed the more straightforward way forward"
And if you want to pressure to move away from copying prod, mention it's most likely a violation of GDPR or something. -
@BordedDev it isn't a definite gdpr violation because we're developing the software for about 100 in-house dau and 300 in-house mau, so nobody would gaf. And even if it somehow got flagged as a violation even though it's not especially sensitive data, arguably legitimate interest, and at a very small scale, they would just pay off the regulator from the same money they're too stingy to spend on less than a TB of disk space for individual databases for all active branches, because this is Hungary we're talking about.
-
> 'I know I have a problem with asking for help.'.
I've been told just that a few times. Also, it's been provided as a reason for 'poor communication skills'.
...thing is, if I can find the information I need myself, why the fuck should I even bother asking others? ...especially when most of the time when I asked about something to 'throw them a bone' it was always the case that I'd have a roundabout conversation && I would have to explain all the things I've already done, checked or whatever.
As such, efficiency-wise, I'm better off searching for whatever I need myself.
You, however, seem to be having a slightly different problem. -
@D-4got10-01 The reason why we're supposed to "always ask for help" is that the company has a really bad knowledge silo and code rot problem. Nothing has a well-defined contract and half the team wouldn't know what to do with it if it existed, so even uncommon codepaths that are taken once a month tend to become incorrect over time. As a result, the only way to determine how anything works is to work with specifically that subsystem for years and years until you learn the general shape of every single function by heart.
-
@lorentz I... don't envy you.
-
and instead today I came to the conclusion that asking for help has only gotten me exploited by opportunistic parties into bullshit they wanted and wasn't for me
it's probably a good trait
---
if things aren't documented I would start a repository of documentation. would annoy me. I can't remember things even on my own and extensively use obsidian for notes for my own hardwares and softwares
make a wiki of all knowledge base. github has a wiki and I used that when I worked
I did get fired once maybe for this reason. I was pinning things in slack to document them for devs after me and my team lead didn't seem to appreciate me documenting her pigeonhole probably. with Google docs she would delete my comments but on slack she couldn't so that was maybe my mistake not picking up on that sentiment of hers until we got into design documents and not just environment setups. you'd think I'd have been appreciated smh
I know I have a problem with asking for help. I'm aware it's a problem, I want to solve it, and I'm trying, but this is easier said than done.
In my defense however, the issues I'd need to ask for help with are completely absurd. We have a shared Feature environment with a shared database. A push to any feature branch auto-applies migrations to this database, so it's full of broken script output. Tests are supposed to use this database. We do not have full rights to edit this database so we can't try and fix the issues. Instead, the database is reset from production once a week, discarding all changes including anything we deliberately put there for testing. I asked who broke the database and if they could fix it please, somebody responded with freeform text roughly describing the fixes _I should apply to fix HIS TEAM'S mess_, which didn't include any technical identifiers and referred to tables and columns exclusively via vague approximate names.
He then posted a screenshot of an e-mail from about a month ago in which HE complained to MY team lead about how "some people" keep breaking the database, which contained no examples and no suggestions, but was sent immediately after the first time this year that we actually properly broke the shared database. By that point they were past their 10th broken migration that warranted an early restore.
rant
shared envs
shared db
breakage