Ah yes, sounds about right. I particularly prefer the "make sure it's not fucked" step, very effective😂 I'd like to get more formal code reviews in place with my current team, I think we could all benefit.
Super interesting. I'll have to experiment with this, the guides I found were not this straight forward. Thanks!
Honestly I started using traefik first and I agree, the learning curve is steep. I'm only just now starting to understand what my labels are doing. But now, I've tried caddy and literally cannot get it to work, or find how to port what I have on traefik over to caddy lol.
How many developers do you have that you have to disable merging? Or is it more a safety-net?
This is super interesting, thank you for the info! Do you guys find a week for a merge too long?
So we use that, and that works well. What does your peer review process look like? Is it pretty loosy-goosy, or do you have hard and fast guidelines and checklists?
What does your merge/code review process look like?
Hey all! My team at work is struggling with growing pains of getting into a formalized review process, so I was wondering if any of you guys have some things to live or die by in your code reviews. How much of it is manual, or how much is just static code analysis + style guide stuff, etc?
Yeah, that's a great idea. Really interested to see how it goes, heard mixed info back on how easy/hard it is to learn.
Feel this on a spiritual level. Although, I can tell you from experience now that trying to collect all the crap and put it "on paper," in one place, is almost more painful after the fact lol.
On the big server, what do you use the assortment of SSDs for? I get specifically having a good chunk of solid state storage, but im wondering if you're like me and just acquired them over time, or if there's a specific purpose in mind.
At work I mostly use Matlab and a smattering of C++, at home I'm trying to learn more C++ but prefer to use python. I think my next endeavor will be learning Rust, not sure yet what I'll use it for though.