I would like to officially apologize for offending the android and cyborg populations, by bringing too much attention to the food desires of the meatbag population.
> The workflow I ended up with was to write a function without any type annotations. Ignore all the red lines of the IDE’s confusion. Compile the code. In the output look for a warning about (Long => Int) return value being ignored in a function returning Unit. Copy (Long => Int) into my code as the return type annotation of my function. Compile again.
That sounds like the most stupid way you could do things.
I have been in interview debriefs where people were concerned about a candidate not advancing enough in a previous position, but I can't imagine one failed startup being detrimental, at least where I currently work if you get interviewed by those same exact people. :) The important thing is what you can talk about from the startup.
Heh, I hear that off and on and I'm curious where that comes from. Is it just something that people repeat because it sounds good, or is there solid evidence for it?