HN user

bechampion

176 karma
Posts13
Comments112
View on HN

I love slack , but they gotta get their game together , this year I have personally seen around 4 or 5 outages, what annoys me the most is the way the app fails, it simply greys out text that you just sent , images take forever to upload (if they ever upload) , i think if you gonna have this many outages maybe build something into the UI

I worked in a big bank in the UK using monorepo "cuz Google uses it", error number 1, your not Google. The clones were gigantic, Jenkins would timeout cloning the whole project when all it needed was a bunch of files. Merge conflicts all over the place, but the best part, we had scripts on our pipeline literally removing folders after cloning the repo to avoid automatic inclusions of libs etc. In my opinion separation of boundaries is one of those things that should t be mess with.

Remember when Linux was hard to install and run as desktop ( multiple screens , acpi , sound , winmodems ) ?? We all have had this colleague that gets frustrated and installs windows after 10 minutes , And spends the rest of his life saying that Linux is of fanatics , geeks etc . Well this post it's literally the same .

I'm still not a big fan to run stateful services in a platform mostly built for stateless . Also not a huge psql user , but replication and failover in psql has always been a half-done job, kube isn't gonna fix that.

I think an explanation would be PTRACING a process and tapping on its syscalls will always add some latency , for example time(process(open())) < time(ptrace(process(open))) if that makes sense ? , similar to selinux ... there's a cost to tapping syscalls.

they make me cringe too , but i often question myself if feeling this way is my own fault. What is wrong with loving code or loving a little project? Do we all wanna be seen as hardcore devs that do this work cause we are forced to? I'm not attacking just a question I'd like to pop out there.