219 karma · joined January 20, 2013
http://en.wikipedia.org/wiki/Evolution_strategy
Video of the evolution:
If the war isn't over, then when will it be over? And is it even legitimate? The U.S. declared war on the concept "Terrorism" during Bush Jr's presidency, not on specific terrorists or al-Qa'ida. The U.S. also declared a war on "drugs" during the Reagan years. Though I'm in support of both "wars" because I'm in favor of the well-being and defense of the U.S. people, I don't think Congress or the president should have a right to declare war on something that cannot end, i.e. cannot terminate via treaty, surrender/capitulation, complete destruction, or victory.
I am a little concerned that we are declaring that it is ok to kill our own citizens without due trial, although I understand there are conditions.
It isn't "allergic to conditionals". It just drives the logic elsewhere to keep the presentation layer looking as clean as possible to the developer so that you can either focus on the view (template) or the controller or model.
Sales is much easier than tech/web development to do remotely because you can use commission and/or sales targets to quantify how well the remote salespeople are doing. Don't use a single salesperson as a "test" though; abilities vary so much, you'd have to have a larger sample to determines how well remote will work for your company specifically. Also, internet connections can go down at home, so if you have limited sales staff and depend on them to be selling everyday constantly, you might invest in a secondary method to connect to the internet or make sure they have a backup plan like working from a cafe.
I've been using Angular for months now and although I already knew what dependency injection was, I didn't have to understand the term to use Angular.
> Additionally, Ember is fully unit tested.
Not to start a flame war, but I'm not sure this is a plus. Full unit coverage is nice for confidence, but can be balls and chains when it comes time to make changes. Just as an example, Rails is not fully unit tested by any stretch of the imagination.
<ul>
<li ng-repeat="name in names">{{name}}</li>
<li ng-show="!names.length">There are no names in the list</li>
</ul>Carlos and Santiago are active Rails 4 core team members, and Steve K. has risen among the core team ranks as well (not to leave the others out).
I personally like AngularJS a lot, but I also like Rails. Rails 4 has a rails-api project along side of it, which makes it seem like they are starting to spend more time thinking of Rails as provider for a Javascript front-end. Because of Yahuda's involvement, they have also placed more bets on Ember than Angular the last few years.
I think that Angular secretly hides an affinity for backing services in Node, and this concerns me a little. I think their team needs to either provide examples and support for each major front-end framework and not just rely on volunteers to provide those examples that won't be maintained as Angular changes. Or at least be crystal clear about what is expected of a service so that as little code is required as possible on the Angular end to integrate with it. And the same goes for Ember. What good is a front-end MVC framework that depends on services to exist if you have to spend any time guessing what to use on the service-side?
If they had focused on "Be Good", perhaps they would have fully instituted good service from the beginning and embraced personal customer contact.
I've been to Sweden and stayed with a family there and got the impression that they are mostly an intelligent and compassionate people that tend to think alike. However the drive that set the U.S. apart (back then at least) was for innovation, business, and capitalism, while the Scandinavian/Nordics were making furniture and high quality items without really caring about making a lot of money from mass production, so their GDP was much lower.
To say now that they are well-governed because the U.S. is starting to suck economically based on biased stats? Worthless info, imo.
"...most of our remote developers work longer hours than our in-office devs. It’s not required, and probably won’t always be the case, but when going to work is as simple as walking upstairs (pants optional, but recommended) people just tend to put in more hours and work more productively."
From personal experience, what happens is that the remote worker went downstairs to play with the kids and pets or watch something on T.V. that someone else was watching while they had a snack. Then they work 30 min more later to make up for it. It isn't working more- it is spreading out the work.
Also the post mentions that a self motivated, proactive worker is more likely to do well remotely. But, that depends. Micromanagement of remote workers is really bad, but so is just saying that they have to figure out what to do on their own if that is not their personality/work type. I personally work better when it is clear enough what needs to be done, and maybe if it is something I'm unfamiliar with, then a lot more information about the internals and business requirements and logic is provided, but I'm not told how to implement it. That is true whether I'm remote or not. But each person has their own way of doing things, and usually those aren't evident or may be misunderstood in an interview, so I don't think you can just say "they need to be proactive and self-motivated" and somehow some mystical force draws the right people to work on your team.
I think recruiters are a decent way to find some of the jobs that aren't found via indeed.com alerts, fog creek's careers 2.0, top*jobs.com, dice (nasty), execunet, HN, etc.
But on the bad side:
Once you are on the list, they will look up your work number and call you if you just put your employer's name on your resume. The only way to get them not to do this is to remove employer names from linkedin.com experience, which you shouldn't do, so it is inevitable. They will not pay attention to requests not to do this.
They equate pay rate without benefits for short-term contract to salary rate full-time with lots of benefits. If you decide to give them pay rate expectation (not always a good idea), give them both your salary expectation and a much higher contract rate that assumes a 3-6 month contract- divide your annual salary expectation by 1000 and that is your per hour, in general.
Why they are what they are:
Average larger sized recruiting companies take almost anymore to get on the phones, and those companies burn them up and move to the next, so it isn't the actual person's fault in many cases. They are given visions of dollar signs when hired and see us like an untapped oil field, and they don't know what they are doing. They want to make the "sale", so they are going to fudge it, and when they later feel used and like the scum of the earth because they got stepped on by us, they quit and someone takes their place. The ones that can justify running through us like we are numbers to be manipulated stay, so it is natural evolution that is not in our best interest.
Advice for those really serious about using a recruiter:
Don't treat them like scum and spend the time with them, even though it might take 10x or more of your time. Let them take you to free lunches and breakfasts. Don't lie to them, but don't tell them everything. They will remember and appreciate the love and will at least maybe write good notes on you and keep you on the hot list so when something comes up, they might call you first.
What I do:
I am an introvert, so I push all conversation to email that I can and don't take calls, ever, until there is an opp I'm interested in that I know is in the right salary range, right location (not just city), and right job description. They still email positions that don't match all the time, but I don't like the idea of lunches, etc. with someone I don't know about positions I might never want.
There is plenty to security that is not in the Rails documentation, though, and it is by no means bulletproof by any stretch of the imagination. If you don't take security seriously, then you increase the chance of getting stung. From exploits that you have to watch out for in your code, to setting up the server(s) and infrastructure in the most secure way that makes sense, it is a lot of work.
Justice will not be served.
Vim plugin. No refactoring available yet: http://go-lang.cat-v.org/text-editors/vim/
Eclipse plugin. No refactoring available yet: http://code.google.com/p/goclipse/
Others (afaik- no refactoring available yet): http://go-lang.cat-v.org/text-editors/
Also, freedom from incompatible work environments would be nice. It is way too noisy where I work. At the very least they should provide nice ($300-400) noise cancellation headphones without me having to beg.
I know a lot of companies do this. Heck, even ID software provided free source of their engines, but didn't give away their WADs. But is the PhP in this case of any value without the rest? Can anything be done with it?
If the PhP is of no value on its own and it specific to the CSS, JS, and images, then imo that totally would violate the spirit of GPL'ing the other. If that is the case and you want to have it be proprietary, don't provide the source/files for any of it (for the new stuff). If you want it to be GPL, then sell it, but make all of it free source, including the images, JS, and CSS. Note: I believe that Stallman's view (if you care) is that not providing images is ok if it is art and not source/required for the source, but I think that is a loophole that can be exploited, so I say make it all free.
However, if the PhP provides some value on its own and is usable (like one of ID's engines), it's all good and do what you want.
There is nothing in GPL that says that you can't get paid for it. Just because you have to provide the source for free doesn't mean people can't pay you for the work, it just means they can't pay you for the source. They could pay you for the bundle (which they could create on their own if they wanted for free, but some may not be savvy enough to do that). GPL is not anti-capitalist.
Would it allow me to connect a USB keyboard (for example) or a USB mouse to my phone? How about a USB webcam that requires an additional linux driver to be installed? How could that be installed easily by the user? How about connecting a printer via USB? Will I be able to print from my HTML5 app? If not, what will it support? I'd also like to be able to find devices and printers via wifi and print, scan, etc. Will I be able to do that?
I think if the goal were to make mobile devices as capable as we should all expect but have been conditioned NOT to expect, then that would be an OS that could compete. Otherwise, it is just a slower UI with fewer applications.