We've been blocking off Wed/Thurs as no meetings day for engineers largely inspired by this article. It's amazing how much you'll get done with 2 days a week uninterrupted. Down side is that it's tough to schedule a meeting (and room), so some meetings get pushed back by days or weeks.
That's not a bad thing. It means meeting time is precious and valuable, so the bar for meetings is higher. People are also less likely to put up with non-productive meetings.
+1 please do. As an accelerator connected to US capital & experience, same language/culture, and being in the same timezone with a 2hr flight, this can only mean great things. A lot of engineers in the community here (myself included) are not necessarily willing to give up life in beautiful Vancouver to move to an industrial park in Silicon Valley.
Exactly. My poke was meant to highlight the fact that a language is more than just syntax. I'm assuming this is intended more as a tool for helping start a transition into Scala, with a heavy amount of refactoring afterwards to convert it to idiomatic Scala.
Unfortunately, many people seem to think FP is the hot new thing and OOP is already over; they ignore that OOP happens to be a great way to structure code that focuses on naturalism, while FP forces math-like structuring.
There is massive fad-like interest in FP right now, especially in academia.
I don't see the vice versa in academia at all. Where is this OOP hype that you think exists? Even OOPSLA changed its name to SPLASH to de-emphasize objects.
FP is quite useful, the fad I'm referring to is "let's make everything immutable" and "let's just use functions to structure our code." This ignores what FP is good at and how it doesn't really compete with OOP in terms of problem space: OOP is basically modelling based on how we think and talk about things (kingdom of nouns), FP works great for more abstract math-based concepts (kingdom of verbs). Immutability solves one problem (consistency) that has other real solutions as well (dependency propagation).
There is still a lot of work to do on objects to not make them suck, just like there is still a lot of work to do with functions. My ax-to-grind revolves around work on objects being neglected in favor of a fixation on functions.
I'm curious why you're running a docker file instead of committing a pre existing development docker container, and shipping that as the deployment artifact? This approach seems to treat docker more as provisioning tool (ansible, chef, puppet etc) and less as a continuous delivery "shipping container" tool.
