skysight-inc/HackerNews huggingface dataset:
“Bless the Maker and His water.
Bless the coming and going of Him.
May His passage cleanse the world.
May He keep the world for His people. ”
In an office I used to work in the personal assistants were adept at forging their boss' signatures for exactly the same reasons that these machines are used. I think this is probably quite common.
You don't need to be set up as an investor. You can structure shareholder agreements and different stock classes etc. pretty much as you please, or directly award vested stock (beware your local tax rules if awarding/being awarded vested stock in a pre-existing company - chances are good it'll be taxed as income based on some estimate of market value; but if you enter from the start, as a founder, that's not an issue).

The issue in that respect is not what you legally can do, but structuring it in a way that won't scare away investors with too much complexity.

Generally, though, nothing will "protect you from future investor rounds" if they really want to fuck you over, other than being diligent and keeping a lawyer around, and picking honest co-founders. If the investors coming in and other still employed founder(s) wants to mess things up for you, it can be tricky to protect against them diluting your share holdings to next to nothing, for example (e.g. do a round on a very low valuation; issue large amount of options to remaining founders to make up for the extra dilution they take). Of course, if investors try to do that, chances are they'll screw the remaining founders first chance they get too.
The CTO can ask you to improve your coding or to stop coding, afterall he was retained to make those calls. But he cannot ask you to leave the company if you are a proper cofounder. The only person who is in any position to make a request like that is your cofounder or your Board.
This is not the Heartbleed bug. I am not certain this is actually an immediately exploitable vulnerability (aka a sexy bug). What this looks like is an instance where the code calls free() on a buffer, then assumes the buffer is still available (uses it in some way). The patch seems to make it only free the buffer after it is empty, preventing this behavior. I think this is related to OpenSSL's issue with malloc and the way it handles memory allocation.
Why is 2048, an entirely stolen game and an example of all that is bad for real programmers, getting so much play on Hacker News? I don't understand this community supporting outright theft.
You can generally offer tradespeople/servers and the like extra money whenever you wish!
It's a bug that got in the way of memory hardening that could have stopped heartbleed, but it's not actually related.

Heartbleed is reading too far, this is not that.
My expectation is that if they were serious about this initiative, they very likely would've stepped forward with some vulnerabilities for disclosure.

But it seems like it's just words and business as usual.

I'm curious what their response would be in the perfect storm scenario. A foreign country or criminal enterprise causes severe damage to much of the US. Both the intelligence agencies, government secrets, and the technology industry are severely impacted, crippled even. And the enabler? A series of vulnerabilities they didn't disclose.

How much damage has to be done before people wake up and realize that what NSA doing is effectively pointing armed nuclear warheads at high-value targets in the US and giving our enemies the controls? The fact that NSA refuses to disclose serious vulnerabilities is an indication to enemy governments and criminals that spending money finding these vulnerabilities is going to be an extremely effective tactic.

I mean this seriously: this is actively telling our enemies how to attack us. How is this not treason?

> Treason against the United States, shall consist only in levying War against them, or in adhering to their Enemies, giving them Aid and Comfort.
You didn't look at the fifteen second description of what Heartbleed is?
It appears Heartbleed has riled up the Hound dogs. It's unfortunate the funds aren't available for bug bounties in OpenSSL.
What matters in business is loyalty, not skills.

And what matters even more than loyalty, in this kind of game?

Contracts.

If this is getting ugly, and the company has a product/service that could take off and be worth serious money, your only friend is your lawyer, and your primary assets should words with some signatures underneath.

And if, heaven forbid, we're talking about a cofounder who doesn't have a rock solid contract, the time to fix that is right now, with the help of that lawyer, while leaving immediately still appears to be a significant threat to the business.
[straw poll HN]: which company (if you had to choose) would you a wear?
google,facebook,apple,twitter,reddit<p>http://strawpoll.me/1488926
Yeah, you're correct. So it seems that you don't need math to solve this challenge, but maybe luck and patience.
Not to be the buzz kill, but the reason raw.githubusercontent.com is text/plain and X-Content-Type-Options: nosniff is to keep people from using it as a CDN, because: it's not. The files aren't served static from github: https://github.com/blog/1482-heads-up-nosniff-header-support...

EDIT: I mixed up the move of Pages to .io, updated with the right blog post.
Hi Aldri - My company Thomas Street is building the project. You can reach us at hello@thomasstreet.com (and it's zackbrown and graunked on github)
Do you own half/part of the company?

If he wants you to leave you should still be entitled to half/part of the company, feel free to leave.

Do what YOU think is best for the company. <--

If for some reason you've been swindled out of owning half/part (or some portion, equivalent to the start-up split) of the company, I think you have a bigger issue outside the scope of this question.
To be fair the linked patch is very sparse and even so not everyone reads C, or knows what the Heartbleed code looked like. I can guess at what this is because some kind people provided a few good links about how bad memory management in OpenSSL is handled.
There are bug bounties for OpenSSL.

1. https://hackerone.com/openssl

2. https://www.google.com/about/appsecurity/patch-rewards/
Wal-Mart Grocery is Ripping you Off
I shop at the Wal-Mart grocery store in Plano Texas and have been using their self-service checkout for years now. Tonight things had changed. My first item I scanned failed to make a 'beep' sound, but charged me anyway. I looked at the employee overseeing these machines and said, do you realize I just got charged and the scanner never beeped? He said no it beeped. I said EXCUSE ME?, I was listening. I listen for the beep because the tells the employee i'm not ripping them off. So he comes over and voids the item and then scans it himself. It beeped. I joked that you have to program the computers to do that (charge without beeping). I insisted it was not an accident and that Wal-Mart was ripping people off. It's not a glitch or computer bug. So I said stand here and watch me. We scanned more items, about the 6th one charged me again without beeping. Then he tries to say "don't listen for the beep, just watch the amount." I said right, but it's not beeping on some of them. He DENIED IT even after SEEING IT HIMSELF. One of them he scanned himself, no beep, but he throws it in the sack anyway. I said, "see, no beep"... He claims he heard it beep!!!! Wow. Shockingly he admitted they had just done a software upgrade after I had told him I've scanned thousands of items and it has never happened before. Bottom line, Wal-mart is ripping you off by making you scan things twice because you'll keep trying until you hear the scanner beep. Amazing. Definitely fraud at the executive level. Boycott? Not yet, but everybody keep any eye on them... you could be getting robbed.
Unless you consider Watchmen literature
That's tough. Your last edit gives me the most pause: if you're good enough to be "desperately needed" for this critical pre-funding period, you should be good enough for after, too.

Don't sell yourself short: simply knowing your limits is a major skill, that will let you contribute where you can, grow where you can, and defer to others where you must. Also, having been involved since the start gives knowledge and perspective that can't necessarily be hired elsewhere.

Ultimately if you want to stay -- and especially if you still have the support of your biz cofounder -- you should insist on having the chance to grow with the company, learning as you go along. And the plan for the future needs to be well understood among the principals, before the fundraising, because that process will tend to firm up roles, equity, vesting, employment agreements, etc.

It's true that sometimes a member of the founding team isn't right – the commitment or skills or shared-vision isn't there, and perhaps the original title/status/equity even gets in the way of acquiring what's needed. But it sounds like you're humble and flexible enough that you should be able to retain a key role.

If you are considering leaving from, or think you might be pushed out of, a valuable position, you will likely want to consult with a lawyer, separate from the company lawyer, about how to best protect your rights. (The fundraising process itself, and getting the whole company/team into "standard" documents, could either work to your advantage, or make it very easy for you to be booted with very little, so educate yourself early, to avoid signing away anything valuable.)

If intimidated by the idea of talking to a lawyer, remember that many will give a free 30-60 minute initial consultation, so simply by the act of shopping around, always improving your 'executive summary' of your situation before each discussion, you'll learn a ton at no cost. (No two lawyers will have the exact same analysis, so the 5th or 10th you talk to may still improve your understanding.) And if you find someone you like, they may give you quite a bit of continuing good advice simply in return for the future-chance/option-value of representing you in a future dispute.
If bribery is necessary for me to receive good service, then I will use bribery. Paying a bribe does not violate my moral code (although demanding one does) so that is not important to me. What is important to me is correctly getting the order that I payed for in a timely manner.

For the record:

Bribery, as you describe it, is alive and well in America. My brother wanted to go to the Naval Academy. In order to be accepted, he needed a nomination. How did he get a nomination? He volunteered for the reelection campaign of one of his senators.

Asking your senators/representatives for help expediting the processing of documents is fairly common too.
Python and Django hackers wanted to help fix health care
Are you good at seeing the products that need to be created? Writing 'running specification' code (hacking things up)? Do you understand the product space well? Who owns product? Is this something you do or could do? How good is your relationship with your cofounder? There is a lot more that involves tech understanding to be done in a startup than architecture, coding, and managing architecture and coding.
The original link didn't mention this was an excerpt from Flash Boys so I had no clues Michael Lewis wrote it. I've never read any of his books. Now I want to because he actually writes pretty well.
Application of research methods before breakfast? good man.
FWIW, he may just have been saying exactly what the OP says himself:

"I have improved significantly in the last few months from where I was (generally unstructured development, no tests, poor formatting / naming etc., but functional, generally coding to working with others instead of by myself) but he has said that it's not enough.

We have hired another coder who I get along well with and I have learned from."

There's quite possibly a good argument to be made saying "this guy shouldn't have commit access to our code base" and it's not beyond the bounds of reasonableness to read into that "a few mid level developers under normal CTO oversight will give us a much better starting codebase than this guy is likely to deliver without significant extra training and experience".

Not saying that's definitely the case, but it's certainly plausible. (And I've seen it before, more than once... Hell, I've _been_ "that guy" myself, back in the day.)
If you are a founder:

- Are you needed?

- yes: then stay.

- no: Do founders hate me?

- yes: get the legal stuff ready, leave with compensation.

- no: Do you have future plans for contribution?

- yes: then get to work!

- no: Do you like your job?

- yes: then get back to work, make contributions.

- no: then why are you asking this question?

I also think that having a CTO does not mean there can't be a technical founder. You can find other things to do, such as build product roadmaps, and with basic technical understanding, you could make positive contributions, not through lines of code, but through the bigger picture.

Reading your post sounds like you don't have self confidence, but you got to find your edge! It doesn't have to be coding. There's more to a startup than lines of code, and if you were there since Day 1, you've already done much more for the company than the CTO. Feel better about yourself, and take a pivot on your perspectives.
Is this not like you build a house, hire someone to live with you since they can build/extend this house even bigger, then they tell you to get out of your own house? I still don't understand how someone he hired can throw him out of his company?
> "that yellow mathematics book"

replace "that" with "those" ( http://en.wikipedia.org/wiki/Graduate_Texts_in_Mathematics ).

the dover books are also a good series, and pretty much anything by Artin is good. i also looked at the Halmos book a couple of people have mentioned.

perhaps one thing to be aware of, though, is that you're not always going to learn things in the linear way they're layed out on the page. moreover, it might be helpful to have more than one book for any given subject. Lang's Algebra, for example, is a really good reference, but a tome if you read it like a text. so you might pick up something small and subject-oriented with a lot of exercises like Artin's Galois Theory or Atiyah's Commutative Algebra, and supplement it with a reference like Dummit and Foote or Lang's texts on Algebra as a whole.

oh, right: whatever book you choose, do the exercises.
Also, using an external CDN will end to more downtime.

You'll never benefit from having your CDN up if your own servers are down.
That is rather irrelevant. While I could reward the UPS delivery guy of the week with a few dollars, the offer would catch him by surprize. Tips cannot retroactively improve service; they only improve service if you are a recognized repeat customer, or if they are common.
Navy's Future: Electric Guns, Lasers, Water As Fuel
What really makes sales taxes fun in the US is that they are variable in many states. If I go to my local Walmart at the start of the school year, some items I pick up may be tax-free because they are considered school supplies and there's a "sales tax holiday", others items are considered "Groceries" and will be taxed at a reduced rate, but prepared (hot) foods, booze, and non-food items are taxed at the full rate.

Then there are the cities and counties that have additional sales taxes.

When I lived in Germany it took me about 5 minutes to fall in love with prices being listed inclusive of taxes.
Why would you expect anyone in that position to expose themselves publicly? Although they could give useful feedback, it wouldn't be in their interest to deal with these issues outside of a formal process. Unless of course it's in their job title to handle developer relations. Even then it'd be more setting up coordination and less anything technical.

Granted without knowing what exactly that process could be accessed or what it is, I agree that you need to do something to "start the conversation." However, attacking is unlikely to achieve the results you want. This is especially true considering the imbalance in your relationship with Apple. I've worked a number of years in enterprise software and for large enterprises. You have to learn how to bring attention to issues and escalate them constructively and professionally. You also learn that you don't always get what you want.

Do the blog posts but be aware of the tone. Use the mailing lists. Get others to raise their voice and show that it isn't an isolated incident.

In the meantime, since the issue is out there and details are known, workarounds need to be figured out that can be implemented. Short-term, there should be things that can be done by app developers. Longer-term, a solution probably needs to be put in place in the project that will address the needs of both app developers and Apple. (Apple dropping use of the project may be a possibility but I don't see that as a win for anyone.)

Also realize that an app developer "losing an entire afternoon" is minor in the grand scheme of things. However inconvenient it may be to be that developer, unless it's an absolute show-stopper, any reaction or solution will take time if one is implemented at all.
That doesn't help too much. You're mostly just stating advantages/disadvantages of one design over the other, without explaining why this should be correlated so very strongly with manual/autonomous control.

> Autonomous helicopters are multi-rotor for simplicity and reliability

Simplicity (less upkeep) and reliability (safety) seem more important for expensive, manned helicopters! So this argument, on its face, contradicts what we actually see. The only argument working in the right direction is something like "simplicity for tiny vehicles (which are necessarily unmanned) is important because number/complexity of parts makes up a larger fraction of total cost compared to large vehicles where raw materials dominate".

> Piloted multirotors aren't as popular because they need computer control to be stable

Large helicopters are expensive. The computers necessary to stabilize them are going to be just a tiny cost. On the other hand, for a drone the computers could be a sizeable fraction of the price. So, again, this argument appears to go against reality.

> batteries don't scale well,

Then why is this truck-sized vehicle (presumably using internal combustion) a multi-rotor?

> and combustion engines have slower throttle response

Ok, so this is close to an answer. The (weak) argument would be "humans want quick throttle response but robots don't much care". But this isn't too convincing, as I could easily see it being true that humans are better able than robots at compensating for slow responses.
See also everydayimmirror.in : https://github.com/jbourassa/mirrorin
I don't find it so odd.

If you read more than a few interviews with professional writers of literature, you'll see them mention how they don't read much fiction but a lot of non-fiction.
The Next Steve Jobs
Hello Hackers,

I have decided to become the next Steve Jobs.

Cai GengYang
This is your company. Not the CTO's.

It's time to have a frank discussion with your co-founder and decide what is best for you and for the company.

It may ultimately be best for you to step down, but it shouldn't ever be because of your technical abilities, and it shouldn't be because the CTO believes you should.

There are lots of things you can be doing, and the fact that you CAN code (even if it's not high level) is huge.

There is testing, blogging, social networking posts, Google Analytics, SEO/SEM, recruiting, buying office supplies, soda runs, customer outreach, marketing, more testing, design, investor outreach, product management, program management.

You have so much that you can do, that unless you are a liability (past convictions by the SEC), or so caustic that you are the direct cause for the companies failures, that you still have an important role at your company for many years to come.

And if you do stay, it's time to put the CTO on notice, the CTO works for you.
There are plenty of other examples from America, including vintage Ford Mustangs, Winnebagos, Converse tennis shoes and Baseball. I spent a couple of years expatriated to Japan and learned that for a Japanese person to admit they had a hobby or interest actually meant they were expert with it. You wouldn't admit you 'enjoyed playing violin' in your spare time unless you were a maestro. If you were not an expert, you would not talk about your interests. If a Japanese colleague mentioned they had 1966 Mustang, you could be certain it was perfect. For many Japanese colleagues, if I spent enough time drinking with them, I'd find a surprisingly intense sense of pride and mastery in an obscure area of interest. You'd never know about it unless you spent time enough to get past their modesty so they'd talk about it. I'd venture that this is the source of the author's observation about not just copying, but improving.

There were also some pretty twisted counter-examples of not getting Americana quite right. I ran across an outer wear store named 'Violence Jack Off', display windows crowded with black leather jackets.[Edit]
Cool site, but I'm talking about a guide that doesn't overwhelm you and guides a user through the process of improving one's fashion.
My personal thing is a landing page I am putting up for personalized chopsticks: http://i.imgur.com/DyFIItZ.png

Hopefully I can get it launched next week and see if I can get some orders. I used these chopsticks as an extra gift to current customers and they seemed to like it and were wanting to order more, so that's why I decided to work on a separate page for those.
Offensive work and addiction
Cool idea!

Isomer, an isometric graphics library for HTML5 canvas.

Screenshot: https://cloudup.com/ca2TeFocl6F

I'm _almost_ ready to release. I've been working on the docs here (http://jdan.github.io/isomer/), but the code is still private.
It's good to see that one of the positive effects of Heartbleed is that it motivated people to inspect OpenSSL's code, leading to more bugs being found and fixed.

This is supposed to be how open-source works; it's unfortunate that it had to take a huge vulnerability to cause this motivation.
I think it is a feat to practice to the point of having seen thousands of problems and still know (or have a felling of) the way to go.

(Actually, most of the good sport coders that I know develop that knack of knowing where the solution is headed, without pinpointing a previous problem)