1,679 karma · joined December 1, 2009
http://blog.lobberecht.com
It is phased down to 90% by 2020, and, in its current form, doesn't fall below that. The phasing just starts in 2014.
You are joining a pop culture that measures, judges, and hires people by how much they know about the current pop culture. Worse yet, everyone who tries to escape this conformity appears to just switch to a different conformity (OOP programmers switching to FP. Emacs users switching to SublimeText. Javascript people switching to Go. Programmers switching to Entrepreneurism. Etc.).
- Choose what not to learn (while being outwardly supportive of endless learning).
- Learn your excuse list for not understanding things now, and sit quietly while energetic people try to "convert" you.
- Choose what you actually want. (Many people are successful in unseen ways, and you never hear about them.)
- Know that you won't get it right the first time, but you will develop a feel for what to pay attention to after a few times around the hype cycle.
And, as always, keep learning.
> So in more than half the states people making just above a certain threshold get essentially free healthcare, while people making below it get nothing. In these states ACA has done almost nothing to help the very poorest.
The ACA, by itself, has done everything it could have to help the poorest, within the options that would actually pass the US congress (2009-2010). The Supreme Court said the ACA could not force the states to take the (federally funded) Medicaid expansion, so the state governments used that choice as a political party loyalty test. The state governments chose to refuse preallocated federal money, to help the poor, to show their loyalty for the next election cycle.
I too would have preferred a single payer system, but the ACA is what passed and the state governments have made their choice.
Perhaps another type of communication, other than issues, PRs, and comments, is needed just for bots. I would tolerate my projects being scanned, if I could separate the human and bot communication streams. (And, block bots when they don't work as expected.)
Nope. I remember specifically copying from known solutions in large organized reams of marked paper (a "book" we called it). They used to have whole rooms, and personnel, dedicated to storing them. Now, you couldn't just ask for what you wanted, like "clojurescript core.async examples". Oh, no. Research required either knowing how to search through the "books" or remembering previous solutions to similar problems. (And, I'm not that old.)
This question has been answered many times before. People are re-solving the exact same problems with a new framework, platform, or language every two to five years, sometimes less. The "solved problems" never seem to stay solved.
Alan Kay had a good point when he said the last 25 years (now 35 years) have been more about pop culture than actual engineering[1].
I re-watched Star Wars Episode 1 recently, and, as soon as the first lightsaber showed up on screen, I felt like a kid again. The movie is still terrible, and should be excluded from the series[1]. But, there is just something about watching space samurai, with light-up swords, that made me spend the next three hours imagining how to build something like it.
I said this exact thing when I threw together my attempt at solving the problem a month ago[1]. (Except mine used a physics engine to simulate springs.) I am now cynical about a JS-based page layout engine approach being adopted at all. There are just too many people who, after mastering CSS, believe it is the only real, performant, and compatible way to do things.
> So the same argument as (say) YAML, Lua tables or TNetStrings. Or, if you include binary representations, stuff like Thrift, XDR and ASN.1. You can embed a JVM in PostgreSQL and write the functions yourself (or use PL/Scheme I suppose), but I would be basically amazed if anyone decides to do it for you. JSON gets the nod because it's understood by billions of systems. Other formats are going to struggle.
While I do not agree with his position, it is shared by many people.
Since many of the Light Table fans either use or have used Emacs, I would say that it is more of a relief to have something that takes the Emacs concepts and tries to modernize, adapt, or polish them. It might also be good to mention that the Light Table team chose a "usable editor first" strategy to build a user base, before attempting the concepts they demoed early on in development. So, we will see if it ends up mimicking Emacs or, perhaps, something different.
> I've made sure that my code was secure
> has just always been embedded into my programming philosophy
> So their environment was broken to me.
> I've began to realize that I'm a much better programmer than all of them
Good code quality, and security, is something everyone needs a bit more of, but be careful not to fall into dogmatic thinking. They are paying you to do tasks the way they want them done. If you can show them a "better"[1] way they might take your advice, but you should never expect it. Programming is more than just a job skill to me, so I always have to remind myself about the line between "my code", built on my own time, and "their code" for which I am being paid to build/maintain.[2]
> I showed them OSWAP, and they have never heard of it.
> I mentioned MVC pattern, and the manager didn't know what that was.
This is common. Never hearing of something is not bad. No one can keep track of all the tools available, learn them well enough to use them, and still accomplish what they need to do. No matter how much time you spend trying to keep up, you won't.
Also, your coworkers, and manager, might already know what will and won't be approved. So, they are only informing themselves of things that are likely to be important to their tasks.
> I've began wondering if all work environments are like this.
No comment.
[1] There are many definitions of better. (Time, money, complexity, maintenance, ROI, etc.)
[2] Some managers / employers want you to mix the two concepts, but, in my experience, this is just encouragement to focus more attention on the tasks they are giving you. You need to draw a line.
It is also worth a note that Elixir adds language features, such as default UTF8 binary strings, real macros, Clojure-style protocols, tooling, etc, on top of the Ruby-style syntax.
High Scalability Post: http://highscalability.com/blog/2013/5/13/the-secret-to-10-m...
Original Shmoocon Presentation: http://www.youtube.com/watch?v=73XNtI0w7jA
I also wonder about all the other small applications in the "HN ecosystem", like karma tracker, that rely on the hnsearch API. I see that algolia has an API, but will those other projects just die too?
There is a classic anecdote about the manager who handled a large stack of resumes by randomly throwing half into the garbage, and remarking "I don't hire unlucky people"[1]. I can't find the original source, and it's probably not true, but it is closer to what they are doing than actually evaluating people for a job.
It sounds like you are fixating on the example of centering, where using a physics model to generate positioning and layouts, without CSS or HTML tables, is the goal.
I have never heard of a hiring war-room or lockdown of that type. Are you redesigning/improving the current process, or just interviewing people until you meet the quota?
As mooreds mentioned in his comment[1], they might already be looking at old-age poverty. People are living longer, healthcare costs are rising, retirement funds are not keeping up, pensions and retirement benefits are being gutted by corporations and governments alike. So, speaking as someone who has a retired relative trying this idea, the downside might be minimal.
But, honestly, it was more of an excuse to learn NodeJS.
This topic comes up every so often. It rarely ends up as a silver bullet to financial independence.
https://news.ycombinator.com/item?id=6350201 (4 months ago)
http://www.zemanta.com/blog/i-bet-you-over-engineered-your-s... (2 years ago, in the comments)
https://news.ycombinator.com/item?id=5206578 (1 year ago)