101 reputation
2
bio website
location
age
visits member for 9 months
seen Jul 25 at 13:49

Jul
19
comment Should we avoid using design patterns in constantly changing projects?
@immibis Good point. We have multiple teams, one for each major technical asset, and we often build interacting API's. But the stakeholders should write only the general "story" or requirement and let the independent groups/developers collaborate together based on documents and technical knowledge to build the final result.
Jan
27
comment Returning different types from one function in a dynamically typed language
My two cents: I hate it when that happens. I've seen JS libraries that return null when there are no results, an Object on one result, and an Array on two or more results. So, instead of just looping through an array, you're forced to determine if it's null, and if it isn't, if it's an array, and if it is, do one thing, otherwise do something else. Especially since, in the normal sense, any sane developer is going to just add the Object to an Array and recycle the program logic from handling an array.
Oct
25
awarded  Teacher
Oct
25
awarded  Supporter