4 ms·
Sounds like you worked with shitty backend engineers. I don’t understand how Go has anything to do with that. Nobody uses elixir bud, and saying basically “my s
by kc1116 7y ago
Sounds like you worked with shitty backend engineers. I don’t understand how Go has anything to do with that. Nobody uses elixir bud, and saying basically “my software would be perfect” is a naive silly thing to say.
- andy_ppp 7y agoI just think I've had this happen three times in a row, as if there is something likely to be wrong with the types of programmer who choose this technology. I never said my code is perfect or bug free at all, you just made up a straw man to weaken my anecdotal evidence.
- apta 7y ago> I just think I've had this happen three times in a row, as if there is something likely to be wrong with the types of programmer who choose this technology. You can add a datapoint to that based on what I have experienced as well at an employer. Exactly what you mentioned, so much time wasted either due to reinventing the wheel, or because of language friction and it being way underpowered to model the problem at hand. I keep laughing that Java would have been a way superior fit in practically all fronts.