Futurice Blog

In my previous job at the Finnish software consulting company Futurice (http://futurice.com), there was a long discussion about this that ended with a volunteer-based publication of peoples salaries - around half of the 200 people opted in. The result was a bit anti-climatic: peoples wages were consistent and fair, no big drama. After switching jobs to another software consulting company Reaktor (http://reaktor.com), I brought up this topic and the discussion was very similar. I decided to try a different route: I created a wiki-page called "Voluntary salary information" and added my name and salary to the top of the page. I then wrote a post to our discourse board explaining why I thought this was important. As of now there are 68 names on that list ( with only 1 obvious troll ) out of about 300 employees. Our head of HR replied to my discourse post with a detailed explanation of how peoples salaries are decided. Overall a great day for transparency.

I think you can store emails but process them only in an anonymizing publicly auditable proxy, ensuring that downstream business services do not have plaintext access whilst still being able to send outbound emails whenever you want. I wrote about it recently: https://futurice.com/blog/trustworthy-services-from-cloud-provider-imp… The key is to grant cloudfunctions.functions.sourceCodeGet (Or AWS/Azure equivalent) on the edge so anybody can verify that your proxy is above board. End users just have to trust the Cloud Providers access controls, not the service providers word on implementation.

Not just IP problems, but also encourages bad work habits. His company should of sponsored this work if they felt it was in their best interest. This type of hero behavior burns people out and keeps open source projects with very limited resources. Edit: To the author because he replied once to this thread: I hope in the future you feel comfortable in the future asking for time to work on open source projects during company time and realizing that you doing work that benefits your company for free is not in your or your companies best interest long term. If you feel that they would be unwilling to do this during work hours then push for something like this: https://futurice.com/culture/sponsoring-free-time-open-source-activiti…

https://www.noredink.com/ uses it https://circuithub.com/ uses it Futureice uses it, here they talk about their experiences with it: http://futurice.com/blog/elm-in-the-real-world Here's a presentation by Richard Feldman of NoRedInk on their experience: https://presentate.com/rtfeldman/talks/shipping-a-production-web-app-i… I think new technologies are best evaluated by a careful subjective evaluation of their future promise (something to grow with) instead of looking at how many people are using said technology already... but I'm a startup guy with Shiny-Thing Bias (STB). :) (and I'm already an Elixir fan, and Elixir is chummy with Elm!)

Exactly which part of that thread leads you to believe that "React plays just fine with Web Components". I suggest you watch https://www.youtube.com/watch?v=g0TD0efcwVg which gives a very clear picture of the current state of React/Web Component interaction, including the challenges associated with it. edit: another good read if you're interested: http://futurice.com/blog/combining-react-flux-and-web-components

Recommended read: http://futurice.com/blog/reactive-mvc-and-the-virtual-dom

Not the Elm Architecture, but I found this a very good article on how MVC differs from unidirectional approaches: https://www.futurice.com/blog/reactive-mvc-and-the-virtual-dom/

If you want Swift on Android, have a look at Eclipse Xtend: http://futurice.com/blog/android-development-has-its-own-swift

Andre's twitter feed has a link to a article on the same topic. (edit: I find it easier to read an article instead of slides.) http://futurice.com/blog/reactive-mvc-and-the-virtual-dom

Interesting, I've been playing with React/Flux a bit lately. I enjoy them more than other JS frameworks, but agree it doesn't feel like it's quite right yet. This blog post from the same author gives a bit more detail than the presentation slides: http://futurice.com/blog/reactive-mvc-and-the-virtual-dom Looking forward to seeing the presentation video