hamvocke
I'm building a small web app with an interactive tutorial and a browser-based singleplayer game that helps people learn and practice Doppelkopf. I've just released an English version:
I found that worrying about deployment automation early on is immensely valuable, especially for side projects. I don't always find time or interest to keep working on side projects after a regular day of work. Quite often there are weeks or even months where I abandon a side project only to come back at a later point when motivation is back or things have settled down and leave more time for my side projects. If I didn't take the time to automate testing and deployments (which makes a lot of what continuous delivery is about) I find myself struggling with getting things up and running and become frustrated before I even get started.
Then there's only one way to make sure that my test and deployment automation keeps working: running it regularly, e.g. in a pipeline.
So, yes, don't over optimise your deployment pipeline early on. But having one in place early can pay off really soon -- and maybe even keep your side project alive.
Could you elaborate why Sketch didn't work out for you?
I did have a hard time figuring out what those odd numbers on the right side of each row should indicate, though. Displaying the percent symbol on hover does not help either. You should provide a tooltip in the individual rows as you do it in the detail views. Otherwise this number just feels odd, especially in the "Trending" view.
It's very disappointing that the only information they provide to "explain" their bold statement are some colorful boxes listing the names of some tools and services. I do not want to sign up just to get even a basic understanding about what I can and cannot do with deploy.io
Grooveshark music streaming service forced offline in Germany
While we have concluded this particular experiment, we constantly experiment with new and more secure authentication mechanisms.
Stay tuned for something even better!