1qaz2wsx3edc

On the value of bitcoins:

There was another discussion on hacker news, where I commented on the fact that bitcoins should have a higher value due to lost coins: https://news.ycombinator.com/item?id=6859991

In that thread, @nl provides the most interesting look at bitcoins from the perspective of bitcoins as a part of GDP: https://news.ycombinator.com/item?id=6860024

Anywho, the value is largely speculative, but most indications seem to point to a long term growth.

tl;dr; Banks are federally insured, marijuana is still illegal at the federal level. Policy must change.

Ergo StreamOS.

I wouldn't bother running Steam on a non-valve distro, it just doesn't seem practical given the options available (Win/OSX/SteamOS).

Full disclosure: I use Steam on OSX & inside a Windows VM. My biggest peeve is that Valve restricts the Steam client to a single runtime (meaning: I can't run steam on OSX & Windows at the same time "This account is logged in elsewhere"). So I'm always switching between the two, which causes a bit of user fatigue. Come on, just allow unlimited instances/logins from the same IP. I digress.

I'm about 7-10 years myself, I've gotten pretty bored and unmotivated as well. But what I've learned is: Programming for money and programming for passion are two very different motivators. They don't have to be exclusive, but regularly are. And often it can become over extended.

So, here are somethings you can consider: Try finding work you're passionate about first, that also pays. Maybe work for a non-profit? Try to find a role that lets you expand from where you currently are, perhaps management, business analysis, marketing, design or whatever pet preference you have. The point is not to over extend a single skill. Consider less hours, I've personally found 30 hours a week to be tolerable. Relax that skill more often. Try working on different projects regularly, I work on different projects every 2-6 weeks. The change in pace & direction keeps me excited & interested.

Also consider: building passive income generators, you've been programming for 15 years (why isn't the code working for you?).

All in all, keep changing your angle until you're happier.

Just my two cents.

This still doesn't convince me it was ever a beneficial design.

While you're at it why don't you fix: (needle, haystack), (haystack, needle)? :P

Just because you can, and others do, doesn't necessarily make it a good idea.

By writing & encouraging developers to use the new `secrets` API, we expose them to a bad practise. Not only that, but other solutions exist (like using `Rails.application.config`). I'm not against configuration files per-say, I'm against secrets as persisted values in a codebase.

Doing this is bad: https://github.com/search?l=ruby&q=cookie_secret&ref=cmdform...

This is a fair criticism, I totally missed the beta flag. Cheers.

> Conceptually, they're the same thing, but since Zeus is written in Go, it's totally different code.

Thank you, this is what I wanted to hear. :)

> I personally use environment variables to handle this case, but basically, every single approach has pros and cons, not to mention that there's legacy codebases... small steps.

I just think it's a bloated feature when `Rails.application.config` already exists.

Yes, I'm aware, but what was the problem with storing configurations under `Rails.application.config.thing` as ENV['vars']?

It just seems like bloated featured.

The only issues I have with this release is that they could of waited until after the holidays. I have a feeling we'll see a security patch right before xmas.

The second issue I have is `secrets` should be entirely removed from the framework. These settings should NOT be stored at the file level, it should be handled by environment flags. I feel this is a fundamentally broken feature.

Spring is neat, was it just a port of Zeus into Rails?

My first thoughts were along: "Nope" and "This is how the robopocalypse starts".

Google & BD are both researching machine learning, it only makes sense for Google to buy them.

I understood some of those words.

I don't know. I find gittip's model mostly rewards popular coders.

Where as tip4commit, rewards are not influence by popularity. I do see how fluff pulls could drain the pool. One needs to ask: Is changing a typo worth $4 dollars? Is it worth my time to do it? Maybe I should just click that merge button.

In my opinion bountysource is the best reward system, as it gives context, popularity is a boon, and it shouldn't generate fluff.

Just my two cents.

My concern is that it may be the wrong vehicle for change when they don't bark what they preach.

I feel the biggest contributors to change aren't large sums of money thrown at it. e-Learning, Bootcamps, or groups like ladies learning code, have, in my opinion, a better effect.

It's perplexing that to avoid gender discriminations, the solution is to discriminate against genders. I don't like these, I think they further the stigmatism that is native to our industry about gender discrimination.

Specifically I'm bothered by direct benefits due to gender, I have no issue with educational programs as long as they remain open to all.

I don't want to end up in a workforce where people are working because it was a good financial decision from yesteryear. I want to work with people who are truly excited about what they do. And choose it for no other reason then it was: fun, interesting, and exciting. Those would be awesome people to work with. Welcome!

It's up to the freelancer to develop a solid pipeline for work.

Downtime isn't uncommon either, it happens, but it's also one of the reasons your rate should be high enough to support your downtime.

Well, I have a feeling it will go higher. I've only been paying attention recently, but as I understand it, 30-40% of generated coins have been inactive since 2009-2010. If the market cap is 15bn, then we can assume 11538461.538 coins exist, but if say 8076923.076 coins (70%) then the value of a coin is 1857.14USD or the market cap is closer to 10b.

Which is it?

Seiki is still HDMI/1.x and doesn't support 60FPS. Nor will it help gaming at it's limit refresh rate. The good is that they're putting pressure on the big brands. If it was HDMI/2.0, I'd be all over it.

It seems like they only want to put pressure on the FAA. 3/4 FAQs mention the FAA.

More importantly isn't this solved via authentication (basic auth).

Or boycott LG and any businesses that acts in this manor.

Attacks like this are common place on the internet.

What I will take away from this, is that github provides a very nice authentication audit log. I really want every service/app/site to provide this kind of information.

You mean it isn't? http://www.thechurchofgoogle.org/

This is a terrible interviewer, it has nothing to do with you. They know what they want, but they don't know how to find it properly.

Don't be afraid to use you're own notebook/laptop to Google a solution, or keep asking questions about the desired solution.

Be free in not having all the answers either, be confident you can find the answers. An interview shouldn't be about vague technical hurdles you have to jump through.

It's about proving competence & compatibility of character.

If your interviewer is willing to end the interview because of one dropped ball, call them on it.

Growing pains, that's all.

They've really done a lot of work. The jump from 0.6.4 to 0.6.5 was 775 commits. Wow. We're seeing concepts being fleshed out, they'll be refactored and strengthen in time. The team seems to be fully focused on 1.0.

Scalability is still a big concern, but it's only a problem you can be so lucky too have.

Meteor still needs to improve code structure, there's no common architectural pattern yet (just some lose guide lines). In my opinion, it would be a benefit. Meteor is still in its infancy and a developer is left to their own devices, rather then common sharable patterns. Rails does this well with the plethora of use-case strengthened API design, a benefit of it's maturity. Meteor will get there.

This is unreasonable. YT isn't going to disappear. Did myspace? No.

The fact that YT provides an API is plenty to reface it. You should view this website as another from of protest. Which of there have been plenty of protests in recent.

It's not wrong, just a different one.

Don't use 1.2.0 until it's reverted or write a getter.

It's quintessentially a bait & switch. Businesses were lured in with a low flat rate, avoiding interchange rates and now square is pulling the rug and defering the rates back to the business.

> The two parts of the announcement, JS+WebGL decoder and the GPU cloud driving the encoder, combine to make a whole greater than the sum of the parts.

So, it's some client JS WebGL code, and something else driving the encoder in the cloud

I like the idea of scriptable VNC like streams.