skysight-inc/HackerNews huggingface dataset:
Just some comments on what would it take to be usable, for me at least:

- two boxes, one with my company info (address, act. info etc) and same for the company that gets the invoice
- I see INVOICE text is editable - great, because I don't send out invoices unless they are paid, instead companies get "proposal" or "offer", and same stuff but with "invoice" when paid. This is due to tax
- Tax box that calculates on total amount

- Amount due -> Total amount

- Shipping and handling - it can be as an item though

- Item and description can be one box

- custom logo image - this is mostly due to formatting. Large BILLABLE and box right to it can be both for "my company" info and other company info. Box that is below BILLABLE could be committed or re-purposed for notes. INVOICE header can be a bit higher with information for: INVOICE (or OFFER/PROPOSAL, brief company info and logo)

- save as pdf

here is an older real invoice I distributed out (note it's in croatian though, but you should get an idea): http://www.vga.hr/temp/old_temp.pdf My newer ones are more leaner.
You're not going to get the money back. 'grellas may hop on and set me straight on that, but what I expect will happen in the best case is that by pursuing a wage claim you start the machinery that finally puts your employer into bankruptcy, whereupon you become a creditor, lining up with all the rest of the creditors who aren't going to get paid either.

Don't let my belief here imply that you shouldn't do anything; all three of your options are valid. However, in each of them, before you (a) get emotional, (b) burn any potential bridges (even treacherous, slippery ones), or (c) contemplate investing serious time or any money in this process, keep in mind that your outlook on this probably isn't good.
Where There is No Doctor (download link at the bottom of the article)
What I hear in the story is that Tom is feeling incredibly frustrated at having to not only plan for the company's long-term growth, but that he's repeatedly brought up the fact that you and Jerry's reactive strategies work to help increase everyone's workload. And this particular latest straw, in which Jerry not only agrees to extra work, but then tries to reassign it to Tom, is viewed by Tom as something only a dedicated crazymaker would do.

If I were in your shoes, I would hire a facilitator for the next meeting. An earlier response mentioned being on the same page as being very important and I have to agree. I think having a professional facilitator will help you, Tom and Jerry (wait -- Tom and Jerry like the cat and the mouse?) hear each other.

Good luck.
The intent is clearly to appear corporate. Given the start up nature of the book it will be interesting to see other responses.
There really is a ruby way of doing things and from the outside it is interesting but not something I feel like I would benefit from. Ruby moves fast and the community moves fast with it and this doesn't fit me well or the way I work.
A lot of senior devs are making that kind of money not because they are domain experts but because they have been in the same spot collecting raises for a long time. Those are the kinds of people my warning was intended for and I think a lot of these people wildly underestimate how hard it would be for a bright young somebody to walk in and do their job.

I'm not denying that older, experienced programmers with strong domain skills are in demand, of course. I'm just saying that beneath that level the competition is heating up.
I'm not sure we're at a point in the evolution of programming having been a viable career path for enough people yet to judge one way or another. There's not many people in their 60s who have been professional software developers most of their career, so you wouldn't (yet) see a large number of retired people "creating awesome open source projects".

IMV, the it was the tail of of the baby boomers who could have started doing programming in anything resembling what we might have today, and they wouldn't/couldn't have started until at least the late 70s/early 80s. When 'home computers' started becoming commonplace, 'programming' started to become an accepted vocation. Those people are now approaching or in their 50s, and still have another 10+ years to go before 'retirement'.

Frankly, I don't see that many 'awesome open source projects' compared to the total number of projects launched/opened. What I value more are 'awesome open source projects maintained and kept current'. I don't see many of those around at all, by young or old people.
If you allow this:

open("/fuse/sockets/www.whatever.com/tcp/80", "r+")

Then what do you do with these?

/fuse/sockets/www.whatever.com/tcp
/fuse/sockets/www.whatever.com
/fuse/sockets

They and other variations would each need different semantics, some allowing rw, some ro, some wo, and some not being allowed at all. Some path segments would not allow arbitrary names (tcp/udp, port number) while others require a specific format (host/ip) and others are arbitrary. Some have to be directories, some have to be files, and some are neither. None of this is very filesystem-like. I think the current design is right: opening sockets is kind of special, but you get a filehandle that is very much like an ordinary filehandle.
What is the difference between KVM and VMware?
VMware is a proprietary product. KVM is Free Software released under the GPL.

What is the difference between KVM and QEMU?
QEMU uses emulation; KVM uses processor extensions (HVM) for virtualization.

Perfect, thanks.
Amazing interview about the ups and downs of startups, and the shear determination of growing a technology seed into a powerful platform.
I like this experimental approach, it's like debugging, except you can also edit what inputs you accept. But is it actually accepted by mathematicians as an accurate description of what they do?
http://en.wikipedia.org/wiki/Proofs_and_Refutations

Even Alonzo Church published work that was later shown to be logically inconsistent http://en.wikipedia.org/wiki/Lambda_calculus
I came across
Very few 35-40 year olds are going to give up 75% of their income for any reason.

Nobody's criticizing YC here though; we're all just making the obvious point that YC trends young because people with established careers in tech make a lot more money in a year than many YC participants will see in several.
As a side note, one of the most significant updates included in Reason 5, which was released this past week, was the addition of live recording of samples directly into Reason devices and a more complete integration with Record, Propellerhead's audio recording package.
If you mean for the proxying, not yet. For the 0MQ handlers it definitely does, but some folks also want to do blocking before sending to the backends.

We've basically laid down the core features and then we'll start planning things like this. Page caching, different proxy backend schemes, filters, handlers, etc.
It should cheer you substantially to realize that you have come around to what I believe Patrick's way of thinking has been all along.
French Open Source Books
Poll: How many times did you fail before succeeding?
My ventures haven't worked out exactly as planned, and I'm wondering how you have made out.

For this poll, define 'success' as generating significant income; whatever that means to you.
Have never honestly tried
Haven't had success yet
Zero failures before success
One failure before success
Two-three failures before success
Four-Eight failures before success
I actually did start looking for a job right a little bit before the salary starting coming late. From the time I sent my first official "hey guys I'm looking for a job" email until the time I signed the contract for my next job was about 6 months. The operations of the company started smelling weird to me the longer I was there, plus I felt like I needed to be in a different type of position, so did start looking before things started falling apart.

While I was still getting paid, I didn't want to quit until I had secured a new job. When they were 1 month late with pay, that pretty much drew the line for me so I gave them 1 month notice at that point.

And yes, now I'm regularly updating my resume and keeping my eyes and ears open for other opportunities.
awk has something similar too:

The following special filenames may be used with the |&
co-process operator for creating TCP/IP network connections.

/inet/tcp/lport/rhost/rport File for TCP/IP connection
on local port lport to remote host rhost on remote port
rport. Use a port of 0 to have the system pick a port.
Two issues from my point of view:

1) You're owed the money legally. No question about it. You can probably even get it. California takes a very hard line on unpaid wages.

2) In the grand scheme of the situation do you feel good about fighting them over the unpaid wages?

#1 is easy. You file a claim. You have a decent chance of getting your money.

#2 is harder and it's impossible to know from the outside. I think it's perfectly reasonable to let people off the hook in some rare circumstances. Only you can make the call if this is one of those times. It doesn't make you weak or a fool to treat people better than they strictly deserve.

It sounds though, like you've already made up your mind that you want to go after the unpaid wages. So give them a final warning (written, certified mail, return receipt) and then file a claim.
You've identified one of the limitations of this service: it requires the musician to think about file size when creating a project. I agree that it is a serious flaw, but I do not think it is a show-stopper.

I generated 10 minutes of white noise and saved it as 320kbps mp3 and quality 10 ogg. The file size of each is 22.9 MB and 18.1 MB, respectively. Let's say we have a 10 minute long song (that's really long) with 4 layers, and you end up re-recording everything twice from start to finish. 20 MB * 4 * 3 = 240 MB for the entire project. That means in the Lite plan you get 42 songs. Sounds pretty reasonable to me.

The obvious argument is that as a musician, you want completely lossless compression. I say that quality 10 OGG is good enough, although if you simply cannot accept that, I understand.

Also, I have plans for creating a program that runs in the background of your computer and does all the dirty work for you.
On the contrary, I'm amazed at just how much of Africa is South Africa.

Out of maybe a dozen tries, I have had one African hit that was not in South Africa, and that was a Spanish-owned island off the coast of the Sahara.
وقت يوتيوب YouTube - انشودة كنت قاعده ديما بشار اعلى جوده طيور الجنه
I think the main point with testable views is that the default asp.net view engine is completely coupled to the asp.net runtime. It was impossible to instantiate a view engine instance and render a view inside the test framework without creating a special app-domain in which to host the test.

I had to wrestle with this just last week, it was a major pain in the ass to work around this limitation.
Thanks for your input tptacek. When I spoke with one of the VP's he also said that there wasn't much I could do to go after the money. But I thought he might be trying to prevent me from doing anything against the company.

What you described about kicking off the bankruptcy process is pretty much how I pictured it. They have implicitly made me an interest-free lender.

One of the hard lessons of life here for me is that I am really hesitant to trust any people in business now. I now understand why unions exist.
Sorry, that should be "While I don't disagree with your general point...."
Ask HN: which ebook reader to buy?
which is better, kindle or nook? Aesthetically, nook seems better, but kindle has far more books in its store and with Amazon behind it, its only going to get better.

Which one would you recommend?

Edit: Looks like nook has other apps (chess etc, I didn't know that). Also there is an expandable memory slot in nook, but not in kindle.
It's worth noting that if you do resort to pushing the company into bankruptcy, at best you'll get nothing, and at worst you'll make things even more difficult for the founders than they already are.
Thanks, that confirms what's been stewing in my mind.
There's also a non-binary approach -- exercise some of your options (i.e. not 0%, not 100%). Figure out how much money (e.g. $100, $1000, $2500, $10000?) you're comfortable losing entirely should the stock become worthless, and what percentage of your vested options that allows you to exercise, and use that as a starting figure. Then adjust that based on how much more risk you are willing to take because you really think the company will succeed.
There is no evidence which would make for good, rational reasons to keep the death penalty

According to you. If one murderer gets out and commits further crime, that's enough evidence for most people. If that further crime is murder, no additional discussion is required.
The one that inspired the author: No. 7 in A major http://www.youtube.com/watch?v=2UTAmV54OWE
I actually prefer this format http://api.rubyonrails.org/. Everything is there, and I can use cmd-f to search for whatever. It's probably because I'm familiar with it, but that's probably why you like python's.
Kurt Vonnegut On Plot Archetypes (2005)
"The guy is so passionate about his idea that developers and designers wanted to work with him, even before he had enough money to hire full-time coders."

So he's a Jobs, who found some Woz's to work with him.
I was underwhelmed after reading the title as well. Good version control software for audio on my PC would be great.

However while this might not be great for close collaborators, it would be very good for remix competitions and less structured collaborations. There is a bunch of sites devoted to these sorts of things, and this would have a huge advantage over them.
I learnt both Chinese and English as a child and all the way through my formal education (up to 18), and I must say, that the phenomenon of forgetting easy characters is pretty common.

Chinese, Japanese and Korean characters are ridiculously complex. The resultant expressive power is obvious, and it's no wonder why these are the few languages in which calligraphy blossomed into a fully-fledged artform, which I personally practice as well.

As with everything, we're going to artificially and naturally select the best language. I personally think that 'best' here is defined by flexibility and beauty.

Flexibility - no way would you have come up with a word like "globalization" in Chinese, it lacks the prefix/suffix system to do that. It also doesn't have the phonetic flexibility to include foreign terms like Japanese does. Eg: "Basketball" in japanese can be pronounced "baskeboru" but it's "lan qiu" in Chinese.

I think one overlooked point is that Chinese isn't a beautiful language, at least not in the opinion of youth today. It's conciseness has spawned some of the best poetry (i think) on earth. But as much as the French complain about how it's hard to sound romantic in English, it's even harder in Chinese (not to mention some of the dialects like Cantonese and Hokkien).

Kinda reminds me of how people despise Lisp (of which I'm also a fan of). It's an obscure language, but it's the most expressive one that I've seen, and will continue to admire it for it's beauty forever. That's probably the reason why it's still around after all this time.

Will the Chinese language suffer a similar fate to Lisp over the long run? I doubt so, since natural languages are a whole different beast. But the problems are real, and with more than a billion people potentially using the same character set, this will be interesting to watch.

---

TL;DR - Chinese is difficult to learn. It's not as flexible as English; you can add "ization" to "global" easily in English, not so in Chinese.

It's also not a beautiful language in the way that youth see it; Chinese makes for great poetry about the mountains and the ocean, but not for whispering sweet nothings into a partner's ear (at least compared to a language like French)
These guys are scum for letting you work blindly without 1) having any idea how or when they would pay what they committed to and 2) warning you they're circling the drain. They deserve to get nailed for it.

That said, it doesn't sound like you have a long employment history, so a cordial relationship and good references from them might be worth more than the money they're unlikely ever to be able to pay, no matter how you go after them. Consider hanging tight at least until you risk losing the right to claim your due (I have no idea if there's anything like a statute of limitations on wage claims or suits).

Good luck. I've been through "oops, we're about out of money, guys", but I was fortunate they were honest and ethical about it.
That’s not automatically a bad number. Japan has a ridiculously low incarceration rate (63 per 100,000 compared to 748 in the US and 96 in France) so it doesn’t seem as though they randomly pull people from the street and then convict them with near certainty. They might throw out many cases with less than airtight evidence.
I in no way said that the python docs were worse than the ruby ones, only that the python docs are really not as great as they could be. You already knowing everything on the page doesn't make it any less poorly designed. I find it much more preferable to be able to search for "python string" on Google and be brought straight to a page about strings, not about every type in the languages (Ruby[1] and Java[2] both do this sanely.)

The formatting within the python docs is also highly inconsistent. Why (on the built-in types page) do the operations on sequence types (5.6) get a nice table, but the operations on sets (5.7) have a poorly formatted list?

[1] http://ruby-doc.org/core/classes/String.html

[2] http://cupi2.uniandes.edu.co/site/images/recursos/javadoc/j2...
Did they approach you or did you approach them?

If they approached you, you're in the drivers seat, set a good cash price up front and do not rely on any money after the transfer has taken place. If they don't take that walk away. They'll be back, or someone else will be or you'll be left running your own business. Either of those are good.

If you approached them then maybe this is not the right party for you. Walk and try elsewhere. If you keep getting shitty deals focus on improving your product, grow the installed base and if you can start making inroads on the companies that you looked at to buy you out.
Fun tool. It's what I imagine living Quantum Leap to be like. ;)
http://www.openvz.org/ does what you want. The PID:s, network interfaces, and the like are all isolated, but you are only running one kernel on the whole system.

Xen might be work taking a look at as well.
They're about to go under if I'm any judge of this.

I wouldn't count on it going anywhere unless you become very blunt. They might be afraid to file for bankruptcy, you might get paid a bit if you threaten to sue, rinse, repeat as long as they pay up bits and pieces.

Until they go bust (which sounds like it is weeks or at most months away).
I don't feel good about fighting them over the money. This may sound weird, but I do want the company to succeed. However, I might feel worse if they flat out got away with it. There are several of us employees who are owed back salary and it was very unprofessional and un-courteous for them to keep us on the hook the way they did.

I think it would be a weak move to avoid it completely, but maybe not weak to at least confront them and then show mercy.

But I think you're absolutely right, nobody here can really decide for me.
The top comment has a remarkably good list of references. I like the nanopass and incremental papers a lot, RTT is a classic, and there were several good-looking references I had never seen. Almost makes me feel some jealousy at the pleasant vertigo the original poster must feel :)
I was in their shoes once, and it was a horrible experience. I had paychecks bouncing at the end, some tempers flaring, and overall was about as miserable as could be. I'd suggested that people start looking for other jobs - there was no turnaround in sight. This was just a group of 5 of us - not some huge office, so we were closer (physically, if nothing else) than some other larger orgs that have gone through this. To their credit, they stayed as long as possible, later than was probably prudent. That may have been partially due to the fact that few others in the area were hiring at the time.

Answer, you can try to sue, but there's probably very little chance you'll get your money any time soon. Whether you
want to pursue this or not depends on a few things. Do you feel they mislead you? Do you think they really have money and are just lying to you?

The flipside of my experiences was about 4 years after that scenario above, I did some contracting with a company - remotely (unfortunately) and they didn't pay. I found out from discussions that the PM on my project quit soon after I started, another developer on the project quit as well. He'd told me he'd quit because he was tired of the contractors bitching to him they weren't getting paid - apparently this was a habit company X had. I had other contractors seek me out and tell me they'd been shafted on payments too - one for $700, and another for $3500. Mine was to the tune of close to $9000. (never again!). So... I drove up to his state and filed a lawsuit. It's been > 2 years, and it's still in the system. Will probably take another year, and at that point, I'd still have to collect. At this point, it's a matter of principal - the company's whole MO was to farm out work to contractors in various states, then not send payment. That's a whole other level of evil, imo.

But maybe I'm biased and I really was as scammy as the guy who didn't pay me? I don't think so. I was honest with people - there's no money coming in - take another job if you can get one. That's not what happened to me a few years later, though perhaps some might see it as divine retribution?
Tptacek is right that your prospects may be slim if the company is truly on the verge of bankruptcy. But if it's treading water, or up-trending, or captures a new opportunity or investment in the near future, your odds go way up.

So be sure to communicate that you still expect to be paid, and keep documentation on the amount owed -- ideally also a confirmation from them of the amounts. Making an official complaint to state employment authorities should be a consideration -- but one you neither rush to nor wait too long to pursue. Ask an employment lawyer about your rights and any deadlines for asserting them that may apply.

So my overall suggestion would be: (2), with increasingly aggressive nagging that gets them on the record with excuses/acknowledgments, and makes them realize you'll eventually go (1), so they might as well pay you as soon as they can.

I'd also be open to a settlement for less, but not be first to mention the possibility. If their fortunes improve, and you then assert your legal rights before they expire, you might get the original amount plus penalties/interest. So you have leverage unless it's a blood-from-a-stone situation.
you should sell them.... to me
There is a 3-year statute of limitations in California on wage claims.
I have pointed this out in a comment on this thread but would like to repeat it in support of your list.

Myth #1: People hire younger workers over older workers because of the money. This is not true. Think politics and psychology first. People who move up the management ranks often have political or social skill superior to technical skill. They slimly don't what engineers who are more technically savvy or not subservient enough around. Not so the young greenhorns or even immigrants. Competent, seasoned engineers can't be as easily manipulated.

There is no substitute to experience, no matter the spin.

And often the obsessive coders pay little attention to the office politics. This leaves them exposed to the career obsessed suits. Politics and human dynamics first, money distant second, as always.