jcahill84

At schezzle (https://schezzle.com) we use Spring. If you don't want to go the whole DI IoC path, just use Jersey (JAX-RS) directly. Dropwizard isn't a bad implementation either, but can be a bit verbose. Check out swagger for docs as well.

Agreed. This was really just written from my personal experience of being bummed out by never launching, then how awesome it felt to finally do it.

At Schezzle (https://schezzle.com) we use docker swarm on AWS.

The build jobs creates images that are published to ECS repositories, and there are auto scaling groups that add and remove engine hosts to and from ALB target groups for each deployed service. It makes service discovery, scaling, etc. really easy.

Definitely try swarm out if you haven't already. 1.12 was good, 1.13 is amazing (secrets, health-based VIP membership, etc).

I think that's where they would draw the line. Generally the "new things" are really new ways of doing things we're already doing, or may do in the future. It's definitely a gray line though.

I'm an engineer at a massive media and technology company. What keeps me motivated is the freedom to experiment and develop ideas on my own, outside of the iteration's expected deliverables. We have a very open culture, where engineers can spin up production servers with the click of a button, deploy things, and tear it all down without interacting with a single approval chain or ticketing system. So that's really it outside of pay... Freedom to learn and experiment on your own is a really powerful motivator for me.

There's some good stuff about this in Ben Horowitz's book "The Hard Thing About Hard Things." I definitely recommend reading it for advice on this, and many other topics.

I wrote up an article on this: https://medium.com/@jcahill84/insurmountable-documentation-s...

I've spent many many years half-completing things... I think it's a really common pattern. I recently, finally, completed something and launched it (https://schezzle.com). The trick is to just make yourself launch. Stop thinking about the business aspects, or scale, or really anything other than launching and just do it. I made a New Years resolution and held myself to it, and it feels great. Instead of watching TV or reading in the evening, pour a cup of coffee, make a TODO list, and start checking things off!

Schezzle: https://schezzle.com.

Ramen profitable, but profitable nonetheless.

On the front-end React and Redux would be excellent to learn. I'm also a big fan of EmberJS. If you don't already know Java, adding that to your toolbox could be very helpful if you ever want to end up in the enterprise world.

https://schezzle.com, which coincidentally is a side-project of mine. There are lots of other ones out there too though. During my day job we use things like splunk, cloudwatch, etc.

My first stop is almost always the thesaurus, from there I usually move on to combinations of two words or two synonyms of what I'm trying to build. My current project is a scheduled API monitoring tool, and I came up with the word "Schezzle" to represent what it is. A 90s rap influenced spin on the word "schedule." I think the trick is to find something that's easy to say and that can be communicated to other by word-of-mouth without having to spell it.