Saw this posted by Mikko earlier. It's an interesting ploy, and I'm interested to see what comes of it. Specifically, I want to know whether the media, as it were, is going to be willing to propagate this sort of story, even with the plan being relatively well-known at this point.
Of course, this could be a long play. "Leak" this plan, build confidence that the media isn't going to propagate false stories, and then when a similar plan is effected, people are potentially more likely to take this manner of news seriously.
While that's a fair statement, an OS--mobile or otherwise--doesn't really need to be among the top few in terms of adoption to be valuable. Lots of people still use their N900 and N9 phones and want something to be a successor to them. This is likely the way I'll be going next.
It's an interesting (read: niche) market, to be sure. It's the same market as someone who might buy 8 raspberry pi boards, or 4 ODroid U2 machines for the purpose of learning about parallel computation.
The Epipchany chip (the coprocessor on these boards) is supported as of GCC 4.8, so we also may see some novel ways to offload work to this chip in the future.
Perl is my first interpreted language. It has a very special place in my heart, even if it was awkward at first to get used to it coming from a C background. Perl will always be a cool kid.
I think it's interesting when people tie sentiment to coding choices. As previously stated, I could never wrap my head around the horrid syntax and the feeling that if you didn't know it from the beginning it was going to be a long, hard trek in doing so.
As for 'cool' I'm not so sure. Perl will be a niche sandbox for quite a while, but most run-ins with Perl (as of late) have been trying to remove it for something else. I think choosing a more accepted language has legs for a variety of reasons including code portability and long-term maintainability, both stemming from the fact that if there's only one guy maintaining all of the Perl code then that's a very-bad-thing.
But, that's just me. To wax nostalgic on Perl and use that as a basis for use-case seems, at least somewhat, reckless.
>May be a better way is to create a nice atmosphere where women feel welcome and comfortable, having very strict code of conduct in conference and generally us (male engineers) being nice to them - this might take time, but the changes would stay.
I agree wholeheartedly! I think that this is the sort of attitude which would be conducive to moving the state of affairs along. In these fights it's often lost that the problem at hand is that treating people in a way that makes them feel like they're not welcome and not respected is at the root of the issue.
Is this a limitation of Widgets, or of the status of Widget development, though? It seems to me that there's a LOT of untapped potential when it comes to widgets.
Anecdotal data, admittedly not perfectly analogous.
I got serious about playing the game of go relatively late in life for a go player--I was 23 years old at the time. In 2 years of hard study (1~2h/day, and a bit more on weekends) I rose from essentially a complete beginner to dan level play. Since then, life has pulled me away from playing go as actively, but the work I do at this point does let me maintain my level of play.
I think it's fair to say that you get MORE out of your effort at a younger age, but at the same time, I think that if you're serious about learning and honest about the way you learn, you can absolutely get a LOT out of those hours--and that ultimately, you can get the same utility as you would have, by tailoring your studies to the way you learn more effectively.
...Which they ought to do. Offering the ability to enumerate user accounts is unlikely to be the immediate goal of this utility, but it's an effect nonetheless.
A good portfolio can be created well before one goes into--let alone graduates--college. I understand the graphic design industry to be largely portfolio-driven, and it continues to confuse me that the IT industry isn't the same way.
Things are starting to shift. More and more employers are looking to see code repo's prior to even looking at your CV in detail.
On our blog we do a series of interviews called Hacker Jobs Meets... where we pose ten questions to CTO's, Tech Directors and start up founders across the UK and almost all place a significant amount of emphasis on the importance of having visible code prior to an interview.
I'm starting to wonder if you're actually being serious.
The vast majority of employers (at least the better ones) like to review developers github/bitbucket repo's in advance. Everything in there is open-source.
Your master and servants act has literally zero relevance to my point.
Yes I am being deadly serious In the UK if its at all related to your work - your employer owns your work if its at all "related" even if you do it outside work on your own equipment.
This is direct from a very senior hr/ir Guy (our GC at the time) when we where discussing the implications of this for a colleague who had come up with some advanced algos for improving big iron systems - IBM used to get him in to consult for them as he was a Mainframe rockstar
And you don't know much about UK and US employment laws as most of it descends from the original M&S act as both countrys share the same roots for their legal systems.
