breakalot

11 ms·

1.
by breakalot 4y ago
The problem is that devs simply can't accept that ops exist. We spoiled devs way too much. Software are still being thrown over the wall and ops takes all the blame. The problem is that many devs can get away with spawning servers and
2.
by breakalot 4y ago
Nowadays employers fail miserably at fulfilling basic needs like, believe or not, giving someone a Linux computer.
3.
by breakalot 4y ago
Yes, can relate. Working in a field where people can get frustrated very easily is though. Specially if you are in the receiving end. I worked with a lot of nice colleagues that makes the job more enjoyable, try to focus on that and ignore
4.
by breakalot 4y ago
RIP Deis
5.
by breakalot 4y ago
That is great! I wish xrdesktop would be updated to gnome 42 and upstreamed one day.
6.
by breakalot 4y ago
The resource IS the state!
7.
by breakalot 4y ago
Perhaps using guard you can automate that https://github.com/guard/guard
8.
by breakalot 4y ago
Perhaps buildbot as a Jenkins replacement https://buildbot.net/
9.
by breakalot 4y ago
Usually codebases are organized into modules/classes/etc and most test suites can run specific test cases (or groups of tests, specific domains, etc). I think if you can't do that in a codebase, then one has bigger organizati
10.
by breakalot 4y ago
> Microservices was always a solution to the organisational problem of getting more developers working on a system at once. Wasn't Continuous Integration (CI servers) created long ago to solve that? Where developers can test and rel
11.
by breakalot 4y ago
You mean "duplicate"?
12.
by breakalot 4y ago
I think we, collectively, should strive for avoiding making other people's life stressful. Just by having a different role, title or label attached to you can be pretty stressful by itself, specially if you are out numbered and decisio