jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Given that it is considerably more difficult to change the shareholder structure of an LLC than an Inc. -- which is the reason institutional investors don't like startups that are LLCs -- an LLC is a rather strange choice of structure for this investment vehicle entity.
It's your own personal Rainbows End!

http://en.wikipedia.org/wiki/Rainbows_End
Which is exactly why taking short term unemployed developers is difficult to execute correctly. They will not be unemployed for long, which means that they get up and leave the project - taking with them domain knowledge. That knowledge is extremely expensive to pass on - it involves the startup having to "train" their next employee. Better to reduce churn and get permanent developers.

This model only works for simple greenfield projects; as soon as you get complexity, it introduces dependancy of domain knowledge, which doesnt work with short term employees.

Even in opensource projects, there are usually only a few core developers - i.e. the ones with domain knowledge. Everyone else submits small bug fixes/patches.
Can't wait more to see the algorithm behind Google Wave. It may have failed(?) as a commercial product, but as a technical product it was kick-ass.
Not worth it. A better way to host a public contest is the way NYC is doing it with NYCBigApps. Take a look at their ToS, http://nycbigapps.com/rules, note section D. Those terms look fair to me.
The reason they don't cross-compile more often is that for the most part cross-compilation sucks - it is impossible to debug through, for one thing.

So, is the issue really the ability to use source debugging? We could still treat Javascript as an Intermediate Language and add a Source Pointer data format that would enable source debuggers in the cross-compiled languages.

In fact, we could build such things into Firefox and Chromium ourselves!
Simplest explanation (imo): SEO.
There are lots and lots of these 'nuanced rules'.

http://mywiki.wooledge.org/BashFAQ/105
Unlike patents, the origin of the work is important for copyright infringement. In theory, two people who independently come up with the exact same image are not infringing on each other's copyright.

Of course, this ends up being a matter of likelihood. And if you generate all those combinations, but happen to select one in particular that is just like a pre-existing picture, the courts won't believe that was by accident. But the collection itself probably won't be infringing.
Volunteer in Haiti for a month.
In addition to the sibling comment, as a pragmatic matter, one cannot. GitHub has a per-repo hard limit of 100GB of content, and allowing only 256 colors, your data set has 256^(800x600) members; this is unfeasible.
> If I find something messed up in a postgres release, and report it to postgres, they will take responsibility for that and manage the rest of it.

> None of this is true for NPM.

Not as it pertains to bugs, but as it pertains to malicious code (the grandparent's actual question), npm accepts and acts on reports. In fact, their CLI even reports security vulnerabilities in your packages, a feature lacking in almost every other package manager.

If all code were in on source code repo, that all authors contributed too....is that really so big a difference as splitting our the areas of responsibility? What are the chances that Tom Lane looks at every single line of every single patch?
Google Project Zero do not use the term “responsible disclosure” to describe this. They quite openly reject the term and do not follow “responsible disclosure”, which would prohibit then from publishing exploit details even after the fix is out, and would prevent them from disclosing that an issue even exists prior to a fix being available. The term was specifically a social engineering attempt to brand exactly what GPZ is doing as irresponsible (even though they didn’t exist at the time).
High frame rate is good, but to not get blur you just need a high shutter speed. Most digital cameras can do this easily. But simply having a high shutter speed isn't enough, as if it's fast enough no light will get it to get a proper exposure. That's why you'll need a supplemental light source, like infrared or a flash, a large aperture (aka large lens elements), or a lot of gain (ISO).

It's really a balancing act between the three. The more zoomed the lens, the bigger the lens elements need to be to maintain the same aperture ratio. That's why a 600mm f4 is absolutely massive compared to a 50mm f4 lens.

For something like this application though, the quality of the sensor doesn't need to be too high, you don't really that high of a shutter speed, nor do you need to worry about image noise. There's always light on at the pump, so you can easily calibrate for night time, if needed just bring a light meter (or use an app) to the spot at night and check.
In the art school sense, it actually impacts one of the most critical questions an art student has of themselves,

"Do I try to make my career defining art now or do I use this time to explore a variety of subjects and mediums?"

The fact the artist doesn't own the copyright to this early work tilts the question to the latter statement.
https://en.wikipedia.org/wiki/Tiger#Reproduction says usually 2-3 cubs per birth, mortality rate 50% in two years. They separate after two years. If the tigress only has one litter on the go at a time, that puts a limit of about half a cub per year.

The reported numbers come to about 1/10 of a cub per tiger per year, or 1/5 of a cub per tigress assuming equal numbers. If two thirds of them are sexually mature, then 0.3 cubs/year each.

That's close enough to the upper bound that it seems implausible to me, but these numbers aren't reliable enough for strong conclusions.
It's interesting how many commenters read "remote" as "contract" or even "overseas". There are lots of developers outside of SF, NYC, Chicago, etc. that would relish the opportunity to still live their suburban/rural lifestyle and avoid a lengthy commute.

One advantage for companies in big cities is they can usually hire these remote employees at a discount. It can get a bit hairy when two remote employees doing the same job are paid differently, but that is already the case in many situations.

The other obvious advantage is that companies that hire remote employees have an almost unlimited candidate pool. Even if a company chose to limit hires to their own country, the only group they cannot hire would be candidates unwilling to work remotely. Based on my discussions with thousands of programmers over the years, I'd suspect this is a very small group.
Partially. Doing so has made you more valuable to the company involved, and so marked you as more valuable to other companies (something about women finding men attractive that are already with another women - the first woman's rational investment is a signal that the man is worth investing in)

You just need to find ways to signal that investment - perhaps doing talks under the brand of the first company ?
In incident response you assume the worst, but in system design you try to minimize impact of common attacks like SQL injection.

There's nothing wrong with nesting algorithms (see the Facebook hash onion), so you can use the following scheme:

bcrypt(bcrypt(password, salt), pepper)

And do a pass on all your database entries like

bcrypt(old_hash, pepper)
> Heck, the phone's OS crashing was a rare, one-in-a-million event.

You live on a different planet to me then. I have used every iOS relase, and every one has been crashy for the first couple of versions.
I find that it's always worth the time. Even more so when I'm working on a quick fix code someone else wrote. I kind of have a few reasons for it:

1. Making the code cleaner is reducing technical debt. This will help in the long run, and I just sort of do it as I go. It's like tidying the house - it is more efficient to do little things regularly than to have a giant mess to deal with later. The little things make it easier to do something later, because you don't find yourself yak shaving as often to get to the main task.

2. In my personal and observed experience - doing the fixes at first seams like heavy task. "it works, this is just grunt work", but as you get practice at it, you'll find that it helps find bugs, it becomes a habit, and you just do it as you go.

3. It helps me understand the code better. Even if I wrote it. Just because I got it to pass tests doesn't mean I know why at first - but cleaning up the code makes me realize edge cases and what's happening.

One thing that helps is to keep in mind the axiom "all code sucks. Some code is useful" (to paraphrase a famous saying). I know when I code stuff, I tend to do a throwaway implementation or two first, just to wrap my head around the problem, then keep one. After a few months, I'll revisit and understand even better what to do, and rework it again. Then maybe it's decent.

I'm sure there are people out there who can do it great the first try, but they aren't that common. The secret is to not wrap your ego/identity as a programmer/understanding of accomplishment up in the code you've written, but in your ability to solve or lessen the problems that come up.
Yes, really. In one or two tiny tweets and maybe a hashtag from someone there. It may not be a big event; but, "acronym #hashtag-describing-event" is a thing. And that would be "happens on twitter" in Twitter terms.
I think there's a huge misconception that to scale your programming language must be concurrent and also extremely fast.

I can't see how you can assert that the JS ecosystem is "better". It is rapidly changing which is partially detrimental. What worked or was considered a good choice at the start of 2014 is now mostly obsolete or abandoned by the end of 2014.

As so many companies have shown it really does not matter what programming language you use as there are plenty of options to make it work, it's more about choosing the language that will provide the best fit for your business.
The sticky bar at the bottom saying that your devs are available to talk to is making me leave the page. It is extremely distracting since it doesn't scroll like the rest of the page, and compared to the rest of the page it stands out because it is completely black with white text.

Honestly I got about half way through before I just closed the tab. Put it anywhere else, it is nearly as bad as those popups that show up on GoDaddy, Dell or others sites asking if I need help and they float over the top of the page...
Another +1 for FastSpring, they've been fantastic to me. But there are other companies who do this too: Kagi & Avangate spring to mind, and Digital River bought & consolidated several companies that used to do this.
We need to treat the mentally disabled better. S Korea is bad, but just looking at places like SF (I feel that most of the homeless have mental issues here); it feels that we're not doing a great job either. The obvious solution is that mental hospitals need more funding. However where will they get that money from? Is there another more optimal solution that doesn't require as much money?

EDIT: I guess we're not that different

http://inthesetimes.com/working/entry/14142/bulls_hit_farm_l...

http://www.dailykos.com/story/2005/06/05/119393/-Slavery-in-...

http://www.globalslaveryindex.org/
I don't really agree with most of the ideas presented here. Setting your corporate firewall to "default deny" is just security theater, not real security. If a black hat installs malware somewhere, it can just as easily phone home via HTTP as on some random port. Arguably, the security theater of forcing everything on to HTTP actually makes it harder to spot anomalous traffic patterns. Earlier someone might have seen a lot of traffic on port 1234 and said "hmm, that's funny..." but with default deny it's impossible to see anything weird except by doing deep packet inspection.

As another poster here pointed out, hacking has gone pro. Clearly governments and organized crime have gotten into the business. The idea that people are going into hacking because "the media lionizes hackers" (like this blog post suggests) just seems kind of silly now. I think if anything, the media tends to exaggerate how scary most hackers are in order to sell more product.

I agree with the author that we are on a treadmill of patching vulnerabilities while creating new vulnerabilities. We'll never really get anywhere as long as we are on the treadmill. But this post doesn't point out any of the things that would actually help. For example, I think better sandboxing techniques in operating systems would help reduce the number of vulnerabilities. Unmanaged programming languages such as C/C++ are a perennial source of vulnerabilities, as everyone seems to know by now. Although most people don't seem to comment on this, languages with eval() such as Python, Perl, Lisp, SQL and Javascript have their own set of vulnerabilities that come from this construct. If we wanted to, we could get rid of these constructs.

Djikstra famously argued that computer science was not about computers. You could make a pretty good case that computer security is not (primarily) about computers, either. A lot of great hackers like Kevin Mitnick were able to penetrate systems just by calling up a technician and pretending to be someone they were not. Computers have given more power to individuals, but the problem of finding trustworthy individuals for your organization is no different than it was before computers came on the scene. A lot of hacks are really just cases of where too much information was shared with too many people who didn't need to have it, or systems were run with inadequate oversight... neither of which are technical problems.
Hey, confidence is a broad topic made up of a lot of skills, habits and forces. Think of it as an ecosystem of parts... To speak simply, it comes and goes. Like waves. No one is 100% confident all the time. You're 'secure' around people you hang out with because you're comfortable around them the same with the area you focus on. That's not confidence. Confidence is elusive and reacts well with the unknown. You cannot play safe with confidence. You have to go outside the barriers and push limits further than you can imagine. No one can guarantee confidence, but you, its a road of bumps and bruises. Hit the gym, work on your appearance, take daily risks and expand your knowledge, you'll feel better about yourself to harness the power and responsibility that comes with confidence. Which most don't. Most people fake it to make it. This doesn't work. It's like building a robust program. Strong code, strong functionality, Great User Interface. You got a hit. Fight for something in your life. That's a huge one, that's where passion lives.
Check out a book called Think and Grow Rich by Napoleon Those are the 13 skills to master to become confident. Real World Experience that you can use immediately. Books on Leadership is another great resource.
They probably watched Reefer Madness back in the day...
What would be the appropriate sanctions for a breach of this magnitude? The EU is pretty spineless and I suspect the answer to the question will be 'none'. Just don't do it again and if you do don't get caught or something like that.

Belgacom seems to have been more than happy to see this swept under the carpet, the gag on Fox-IT and their partial answers in the investigation are most telling.
Here is the TinkerPop/Apache proposal that was approved today: https://wiki.apache.org/incubator/TinkerPopProposal
Under your proposal, petit-torts would never be subject to class action suits since the lawyers would never make money.
Find a medium-sized company with a local monopoly.

- They are not competing in their market / has had dominance for more than a decade.
- Their business model does not depend on innovation or moving fast.
- The ambitious people are all located in sales/marketing.
- The development dept. is known for saying "good things take time" because they can afford to.
- Career advancement typically isn't possible unless a tech lead quits, but they're cushy.

You can't trade low effort for low wage. You have to qualify skill-wise and drop the effort over time. You may be able to find something on the low end for your skill level, but an employer will think it's average. Picking something you think is below your skill level might boost your psychology, and you might be able to pull 2-3x.

As for picking tasks where you can minimize effort:

- Pick a role where spending time on other people's task is justified. During stand-ups when you have to explain what you did, you can say that you worked on your own thing, and that you helped the other person. This is not just a way to cheat: I care more about what I do, if I'm helping someone who cares more. I invented this coping strategy at points where I didn't care at all myself.
- Pick more researchy tasks: People don't know exactly what to expect, the work isn't as easily quantified. So when you spend longer or don't have as much to show for it, that may make sense.
- Become highly available on emergency / show high effort once in a while: This counts against not making an effort, but people will remember you for fixing things when it matters, and they tolerate you working at your own pace most of the time.
- Select somewhere with a new CTO / tech lead: They're super busy learning how to juggle management and mentoring, so if you're stuck onboarding for more time than normal, they won't blame you. This may sound leechy, but just make sure you provide some kind of value to everyone else other than your full attention.

Also, this was my best-paying job for 3 years focusing on family and mental health outside of work.
Senior DevOps Engineer at a mid-sized, stagnant californian “startup”, roughly $150k salary.

Seriously. My last three jobs were at companies which were 10-15 years old, had burned through $75m-$150m in VC and had flat revenues of $12-$15m for years.

These are my bread and butter. I “work” remotely from utc+2. Theoretically I am working from home, but pre-covid 60% of my time I was “working” from cafes around Europe/the middle-east 1-3 hours per day.

The rest of my time I was being a tourist, getting stoned, having flings or mm-transit to my next destination.

The thing about companies this size is either you have a good sized team managing a medium worklod and very low expectations.

The long timers are milking it to make up for their worthless stock options. The executive positions are revolving doors (all 3 companies saw at least 2 ceo turnovers during my term).

At my last job all real work was done in Belarus and Russia. As the team lead, my entire job was ended up being tidying up / linting / deduplicating our terraform code base while giving the actual engineers encouragement and architectural advice. It even gave me a reason to party in minsk and make more friends.

I get fired every 1.5 - 2 years, but I spend like a poor homeless backpacker and my home base is in the 3rd world, so at age 40 I already have enough saved to retire.

I used to be a hard workimg, diligent, ambitious engineer working startups I believed in, but getting screwed over by 2 consecutive YC startups made me look at employers as nothing more than a short-term atm.

These positions are easy to get if you use the right search criteria, actually know your shit enough to project confidence, and if you’re extroverted enough to have built anreally large network of colleagues who like you.

Look over YC’s list of companies from ‘11-14. Specifically look for the companies which are still around, aren’t unicorns but haven’t failed, and use the tech stack you know best.

Don’t be afraid to shamelessly inflate your resume to do this. Your employers will lie to you, their customers and their investors with a sociopathic calm demeanor. There’s no reason not to do the same.
Java libs are definitely helpful, the time I mentioned includes wrapping Object oriented code into functions. This is easy if all that is required is one or two methods from the Java, however for more than immediate usage, it feels like building a library just because I need to use it.

In Python ecosystem, that labour already done by someone else, preferably who didn't start writing a library just to deliver code within a week.

One good thing about writing libraries in Clojure is the immense stability and composibility it offers. We can use the same code many years later without fearing breakage,a 'primitive' function can also be easily squeezed into numerous other functions which means reusability is quite high.

However, it is still an impediment for shops less than 5 devs.
https://deepbaltic.com/2018/03/20/being-non-binary-in-a-lang...
Indeed. I saw an interview with the tank commander that was ordered to drive his column through the crowds in front of the Kremlin. He refused. In China they did it.

But the Chinese were smart. They used units recruited in the regions, far out in the countryside with no connections to Beijing or the big cities. Tiananmen Square wasn’t a spur of the moment response, it was meticulously planned.
Thanks for the kind words, I'm absolutely not depressed ! I'm very happy with my life outside of work. Some days I even feel euphoric being lucky as I am, being able to play my favorite sport and having a loving family.

I'm only trying to optimize by reducing the time spent working and thinking about work, which I never see bringing me anything else than money.
> Full respect to him.

I somehow feel like this last line isn't well suited for this audience. Anyway, noone is doubting the impressiveness of his particular suite of skills or his business achievements. Thing is that as a leader he's a mixed bag. He gets impressive things done, but he has an occassionaly repulsive world view. What I personally like about him is that he picks projects that have social potential and at the same time are low hanging enough to be doable within a matter of decades. Power to him for that, but let's not idolize him.
Thank you very much for your insight!
Wickr is proprietary.
Suppose Cheney decided by himself to let the attacks happen, could he have, without anyone catching on? If not he alone, who else would be needed? No more than five surely.

No, because the people at the top are not the ones who do the work. They set policy, and sometimes directly tell people what to do - but, more often, they tell people who then tell other people what to do. If a conspiracy is going to involve the top of the chain - and it should be pointed out that the VP is technically not in the chain of command - then it's going to involved dozens, if not hundreds of others if the conspiracy is actually going to do something effective. And in that case, there will be enough written down that eventually it will out. See, for example, the Iran-Contra affair.

An excellent account of both what the critical points for intervention were, and what happened on the day is "The Ground Truth": http://www.amazon.com/Ground-Truth-Untold-America-Attack/dp/... The title has unfortunate "truther" connotations, but it comes from a term the aviation industry uses to establish what happened after a crash. They use first-hand material and evidence to establish the "ground truth" of the crash, and from there try to extract lessons. The author does exactly that, using primary sources exclusively - such as recorded conversations between air controllers - to determine the sequence of events.
That tagline is indeed humorous when attached to such content-free material. BTW, http://www.businessweek.com/magazine/content/11_17/b42250411... if you're curious.
I feel like it's pretty rare that I'll find something as convenient as a pole to lock my bike to and other than that, I don't see how this can be used.
yeah the sloped bed is going to be a big problem i think. loading things from the side, ladder racks, tool boxes, etc. lots of issues with that.

the bed cover looks awesome though, and I love the ramp from the tailgate. that's fantastic.