overview for podatus

I kinda wish there was a better way to do if err != nil in go in c/golang@programming.dev

[–] podatus@programming.dev 3 points 1 year ago (1 children)

I would rename Check to Must which there is at least some precedent for.

Seriously, though. How often do you think of the Roman Empire? in c/asklemmy@lemmy.ml

[–] podatus@programming.dev 10 points 1 year ago

I eat 2 cups of food for lunch on weekdays because if it was good enough for a roman soldier to march on it's good enough for me to go clickity clack on a keyboard.

How do you get your team to write tests? in c/experienced_devs@programming.dev

[–] podatus@programming.dev 4 points 1 year ago* (last edited 1 year ago)

code review as others mentioned but if everyone is on equal footing in the review then you need some kind of enforceable policy where work isn't merged until a policy team signs off on it. Who is on that team becomes a matter of office politics and navigating such. With support of CTO that can be worked out for designated roles among peers.

If the people on that policy team require too much and slow things down in your fast paced environment then that is another seperate issue to navigate to find the right strategies and methodologies.