skysight-inc/HackerNews huggingface dataset:
Probably. AGPL says you need to "provid[e] access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software", and GPLv3 also seems to require digital distribution of software to include immediate source access. GPLv2's source requirement, on the other hand, can be satisfied by a "written offer" to provide the source no matter how the binary is distributed; I think this is (along with apathy) how Apple gets away with taking months to publish GPLv2 sources.
I reposted because I've made some improvements and open sourced it since then.
>Japan was known for making cheap low quality products much like China is now. It's only relatively recently that they moved up the quality ladder.

Perhaps you mean the cheap radios, cameras, vehicles etc of post-war Japan. Those were made to rebuild their economy, and from a starting point of almost great desolation.

Go back a few decades from WWII, and you'll find out that for centuries before Japan made extremely high quality products, from swords and teapots, to furniture and jewelry.

To the point that European and American artifacts of the same type and same era look like the Dell Ditty compared to the iPod Touch.
I've always had trouble getting programming jobs, apart from the very first job I got which I got by a combination of knowing the guy and exaggerating my skills (also it was frightfully low pay).

At various times during my freelance career, thing were so bad that I dusted off my resume and went out to try and find something permanent ... I never could.

A mixture of dealing very badly with recruiters (whom I consider to be pure satan spawn) and good luck of finding another freelance gig "just in time" has always kept me off full time payrolls.

On the one hand it would have been way easier to be earning a great salary while I saved up and then finally "cut loose" to launch my own company, but being forced (somewhat) into freelancing has had beneficial side effects; mostly that I now run a business that actually has some promise of turning into a saleable asset and allows me to live where and how I want to.

I also made things harder for myself by being too obsessed with the particulars of the technology I used and a heavy dose of NIH (not invented here) so I wasted a shit tonne of time writing code that was never really used.

If I had my time over again I would probably have focussed on flipping wordpress sites at a margin sufficient to give me time to work on other stuff. That type of consulting is also pretty easy to systemise, meaning you can hire people to do lots of the work for you once you've figured out how to get customers.

You probably have a lot to offer as a "consultant" because you have a general understanding of how shit works, you can communicate well with business people and you can put together a team who can achieve a specific goal.

The challenge, of course, is that no-one will give you that job. Fortunately it's not impossible to just go out there and create that job for yourself.
http://i.imgur.com/zmrDFoY.png

I'm a day late, but I had this tab open all yesterday, so close enough. Currently working on Fortune, an iOS app. The premise is that sometimes you just need some sort of fortune/pick-me-up/inspirational message. Fortune sends you a random user-submitted fortune at a random time during the day, and also allows you to submit fortunes that will be sent out to users.

Pulling the screen up (http://i.imgur.com/CC5OKar.png) reveals the interface for giving a fortune, while pulling the screen down (http://i.imgur.com/Cm3qgJs.png) reveals the interface for taking a fortune.

It uses Parse.com as a backend, and I'm currently working on reducing the total number of API requests.

One of the problems I'm anticipating is how to prevent users from submitting negative fortunes. I'm looking into doing sentiment analysis on fortunes as they're submitted, but I'm open to any suggestions.
IHMO, key to well executed #1 is that it should be social yet anonymous so the writer gets a sense of community without feeling like they would be judged.
As a handicapped individual, I hate all this stupid word play. I'm a cripple. Unless calling me something different is going to somehow make me run, climb, or dance again, then it really doesn't matter how you refer to me. Call me whatever you want, but don't refer to me by any of this flowery language, I find that far more offensive.
This what you should see in a secure browser. The site was apparently provisioned with a pre-revoked certificate, so you shouldn't be able to connect to it. Though some browsers can.
Swallowing strong magnets is pretty dangerous.
Hey, I was just wondering why you think learning JS is a bad move? As someone positioning themselves in this industry and not often hearing the bad sides of things, this would be great to hear.
Fantastic post! I look forward to more soon!
Maybe something like http://pineapple.io/ ?
Find the people you want to hire outside of HR, and then craft an HR job posting that they can ace.
You might consider pursuing an apprenticeship in Software Craftsmanship. You would likely spend 6-9 months as an apprentice and potentially end up with a full time job. There are a number of companies in a number of countries that do the SC apprenticeship model. You have to look around for them though. Look for local SC meetups and go. Talk to the people who work at the company that does apprenticeships and see if it is a good fit.
Forgive my tone, but don't give a shit if students aren't interested.

I've found that a love for OSS and linux is something that will attract hobbyists and tinkerers more than students.

Turn you LUG into a Dallas one, not a college one. I guarantee you'll get at least 1 guy over 60 years old, a ton of devs in the area, tinkerers/hobbyists and a lot more knowledge than a couple of 2nd year noobs trying to make their tarballs run and getting compile errors for CS assignments.

Try it and please do share your feedback.
Who pays the price?
I like this, but rather than "hardcore", targeted at pre-CS, and possibly 1st year CS students. Computer Science programs are awful at introducing and reinforcing fundamentals. Examples are binary/hex, how data is stored in memory, compilation, basic system architecture (CPU/memory interaction), basic command line/shell usage, etc. - topics beyond a typical high school programming course, but prepares the student for their first year of CS. Content built around an Arduino or Pi would be ideal.
Sure, we can label it whatever, but a turd is still a turd. If we're experiencing crony capitalism then we need to take action to correct it.
I think it would be interesting to have an app that determines the optimal times to stop for gas during a trip. Especially when you are traveling across state lines, gas prices can vary a pretty decent amount.

The simple version:

- Once you're under a certain amount of fuel (1/3 of a tank?), you open the app, and tell it you need to get gas within the next n miles. The app checks gas prices along your route (does gasbuddy have an api?), and tells you which gas station you should stop at.

The complex version:

- The app connects to your car with an OBDII device via bluetooth (they are pretty cheap), automatically watches how much gas you have left, and determines the optimal place to refuel once you are under 1/3 of a tank. Basically, you would be able to open the app at the start of your trip, and it would alert you a few miles before the best exit to get gas.
Even if their intent was just to start a discussion, they are not being helpful by "submitting" such bogus code. It would be easier for an expert to rewrite this patch from scratch than try to figure out all of their flaws and unfinished sections.

In one of the email responses, someone pointed out a problem with their code and they responded, "Oops we posted the wrong version" ( http://article.gmane.org/gmane.comp.encryption.openssl.user/... ). They aren't exactly being respectful of other people's time with stuff like that.

In secure coding the phrase "the devil is in the details" applies very strongly. So if you don't have the details figured out, you don't have much of anything.
I think it's better to think of it as division being an operation that returns the appropriate type for the operation, i.e., a float where necessary. The type of the operands remain unchanged so "upcasting" is not applicable if you ask me.
Dear Uber: you’re great but please add this feature
There is such a thing as culture, and different cultures have different characteristics and values. This is well known to ethnologics and social scientists, and has been studied extensively.

Those are not "racial generalizations" (and the fact that the Japanese are asian has little to do with that, it could have as easily been about differences between French and German attitudes).

Of course you can find Japanese who are totally sloppy and against the description given above. But you wouldn't find a Japanese culture where sloppiness is OK, and shame is not important.

Outliers exists everywhere -- but the importance of observation is to find larger patterns and be able to summarily understand your subject. Science starts with labelling things -- and it's perfectly rational.

And of course, observations and conclusions can be corrected as more data arrive.
sites like freetaxusa.com do taxes very well, and are free in most cases and extremely cheap for the services it does charge for

from an end user perspective, if it's already free then being OS doesn't really add any value
You're right, I'll add a link to their site.
Out of curiosity - what does it cost to have an electrician install a 240VAC outlet in your garage? Has anyone out there done it and can give an idea?

Teslas can charge off a 110 outlet, but they recommend using the 240 volt faster-charging unit. But most houses don't run 2-phase power out to the garage.

And what if you don't own a house? What do apartment and/or house renters do for charging?
I love this. These projects almost certainly ultimately fail, get laughed at, and then end up educating us anyway, whether for what to do or what not to do. I expect I'll probably see some hilarious things from it early on, laugh at it's idealism and mistakes, and in 10 years I'll be using tech designed by it's apostles.
Empathy is a core engineering value. If not exercised, people will unsurprisingly often ignore what you have to say.

It's possible to be correct and helpful without saying unkind things.
These are some pretty good points. I got lucky in a few ways, but i'll tell my story. I was a journalist for five years, but had always written code for fun. I ended up becoming friends with a former programmer for a large software company who had recently started his own consulting shop. I showed promise as a developer, plus I had other skills that they could use. It was only a 3 person shop at that point, but they were able to find several smaller contracts that I could take on, while also having me help on larger contracts in Rails. I kept at it (and have been at it for about 18 months now). I feel like i'm just now coming into my own, so to speak. i know a popular framework relatively well at this point, and while I don't know all the nuances of several basic web technolgoies yet, I'm still studying them (also, you never stop learning even if you're an expert).

the bottom line is that I found a place that would nurture me as a developer because I had promise (probably like you, if you do it for fun), and I had other skills that they could simultaneously use. By putting my understanding of journalism/communication/marketing to use, I was able to bring in some really nice contracts, and now I'm working on a popular social networking application in Django.

So, I guess what I'd say to OP is to find all your strong points, find places that those skills are also relevant at, and "dual-class" so to speak (if we're going the RPG route here). This way you are leveraging your abilities three different ways: past experience, future promise, and current strengths.

oh: and one thing i forgot to mention. HANG OUT IN IRC, a lot. The people there are incredibly knowledgeable and can often help out or give you advice really quickly

i dont even know if all that made sense. but hopefully it helps some
I see these stories quite a bit and they're kind of annoying. ex. 'How I switched my career, and tripled my salary, and became a software engineer, all in 8 weeks'.

Please. Many of my colleagues, and myself to an extent, have spent many many years since childhood preparing just to get into a reputable engineering school. Then it's 5 yrs of constant workload get the degree, whilst hustling doing coop. Then you get out in the real world, and life smacks you in the face, and you realize its only getting started and you're about at the bottom of the rung as can be.

To be honest, I get a little offended when someone goes through a couple tutorials, reads couple blogs, and suddenly they call themselves an engineer. I have friends who've been grinding out code since they were 10yrs old (now works for google), people have to realize programming and engineering takes a lot of hard work, it's not something you master over the course of a few weeks/months.
Sure, you could prob hook it up to gcal. But I thought they may have a timer event as well.
Similar question: When is it time to stop being a developer? It seems like many companies have a very low average age. I don't think I know of a single person above 50 at mine. Where do they all go? Does everyone retire relatively early? Or do you actively have to seek out companies with older people (or start your own)? How many of you moved into some form of management or executive role after beginning as a developer?
http://media.caranddriver.com/images/media/51/under-the-tesl...

In addition to the motor, the schematic diagrams above seems to many moving parts that typically need work by 120,000 miles. Eg: steering (likely) differentials (likely) and in various parts of the suspension (internal). Whilst the specifics may be debatable, most of these items are wear items and require fluid changes and/or replacement internals. Things also like wheel bearings will need some preventive maintenance. If this spreadsheet was for a 50,000 mile interval or a lease perhaps you'd overlook these. A chassis for $30K+ with 120k on the clock would bring customers looking at the cost of these services, I would venture. One way luxury brands (at least in the past have) maintained the price premium of their new vehicles is to make the 100K and up maintence quite expensive.
>If you want to be a reasonable developer, you cannot get away without being expert at least one low-level language (C or C++), one high-level language (Python, Ruby, LISP, etc), some knowledge of OS fundamentals (threads, processes, filesystems), some knowledge of concurrency (threads, locks, message passing), understand how to design your own language and build a compiler or interpreter (Flex/Bison, lex/yacc, etc), and a good base in discrete math (at the minimum, ideally some knowledge of numerical analysis and probability would be very useful as well).

Okay, so I think when the OP was talking about 3-6 months for a developer job, they were referring to web dev. That is where I have seen the most "6 months to a position" stories. You certainly don't need all of that knowledge to put together a crud app or a front end with all of the frameworks and templates available.

You do need that knowledge when your app/site suddenly explodes with millions of users and your backend has gone thermonuclear due to being unoptimized.

In this case, the body of knowledge for a web developer is much smaller: HTML/CSS/JavaScript/A few frameworks. This is much more appropriate for the 1-3 year span.

Some quick google searches:

http://learnwithjeff.com/blog/2012/08/21/how-to-get-a-job-as...

http://www.codeconquest.com/what-is-coding/programmer-6-mont...

http://freelancefolder.com/how-to-become-a-freelance-web-dev...

Note: I know these are basically blogs with probably zero credibility here, but I've had a few conversations which basically said the same thing + 6 months extra time to be conservative.
Sure.

The first three parts are a rundown of how the Soviet Army was organized at the time of writing (the early 1980s). This part was of great interest then, because reliable information on the Soviet Army was hard to come by in the days of the Iron Curtain, and the author (http://en.wikipedia.org/wiki/Viktor_Suvorov) was a recent defector. But for today's reader, this part is pretty dull, all tables of organization and maps of military districts. They're all safe to skip.

Part IV ("Mobilisation") departs from the data-dump format of the earlier chapters to talk about how the Soviet Army is organized so that in wartime it can double its number of units overnight, through a system the author calls "invisible divisions." If you wondered how the USSR was able to turn things around after the early disasters following the Nazi invasion in 1941, this chapter will be of interest.

Part V ("Strategy and Tactics") is where the book starts to get really interesting, because here it starts giving you insights into how different the way the Russians looked at war is from the way Western armies do. Part VI ("Equipment") expands on that theme by showing some examples of how that type of thinking informed the way the Soviets designed weapons that became world-famous for their effectiveness, like the AK-47, the T-34 tank, and the Hind helicopter.

Finally, Parts VII ("The soldier's lot") and VIII ("The officer's path") are narrative descriptions of the lives of enlisted conscripts and officers in the Soviet Army.

Overall, I found the book useful because the author's experience in that system taught him a lot of lessons about leadership -- especially leadership in situations where you're expected to achieve impossible things with limited resources and mediocre (at best) people. And the stuff about Soviet strategic thinking and weapons design has lots of interesting things to say about the value of simplicity, reliability and scale over things like feature richness or even user comfort.

These are not arguments you hear a lot from Western writers, so they are a refreshing alternative take. He's writing about weapons, of course, but the arguments are presented in such a fashion that you can easily extrapolate the lessons to really any kind of product.

(I actually referenced one of those lessons in a previous comment on HN, here: https://news.ycombinator.com/item?id=5062096)

You don't have to read the book front-to-back to get the good stuff out of it; skip over the early chapters and start at Part V and you'll get all the nutrition with none of the boring, out-of-date tables and charts and maps.
"The need which will drive new OS adoption is security."

Regardless as to wether or not Ethos is the next widespread OS, that line rings very true.
There's just one issue with the survey (although this is fucking brilliant!):

You should have first defined what "Remote" means.

A company could be willing to hire remote, but to them remote could mean somebody within the area who can drop by the office from time to time.

Still, I am very impressed by your efforts.
Blackcoin's proof of stake promise made its price fly
He's not saying dice or other activities like that are rigged, he's saying the odds in casinos are manufactured such that the house wins most of the time.
True, but this is useful if you want to stop somewhere along the way somewhere. For example, I've had a few instances where I wanted to stop by a store on the way home from work. This would find the best one to stop at on the way home. Google Maps just shows me the closest one to my current location - I don't really care where it is, or when I stop at it, as long as it is on my way home.
Hmmm, interesting.. Never heard of this before..
That's nice, but I'm specifically wondering about the motor "oil changes" and the cost of the motor itself, and this doesn't address that at all.
I don't have the stats, but most people knew someone at their current employer before they worked there. Nothing is a sure thing, but knowing someone there (and them knowing that you applied, really want the job) is the best way to tip the probability in your favor.

If you don't know someone at the current job you're at, figure out a way to meet them. It's very easy these days with social media, just favorite their tweets or attend meetups.
>The pizza is indeed incredible. However, how much of that is simply an alignment of my sense of taste?

Little I'd say. Judging cooking is not just about "taste". Even if some people don't like some dish, quality fresh ingredients and proper preparation are not debatable for example.

So, that some people might hate that pizza and love Domino's, or prefer some other kind of crust, doesn't mean much with regards to the quality of the restaurant. Other stuff matters.
Ask HN Mods: Can we add some extra options to comments?
In large threads where there are hundreds of comments, I find myself frustrated at times with the way comments are displayed.

1. They don't seem to display in order so new comments coming in can appear anywhere making me have to scroll through all the comments again just to find the new ones (even with browser plug-ins that highlight new comments).

2. There is no way to just view top level comments (yes, I have a browser plugin that allows me to collapse comments, which I think HN should do on its own, but I'd have to manually collapse each one just to read the top comments). Ideally I'd like a fast way to view all top level comments by default

Some threads where this immediately becomes applicable are threads like "Who's Hiring" and "Idea Sunday", etc... I'm sure there have been other popular threads where comments just grow out of control and I wish there was a better way to manage this.
This would be a more compelling rebuttal to Willem's post if Akamai hadn't confirmed his central thesis:

https://blogs.akamai.com/2014/04/heartbleed-update-v3.html
I'm a manager of a small team and 2x wouldn't bother me too much as long as it was completed well enough that I didn't feel the need to rewrite it before it goes to production. Small things caught during code reviews don't bother me too much. Major gaps in fundamental understanding bother me a lot.

I currently have an ops guy trying to transition to development and he is seriously 10x on the 4 tasks I've given him recently and I will not use his work in production even after that work. He does the meetup thing and can talk the talk but I've had to completely write 3 of the 4 items myself and the 4th sits in the back of my mind. Only reason he still works for me is its hard to fill this specific ops role and he does that ok though I'm questioning that now as well. If you are 10x slower then yes please stop now.

Don't let that discourage you as you don't sound that far off the mark and maybe it will click but it does sound like you are probably at a disadvantage technically. If you get the opportunity focus on something else that differentiates you from the rest like documentation practices.
> Lobbying money goes to politicians pockets.

Well, not till after they (or their staffers) retire it doesn't.
Can it be modified to support more than one "via place"? And what if I don't really care about the order I visit each location, but just want to minimize total length?
Firefox on Android rejects it properly.
Sounds like a networking issue rather then a skills issue. Start making contact with startups, design agencies that might do a bit of coding on the side. Approach them not to get a job, but just to have a face to face chat about what they do, if they have any advice for you.