1,679 karma · joined December 1, 2009
http://blog.lobberecht.com
You don't need to worry if, and only if, you assume that the standards are designed correctly and all vendors code to all the standards correctly.
As Quviq found, you should not assume either of those things.
As someone who is currently reworking their resume, I can say your suspicion is correct. If I don't know someone in or around a company I am interested in, or I don't have a target company, I expect to be treated like a random person off the street. That means submitting my resume to some email / web form; then having it parsed and stored in their applicant tracking system until HR does a search using the job description keywords. Only after a sufficiently high percentage keyword match would I expect someone from HR to begin their process with some kind of form letter email.
It's like what happened with automated phone systems and ATMs. I no longer expect a person to answer.
I don't understand why the utility companies can't convert some of their regional substations to local grid level storage locations, to counter this trend. They have the scale to utilize larger scale banks of batteries, hire people to manage them, and even exploit more dangerous technologies (like the emerging molten salt batteries).
As of 2013, the 60 and 80 kwh batteries are approximately $10k and $12k respectively. [1]
[1] http://www.teslamotors.com/blog/2013-model-s-price-increase
The people in the Clojure community have already started exploring this issue. Component [1] [2], Jig [3], and others are trying to add just enough OOP back for the reasons you mentioned.
[1] https://github.com/stuartsierra/component
Home health monitoring was the end goal of the "Intelligence Toilet" system made by Toto (Japan). I'm not sure how far they've been able to take it since 2005, but it was suppose to start with urine sugar level monitoring.
I consider it an attribute of human memory, rather than a problem. Emotionally charged memories can haunt people for decades, negatively affecting their daily lives. (PTSD is a general condition, not something only reserved for solders.)
Once people understand the malleability of memory, they can desensitize themselves, remove emotional attachments, or degrade memories entirely on purpose. (In a strange twist of fate, this effect is at the heart of many alternative medicine / pseudoscience techniques, from hypnosis-based trauma release to scientology's auditing.)
My suggestion:
1. Learn the existing CF system, with full knowledge that CF is not a "marketable skill". (Even though there are a ton of legacy systems written in CF out there.)
2. Institute the process changes (source control, bug tracking, testing, etc) yourself, just to learn them and experience the problems in implementing them.
3. Use the free time to build a complete replacement for the existing system in a currently marketable stack (Node / Javascript, Elixir, Clojure / Clojurescript, .Net, etc).
4. Socialize / network with other developers at meetups and conferences.
5. Start the CS degree (and possibly explore options for transferring).
Extra Credit: Start a side business as a web dev consultant or, even better, a product. The education market is full of niches that can be better filled, and you have a front row seat.
http://en.wikipedia.org/wiki/Clinical_trial#Phases
It might also be good to remember some of the history around why this structure is in place.
The Battle to Beat Polio: http://youtu.be/qMRgQhbSyqs?t=18m50s
1. Fixating on platform stability over project evolution
2. Ignoring the community on project direction
3. Preserving public image over project committers
4. Being a total square
NOTE: I am against the fork.
I'm curious what you mean by this. Is your definition of a DSL based on the language's syntax, or on the language's paradigm? Clojure's core.logic [1] provides logic programming, as apposed to functional programming, but maintains the syntax of a LISP.
I personally can't work deeply in more than about 4 languages at once. This might be my memory, my experience level, or it could be a human limit, like the short-term memory 7±2 limit.
For me, Yes. The core of the issue is that the sequence of pitches is not meaningful on its own, like all communication. When I am listening to music, assuming a human made it, I explore and project meaning, emotion, and thought on to it as if expecting it to communicate something that would complete my mental model of the artist or environment. All in an effort to feel what the music was conveying.
If I find out it was just auto generated, I feel like a fool looking for meaning in tea leaves.
RoR was propelled forward by businesses trying "new" technologies in the hopes that it would pay off in faster / cheaper software development. While RoR is not getting any less useful, the 5 year hype cycle of web dev has made SPAs and Node.js the new technology stack to experiment with.
My suggestion is to either secure traditional employment in the RoR stack, or move to the JS and Node.js stack. The former will give you a few extra years, while the latter will allow you to continue with the remote work you have grown accustom too.
Interesting quote, but I think it unfairly judges people who are not "like you". Discussing people, like celebrities, is like discussing the weather. It's a lowest common denominator that you fall back to when you have difficulty connecting or communicating with another person.
It's better to think of ideas, events, people, and weather as a way to measure the quality of connection and communication you are having with someone. (You can also start a conversation with a "bottom up" strategy by starting with weather, or people, and working your way up.)
IANAL: Last I heard, the logic was that you, the owner, are not accused of anything. Your property is accused of being used in a criminal act. Your property is guilty until proven innocent, because it is not a person protected by the bill of rights.
The idea was to seize the assets of organized crime without having to completely prove they were committing a crime (which is hard). The road to hell is paved with good intentions. (Also, if your plan is to use the bill of rights against a prosecutor, you need a better plan.)
I wonder if using Facebook over Tor would help in that regard.
https://www.facebook.com/notes/protect-the-graph/making-conn...
Home LED lights and better electronics efficiency might make a dent on total grid usage eventually, but it really feels like it's only scratching at the surface.
That is not true any more. There was a discussion [1] two months ago about the changes in the law regarding property seizure post 9/11. They call it "asset forfeiture".
Software development is built on layers of abstraction that directly allow one human to frame a 2-story house, while typing very little. The amount of actual machine code generated by a simple CRUD application can be massive. Optimizing the raw typing is only useful when you have no control over the deeper abstractions (like if you are stuck with C++).
Popularity is always a problematic metric for platform evaluation, because the programming community generally has a very short attention span. I would attribute the lack of marketing to the previous license fight, work towards platform stability of version 2.x, and work on the upcoming version 3.0.
> a polygot application framework sounds like the ideal way to use the right tool for the job.
Vert.x is not completely polyglot. It supports many languages, but they all must compile to JVM byte code to work within the platform's event-loop/thread-pool management. So, the Javascript must run on Rhino or Nashorn, the Ruby must run in JRuby, the Python must run in Jython, etc.
[1] http://criu.org/
The training industry has been around for a long time. I would suspect there is years, perhaps decades, worth of data, just not under the name "bootcamp".
That being said, I still think there is a valid business in training developers who want to change "stacks" (i.e. Embedded dev jumping into web dev, C# dev jumping into Erlang). The stacks, and ecosystems, are just complex enough to require allocating a lot of free time to becoming proficient and employable. Not everyone is an autodidact. (Perhaps, this is also the solution to the old "developers burn out at 35" axiom.)
That reminds me of the old QA technique / tactic of only telling the developers where a bug was found. Sometimes you don't even have to find an issue, you can just pick a complicated module.
Real success is extremely hard to quantify, which is why i'm not suggesting that as the goal. The goal is to grade spam messages, and encourage people to not repeat known spam patterns. (And, if you show the score to the recipients, it also acts as a spam filter.)
Encouraging / forcing people to write less spammy messages might improve the overall message quality, just by increasing the cost, in effort and time, of sending the messages. It also provides some minimum level of feedback to the people who get zero responses from their messages.
Sounds a bit like how Microsoft was structured [1].
[1] http://www.globalnerdy.com/wordpress/wp-content/uploads/2011...