valid reason IMO
sip
joined 2 years ago
not all wine has aging potential.
I don't think he was trying to find excuses.
yea, but it stops being fun when they say it's a bug and it's always supposed to work like that.
this is ongoing now. Our "creators" were supposed to be "matched" for a "job" based on "skills", not "skill". pure chaos
some places are like this. Where I work now seems to be like this. Tech lead starts working on something, breaking things, then he has 100 meetings and either gets distracted or has another emergency and leaves things broken. He doesn't write tests, pushes images built locally without CI/CD pipelines and lately he keeps messing pubsub subscriptions. Data from other services stops coming through and people ask us why isn't our service working. ugh
unless everyone starts coming in early just to pester you.
this ain't a criminal court. It's ok to be helpful to a degree, especially if a bunch of people can't work because of that issue.
I prefer the FP approach where I create smaller functions that I compose together in larger functions or methods wich rarely repeat themselves elsewhere identically. Forcing extractions and merging of such functions often leads to weird code acrobatics.
yea but the counter was that they need to move fast.
In the beginning, tests slow you down, but in time, the amount of bugs tests catch and the confidence in refactoring adds up to way more saved time.
yea but if we both aren't really keen on writing tests and I review you, it would be in my lazy ass' interest to 👍 without tests.
versioning and version dependencies are more manageable.
idk why aren't they using
git clone --filterto clone a part of the repo and/orgit sparse-checkoutor at leastgit status .while in the subdir you are doing your work. what's the point of doing git status on the whole thing if you're working in a dir?