codingvelocity

6 ms·

1. 31.▲
   See Android Go(codingvelocity.com)

   112 points by codingvelocity 11y ago|63 comments
2. 32.▲
   by codingvelocity 11y ago

   Not the original person, but in any organization with a non trivial amount of code needs someone that is really on top of managing how the applications build and how dependencies mesh together. There's many tools to learn and leverage
3. 33.▲
   by codingvelocity 11y ago

   I used locust to supplement testing that third party was doing (they used some ibm product that I didn't have a license too). I liked locust because it was easy to start using, but you write a decent amount of code if you have a compl
4. 34.▲
   by codingvelocity 11y ago

   It's largely accepted that while you can use gdb, it's not really good at debugging go code. from your own link.. "GDB does not understand Go programs well" https://github.com/derekparker/delve delv
5. 35.▲
   by codingvelocity 11y ago

   I agree largely with what you say but advice point 2 is an obvious smell in today's working world. I'm taking that advice as "don't do anything that would prevent you from moving tomorrow". That includes having a