I would imagine that in certain niches or scenarios that minimum wage can cause harm. The exception is not the rule though. The overall good it does should exceed all of the bad. Where there can be exceptions made to move towards the best of both worlds care needs to be taken.

Egyptians did it already.

Honestly PHP has been pretty good for security if you use the proper manual and actually read it properly. It has a lot of pitfalls but most are detailed in the manual. Unfortunately few people really RTFM or care *how* what they are doing works too much as opposed to that it works. In any language that's a problem.

I've been teaching people about this for ages. I have reviewed perhaps a couple hundred recruitment tests as well. You would be shocked how many can't even indent and you see injections all the time. I sometimes perfect to see manual escaping using the provided functions than prepared queries because prepared hides the problem. I am pretty sure a lot of them use tutorials as they are doing the test and it makes me wonder.

When I am training juniors one of the first thing I get them to do is to learn to go straight to the authoritive manual and ignore the top results. I explain to them how SEO works and that these people are making money sometimes practically plagiarising the manual and then using SEO to get their ad laden version to the top. Originally it came from having for some languages bad manuals or really thick specifications (W3C never wrote decent manuals). They get a bit of traction being one site for multiple languages as well.

It's not just tutorials but also questions (common error messages, problems, etc). Stack overflow has done a really good job of cleaning things up. I still see junk in there rarely but you can at least add your piece. One of the worst cases I saw was when I searched for best MySQL practices and found a guide with some questionable things or poor explanations. The result of that is that I had one developer adding LIMIT 1 to the end of a hundred queries entirely needlessly. This practice added noise to code and led to obscuring possible errors (where if you don't get zero or one result the query is broken). It was never added in the kind of situation you would actually want to limit by one such as with an order by to get the top result. These practices are useless if someone doesn't actually understand what is going on and if they understand that it should be immediately obvious when and when not to limit. That was one of many dodgy things in there. I think the worst has to be where if you downloaded something precompiled for a certain platform you would get an error message about having the wrong library version (dynamic linker error). The guide explained how to hex edit it to look for a different version. Asides from the potential issues this can cause with compatibility and segfaults (security as well), the software was open source so could have been downloaded and recompiled.

Pretty sure it's IRC :D

I like Soldier.

My favorite of his was Kin Dza Dza. I can't for the life of me remember why or any part of the movie though.

Ideocracy

I'm still waiting for someone to release box. It's in Star Cops.

I tend to agree. It's just a case mod and maybe something special for the controller or even if it supports carts which I doubt. I used to use emulators a lot a decade ago. Last time I calculated something like if you pay three or four times more than they charge for a console and a few dozen games then you get a system that can be used as a not entirely bad PC, plus that can emulate a bunch of systems and that can store hundreds of thousands of ROMs in total (most systems are thousands of ROMs to tens of thousands, for tape based they are tiny and you have tens of thousands). The way they sell these things at the moment just isn't good enough. People want access to everything and essentially something like eat all you can.

I like things that are mainstream and more obscure. None of those attributes tend to factor in though. It depends on the problem. Saying that I occasional have a bias in selection for mainstream which is justifiable. Mainstream in Open Source means more tried and tested, more contribution, more community support and a larger talent pool to hire from. It's not always good. Some things get massive contribution, even too much that quality goes out the window and you have a maintenance nightmare. On the whole though, mainstream tends to be alright.

"The whole Mir hate-fest boggled my mind - it's free software that does something invisible really well."

Actually I got really annoyed at this. Not specifically at Mir. At the whole there's always two things to choose from. Wayland/Mir, Systemd/Upstart, MySQL/MariaDB, oi.js/node.js, Electron/nsjw, etc. Choices are always annoying. Node.js managed to fix things. For a lot of things I find myself avoiding being an early adopter and wait to see how those things work out first to see if they merge or there can only be one.

There are two things I really hate. Bandwagoning and the unique/superior obscure tool obsession. You often see spikes in tech use due to bandwagoning that then drops as the language turns out to be too much trouble but then you still have the lingering stench of it because of a bunch of legacy products that used it. Bandwagoning can be linked to the other thing. Often someone will want to learn an obscure and often over complicated language so to not have competition and because they believe a theoretically superior (perhaps potentially than actually materialised) tool will offer them that. It will make them special or something. This can happen with new tools but ironically everyone has the same inclination so you get a burst of them. Then when they all realise that actually this boat is quite crowded they all bugger off to go master a variety of other obscure languages like Haskell, Erlang, Prolog, Lisp, Ada, R, etc. All of them though secretly dream their language will suddenly become famous and that they'll be the master in it or at the forefront. I just stick with what works well for the problem rather than some new fangled technology then adopt something when it becomes mature enough and suits the problem well. If language A is the traditional choice for domain A, then language B comes out claiming to suit domain A better, I can't really know that without a point of reference, such as language A, except when language A has been used in domain A a million times but language B ten times then I know that language A is a pretty safe bet. Don't get roped into being a guinea pig more than is necessary or that you really have the time for.

I come from a background of hating Agile and in particular Scrum. After looking into it however I came to understand that the structure and concepts are purposeful. I don't believe it's appropriate for all scenarios or problem free but the structure does make sense for a number of scenarios if applied correctly. I do not really believe in a strict form, or at least it should be fairly strict but tailored to specific needs.

What I have noticed is that a lot of people banging on about it don't actually seem to get it. Even some of the books go into la la land turning what are meant to be principles about how a team should operate into something like a game of the sims and the personality traits you should hire for. I don't like that it tends to contain developers, in fact all of your actual productive staff. There's no career progression in Agile if you want to remain technical.

I take time off sometimes even though I am in the same situation above.

There's always the hit by a bus scenario.

Then simulate it. The less time you take off the more critical your presence is.

I find that the best way to have people able to cover for me is to have them cover for me. Rule by neglect.

By staying present all the time all you are really doing is depriving anyone the opportunity to fill your shoes.

Whether you like Trump or not, Trump has been in office for how long?

The spam filter as well that acts like a localised shadow ban and sometimes fires on things that aren't spam.