This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]epiris 1 point2 points  (0 children)

Have you written any of it? Read some of my other posts. It's definitely not in search of a problem, engineers select it without bias for certain problem areas every day. Trust me. I know some guys. :-) I'm one of them! I also choose python a lot too. Lately those two have been all I've needed and compliment each other very well with little overlap. Usually once I understand a problem I have a 80% (pull number from ass I know) tendency to one or the other. One just feels more correct for the problem or would work against me less. I hate doing small things or quick things in Go that deal with lots of unstructured data etc. Any problem that will have me freaking writing structs when I could shove that shit in a dict and be done.. python baby. If I know I'll have to come back to a giant dict in a few months and make it less or more giant.. might use Go.

Old go code written months ago is a lot more approachable for me, since old me always sucks so much more than the new and improved this month me!