swap32

6 ms·

1.
Show HN: AgileDash – Agile Dashboard for Asana(agiledashhub.com)
1 points by swap32 8y ago|0 comments
2.
Managing sprints with Asana(agiledashhub.com)
1 points by swap32 9y ago|0 comments
3.
by swap32 9y ago
this is kind of unproductive. The job of the manager should be to push the envelope of the team as a whole. As such if he already has a high performing team, he should be as hands off as possible, focusing on other crucial areas. If not, hi
4.
by swap32 9y ago
> One thing I can suggest that has helped me on my current project, is to do a morning standup I've found that this is the only sane way that works if you're trying to manage a team of 15-20 people.
5.
by swap32 10y ago
:) I'm the founder. I understand what you mean. Really. Appreciate it. For the record, the photo is not of our office, it is of a hackathon. We don't have spanking fancy office actually. There are a lot of people I know who like o
6.
A simple assessment tool for developers(freshtalent.co)
1 points by swap32 10y ago|0 comments
7.
A simple alternate stack for Parse(racknole.com)
1 points by swap32 10y ago|0 comments
8.
Why you should finally ditch Parse right now(racknole.com)
1 points by swap32 10y ago|0 comments
9.
by swap32 10y ago
There are some excellent suggestions and workarounds here and looks like you've been using them in production for some time. Thanks for sharing.
10.
by swap32 10y ago
Please enlighten us with your professional wisdom and do point out which parts of the article are amateur.
11.
by swap32 10y ago
see my comment above - https://news.ycombinator.com/item?id=12930829
12.
by swap32 10y ago
>> do development w/o hot reload! We didn't. Please read the relevant sections again carefully.
13.
by swap32 10y ago
As I said, if it is really as obvious as you say it is, please point me to a single mention in official documentation that databases should not be containerized.
14.
by swap32 10y ago
>> Why bother to put your database inside a container if the way you ran your databases before worked just fine? For the same reason you'd bother putting anything in a container at all. The purpose of docker -as advertised by do
15.
by swap32 10y ago
>> afternoon briefing on in a meeting room and then kinda wing it on implementation I don't know where did you get that impression from. The article clearly states we ran docker in PRODUCTION for 6 months . The article wasn&#x
16.
by swap32 10y ago
>> written by your typical one trick pony, technology averse client services agency. You can be forgiven to have that perception. Sorry, but that's not true. >> They are the last to adopt new things Are you actually complai
17.
by swap32 10y ago
Well, I didn't name the reasons of why we continued using Docker because I thought they were obvious to any serious docker user. The reasons are all the promises that docker makes to you without actually telling you the complexities in
18.
by swap32 10y ago
Isn't every "figured it out ourselves" followed with the sentence describing what we figured? I see only one section where I didn't describe what we figured, which is the workflow part and I mentioned there that I would
19.
by swap32 10y ago
Yes. My bad! We really should have invested some time evaluating Kubernetes.
20.
by swap32 10y ago
>> Data written in the container is persisted to disk Even if you don't mount any folder from the disk onto the container? Are you sure? Then everything I know about containers is just wrong.
21.
by swap32 10y ago
It is fine for dev, but not for production. To quote from the link at the end of the article- "Docker is meant to be stateless. Containers have no permanent disk storage, whatever happens is ephemeral and is gone when the container st
22.
by swap32 10y ago
We didn't use orchestration across multiple physical machines so it was possible for us to get away with just docker-compose. Otherwise we would have had to go with swarm. Kubernetes is a way better choice than both compose and swarm b
23.
by swap32 10y ago
I think the article is very clear that this is about OUR experience of using docker. It is also stated right at the beginning that we have a business to run. If it going to take 2 years to integrate it into workflow (as it did for one of
24.
by swap32 10y ago
It'd be great if you can share your learnings and increase in productivity with docker AND where not to use docker.
25.
by swap32 10y ago
I can assure you, you can do all that without getting yourself into the microservices mess and docker. As you said, please get them another way. If this is a serious project with deadlines and client money at stake, as you said please do it
26.
by swap32 10y ago
Well, most of your client are bound to do this. The point is we managed to get away with only one private repo. My guess is you'd need more than one private repo very rarely.
27.
by swap32 10y ago
Because since the source code folder was not mounted on the container, we had to rebuild the image with the updated code and then restart the container. On dev machines, since the source folder is mounted, django runserver's autoreload
28.
by swap32 10y ago
I would put it this way - how much value gain are you expecting integrating docker in your processes? Is it a pressing need right now? How badly would it affect you if it doesn't work out for you? The article is the summary of our smal
29.
by swap32 10y ago
yes, that's pretty much what I meant. Our usage scope has been limited and so has been the time/resources we were willing to invest into researching fixes for things which were obvious for us before.
30.
Running Docker in production for 6 months(racknole.com)
197 points by swap32 10y ago|159 comments

More ›