VEry good answer, thank you. So in my scenario, I was thinking of packaging our service apps (which run on JVM) and if I make sure that the OS has jvm and all the needed stuff ready. Shipping a package and deploying the service, is just transferring the Docker container and run it. Which happens to be using the same process models as the OS itself. So in other terms, Docker is a convenience layer (a glorified FS abstraction). I am not saying this to undermine the utility, just trying to figure out if it solves more problems then the complexity it brings (which is one more moving part in your toolchain)
HN user
apphrase
Apphrase
Can anyone please tell about the overhead of Docker, compared to no-container scenario (not against a fat vm scenario)? I am a "dev" not "ops", but we might make use of Docker in our rapidly growing service oriented backend... Thanks
Lack of single key Home/End and forward delete etc. All are somewhat possible with the Fn key, but that makes crazy combos and go to start/end of line also is a pain...
Check Paymill. They have a pretty good integration and are one of the strongest players in the market. They claim that they support Turkey too, but since I am located somewhere else I cannot check that. Otherwise they are cool Good luck
The framework choice is not an independent evaluation, you have to take into consideration the accumulated experience level of prospective engineers you can grab within your reach. That's why actually all of the mentioned frameworks will be alive and going. It is increasingly hard to go exotic, if you are thinking of growth and agility. Otherwise you can paint yourself into a corner where recruitment is impossible and a big rewrite is inevitable.
It is very unlikely that the next Instagram would be using Parse
This is one article that is going to be referenced for years to come. I like the snowball-effect traction of 'how to deploy an X app on Heroku'.
Perfect post about one of the most important principles in programming. Nine out of ten, concise design with fewer lines of code is better design than over-engineered abstractions over abstractions over abstractions over...
Work on developing solid technical skills. This is necessary condition but not sufficient. So, when the time comes, you can take responsibility and people will notice that you are good. If you can combine this with good personality, social skills and integrity, then you will definitely be appreciated. Almost always there will be some smart people around to notice you. And after enough time doing this, you will be the one who appreciate other people's efforts as well. Avoid empty politics at all costs, but own your work and present your value in a decent way. Don't wait silently, show your contribution, but don't overdo it. Job security is an illusion, don't go after it. You will probably receive fair compensation eventually. Focus on the things you can do passionately, and then happiness will follow. If you don't enjoy what you do or the people around you, you cannot force yourself to do it for long anyways, so change your position until it feels right. No-one can tell you when and where, but you'll notice it when you have it
I cannot believe how subjective it can get to discuss about such issues. You can discuss about the DO's and DONT's of programming with a fellow programmer for hours, and then he goes on his life and keeps writing infinite number of abstractions with little to no real benefit. Especially a common disease in Java world.
Writing clean and minimal code is hard, really hard... Great article
Whenever the question is 'how do i ...' followed by insane amount of something, the right answer is usually; 'Don't'
Are you sure you want to have that many things in the same view, coz human attention is limited as well as his perception of movement and reading speed...
I wonder if this can turn into a payment gateway solution for SaaS startups. Gumroad has a pretty decent track record of functional yet pretty(as in not boring) payment pages... Interesting update
version two disease
Tools and community are the key, the rest can be argued for days or months or years with no real winner nor real value to it...
have had some great experiences with resin back in the day... great product indeed. Kudos to the team
Unfortunately we are still in beta, but this is exactly the problem we are tackling. Hopefully within a couple of months we will be helping you or similar people. In the meantime, I agree about the good comment below about advertising. And also you should be pushing it to friends and family first. Although a language barrier seems to be an obstacle, I am sure you can find at least a couple of friends to use/recommend your app. We think of it as a tree, first branching is hard but possible, the rest is just growing the tree. Advertising as well as active participation is key here. Needless to say, good quality product/service is essential too. All the best with your endeavour
SaaS model all-in-one marketing toolset service for bootstrapping apps. The current ones are either to much data analytics, or too dumb mail-list management tools.
i liked the 'YOU ARE MARRIED TO YOUR CO-FOUNDER' part. You might as well marry him/her as in our case...