jafaku

What does that even mean?

Once you have figured all out, it doesn't stand in your way at all, I really like developing with it.

Personally, I use aliases for almost all of its commands. I have also created various scripts for automating things like configuring the SSH connection to the container, etc.

Another thing you have to figure out is how to edit the code. My choice was to use a volume (only in dev), and download the code into a different directory inside the container. Then on the first run, an init script inside the container will clean the volume and move the code.

It has been some painful months and I haven't even finished. I'm liking where I'm going and I'm almost there, but if I had known the work it would take I think I would have avoided it. But if you are a team it's definitely worth it. Devs can now install anything they want without asking the Ops people for permission (as you can imagine by this statement, I'm more a dev/devops than an ops guy).

Oh one thing that does make it awesome though is its combination with Jenkins, if you are into continuous delivery. With those two, you can easily test all kinds of environments in the same machine without wasting resources, and thanks to Docker's cache it doesn't have to reinstall everything every time, it's really fast.

Dammit, you are a few months late. I learnt all the things you posted the hard way, and I agree on everything.

What happened there?

What's that? I don't get it.

Yeah our culture is the best! Everyone else is wrong!

I wouldn't mind writing unclean code if I weren't the one who's going to have to maintain it and add new features to it in the near future or the years to come.

> Also be careful with which registrar you check for availability as if you don't buy immediately you may find the domain on their premium list the next day at an inflated price.

I have always been scared of that kind of thing, though in the end it never happened to me. So it is a thing then?

I don't think sharing the image is necessary during development. I just add the Dockerfile to the repository and each dev builds their own image. If they are methodical they can pull the repo and rebuild the image at the beginning of their work day. Most times it will be rebuilt in a second because there have been no changes. If they don't rebuild the image, it will be the main suspect as soon as something breaks anyway, so I can't see this causing much trouble.

Jesus who?

> As someone who's been working on cryptocurrencies

Do you realize you are talking to a Bitcoin core dev? lol...

What problem?

Oh wow, I didn't realize others had already done this, let alone make comics about it. But yeah it's like in that comic.

I did something similar for a couple years, I used to sleep 8-10 hours but only 6 times a week. People kept telling me that my rotating hours were bad for my body, but I was in perfect shape, ate well, exercised, etc. Eventually I came back to "normal" because of certain obligations and human interactions, but I think I'll return to my rotating hours once I'm done with that.

Nothing, we are all being downvoted. I guess it's the usual Bitcoin haters.

Mac only? Why?

Seems like Bitcoin haters have reached HN too. All the comments being downvoted for no reason.

The problem with that is that the app on your device is usually developed by the same entity, meaning they could take your key and steal your coins.

What we need is to decouple the online service from the app on your device. Maybe someone could develop a secure app with a nice API or protocol that users can securely connect to 3rd party services without fearing that the key in their device could be stolen.

Damn, Javascript is only becoming messier. I think I'll just watch it from the distance and wait until someone figures out the best way to deal with it.

Really? I'm supposed to go and work for free for them, just to prove your wrong? No thanks.

> Also their tests are run without caching for a reason. It's not a test of the language/framework if they just use whatever language to generate a static/cached file and serve it with nginx.

Haha lol, so the tests are explicitly meaningless. I guess I'm done here then.

Unlimited private repositories for free, yes.

That's great, thanks. I'm sharing it now.

What the heck is an octobox? Do you really want a git tutorial to use github-specific terms like that?

> I dispute that there is any good software written in Perl.

Do you even Linux? Have you ever installed anything? If you pay attention you will notice that lots of the libraries you are using for everything are written in Perl.

That makes no sense whatsoever. Symfony2 is fast as hell. If you don't think so, you simply don't know how to properly configure it for production. There isn't much real speed you can gain from using weird things like Phalcon, unless you don't know the first thing about caching. In fact, not having all the caching mechanisms that Symfony2 gives you will probably slow down your application, even if your code is written in C.

You really think those guys know how to configure for production a hundred frameworks? If you base your decisions on those benchmarks, you are gonna have a bad time.

CI is a badly designed and outdated framework. For real speed you should use something more professional like Symfony2.

Symfony can be overwhelming for a newbie, but that's because web development is becoming a bigger field every day. There is so much to learn, and Symfony will teach you all kinds of best practices and other things that are not framework-specific at all. To learn Symfony is to learn web development done right.

Laravel is basically a wrapper around Symfony, to make it simpler and easier. A newbie might prefer to use that, but at some point after feeling comfortable with the basics like MVC, ORM, etc. you will definitely want to move to the more professional Symfony.

> Many have been where you are now, and then moved on to other languages to never ever look back. From what I've seen, the reverse is much less common.

I really doubt that. In my experience there haven't been a single time when someone attacking PHP actually knew something about it that wasn't outdated by at least 5 years.

It's funny how difficult it is for people like you to grasp that the language and its ecosystem evolves every day, much faster than other languages. Just look at what you just said. How can someone have been where I am right now? They used a time machine? Or you are assuming that the language stopped evolving at some point, or never evolved at all in the first place?

Well? What do you do?