Walkman

You just start doing, that's it. Don't overthink just start it NOW! No work is perfect, you have to release it and let people judge so you can improve or abandon but if you release nothing, you will never know.

You have to decide which is more important FOR YOU. If you choose money, you can do things with it in other areas your life which makes you happy/satisfies you. If you choose a job with better management, technology, etc, you will be happy in your job.

I choose the better job (better people), because that's what I spend most of my day and everyday frustration doesn't worth it FOR ME.

The whole idea of Docker is to make it possible to better saturate single machines. How is that not more energy efficient than solutions before Docker?

Thanks!

I predicted this last year: https://twitter.com/kissgyorgy/status/783825879348744192

That's very nice to hear! I prefer this "make it great and release when it's perfect" attitude because it means way better quality and care I can rely on for the long term. Thanks for making Caddy, I'm pretty sure I will use it at one point!

I don't know how everybody feels about this but I really like to control my whole environment from the OS to what servers I use, how I secure them, what kernel features do I allow what packages do I install and how I protect my services. If something goes wrong, I fix it. If something goes wrong with CodeStart you wait for Amazon to fixit. I don't like giving up control.

That's nowhere near 90% of Python. It's strange because everyone thinks Python is an easy language to learn, but that's not True at all. It's easy to pick up and be productive with it in a very short time, yes, but the interpreter has so much going on you can't learn everything in years. If you happen to learn everything about protocols, the interpreter gotchas, there is the standard library which is also huge, and if you got everything in it, there is the ecosystem, which is so large nobody can know about every package. And I did not talked about the whole new world of Python3, asyncio and the whole old world of Twisted.

OneNote webapp on Linux

I do. with very similar configuration to production

Yes please!! So painful. I also have dozens of applications open, all the time, which I lose when I dock/undock when in sleep...

The reason I'm way more productive with multiple monitors* is not that I open twitter and want to look at it constantly, but because I open my code from different angles like: - comparing two pieces of code - opening code review and opening actual code in text editor on the other - opening a text editor for commit and looking at the diff on the other - open the documentation and look at the code on the other So I'm way faster at switching things or way better to compare things this way.

I tried i3m today (the tiling window manager) but I realized it not gonna fit my workflow because I can't have 10 windows open and look at just two-three at once because you either maximize and then you can look at only one thing at a time or see 10 tiny windows at once.

* Having one big enough monitor with huge resolution is the same, but one with simply HD resolution is not enough for me.

"The modularized monolith can be scaled horizontally as well, but you scale out all modules together."

That's not exactly true. Yes you probably have to ship the whole monolith, but who said that you also have to get traffic for all the parts? For example you have /users/ and /books/. You can configure your nodes to only serve /users/ and configure different (maybe more) nodes to serve /books/. The code sits there but who cares?

That's actually a very good counter-argument against mine.

Ok the tone of my message might be out of line a little bit, but I find it important to make people aware of incorrect usage of principles/tools/framework/stuff. I would not have so much problem with this project if they would call it "API" instead of "REST API", because it would communicate the purpose much clearer.

Also it would be a huge design mistake to use this on any serious project and probably not everybody will realize this.

Nice project. A little pun: if the author intended to follow the naming scheme of spacemacs project he or she should name this spacvim :D

The problem is not with developers or tech savvy people. Everyome will know about this by then and solutions will be applied. The problem is with end users, who will only realize this after the shit hits the fan and their fridge will go crazy or there will be a car crash.

Last week I made a comparison matrix against Badssl.com for different Crypto libs on OS X: https://gist.github.com/kissgyorgy/54601c883891991f28e49ac1b...

This is just perfect! So simple, so fast and can even sync to a Gist. Great job! I was looking for something like this for a long time.

There are practices which can ease the use of feature flags. E.g.

- Only a handful feature flags at a time.

- When the feature is stable, delete from everywhere!

- Easily turn on and off.

- No branching makes it much easier.

This is the last time I spam a Keybase thread with invite codes :)

https://keybase.io/inv/6953921e2f

https://keybase.io/inv/637bfd5d42

https://keybase.io/inv/20be67f672

Seems like very basic mistakes were made, not at the event but way long before. If you don't test to restore your backups, you don't have a backup. How does it go unnoticed that S3 backups don't work for so long?

I hope awesome-list owners all agree with a master topic and each of them will use that!

Don't call it "s", because then you break consistency basically with the whole Python ecosystem. That's not very nice for fellow programmers who already used to read and understand "self".

One can make very interesting conclusions based on purely this. Examples:

- Python developers does not follow Clean Code (ala Uncle Bob) as much as Ruby , because if statement is more frequent than def and return.

- Ruby makes it possible to write in a much more functional style than Python. OR Ruby developers like to develop more in a functional style than Python developers.

- People don't really care about good variable names ("a" is a terrible variable name in scripting languages like JS and Python, still top 11)

- PHP developers might practice "return early" in functions (more return than function keywords) OR their functions just do too much :)

When you have a strong static type system like Go has, you don't need descriptive names that much, because even single letter variable names are evident, because the declarations are there, close to the variable names. It needs a bit of getting used to if you only programmed dynamic or scripting languages.

docker-toolbox you are talking about. The new version (Docker for Mac) with this problem doesn't use a VM anymore, but native virtualization on OS X. The old version doesn't have this problem.

And for a developer who uses Linux desktop for development every day, this is a no-go.