skysight-inc/HackerNews huggingface dataset:
I agree this would be a major problem. It's one of the biggest problems listed with unlimited vacation, and that's when you're still getting money for it.

I think the underlying problem is the conflation of hours worked with value to the company. I think most people will be more productive for a company working reasonable hours for at most 50 weeks a year than working all 52 (minus holidays in both cases).

Accordingly, I think it is appropriate for a company to pay you to not work some of the time. I think that fits with your suggestion pretty well: give an employee 4 weeks PTO (or whatever you think will optimize their productivity and happiness), with the option to take more UTO that might not be an upside for the company.

edit: There should probably still be some reasonable cap on the additional UTO. Not pay their salary during vacation still doesn't account for fixed costs like health insurance and office space. In practice I don't think most people would take enough UTO for this to be a real issue, especially with the work culture in the U.S.
Nice bit of nostalgia considering assembly courses at Northeastern University were MIPS/SPIM when I took them back in... 1992-ish? Was an easy-A class because I had been programming in 6502 and then 68k assembly for years before, but SPIM gave me great respect for the power of virtualizing a system you are developing for.

And MIPS is still a great instruction set to learn the basics on.
Many wireless routers run a MIPS architecture, for one.
In today standards learn MIPS can be a good bridge to x86?
I built QueryTree (http://querytreeapp.com) as a response to this sort of problem. It's a domain specific visual programming language designed for working with tabular data. So people who want to build a custom query on a database can do it just by dragging and dropping the right "tool" onto the "worksheet".

It's a desktop app rather than web, although it is actually built using HTML, canvas and JavaScript.

It can do almost anything SQL can. It can't do "IN" queries yet but I have a plan do that in a way that's consistent with the general drag and drop approach of the app. It doesn't explicitly handle BETWEEN queries but they are easily achieved by using two filter tools one after the other.

I think there are two types of complexity to be dealt with when enabling users to build reports/queries. One is the complexity of the concepts involved, the other is the complexity of communicating what you want to happen to the computer. I built QueryTree because of a belief that many people understood they the concept of a filter or a join, but just didn't like text based programming languages. I replaced the SQL syntax but left everything else in place. If I didn't think my target users were up to understanding the conceptual complexity I would have restricted it a bit more and would probably have ended up with something like IFTTT.com but for data. Mostly, people seem to "get" QueryTree though, especially when they're using it on data that they're familiar with.
there are a lot of query builders out there, i'm pretty sure you dont need to write one. Doctrine has one :

http://phpcr.github.io/

which deals with pure PHP objects.it follows a java standard,you can write SQL like queries with it.

https://github.com/phpcr/phpcr-docs/blob/master/tutorial/Tut...
Haha :)

The title could be qualified with "in our company", but then nobody would read it! ;)

I love F#, but I'm not sure it's currently getting the love it deserves from MS :(
Vast majority of wifi routers use MIPS. I believe the Chinese longsoon processor is MIPS-derived as well.
Archimedes would approve.
Will this just make the tax return process simpler or will your AI assist in finding the loopholes that the wealthy exploit?

It would be fun to see everyone claim deductions on dog food the same way a rich guy might deduct on his horses.
for println(...) it should show in a black console like at the bottom.

For inline values, it shows in an orange comment //> value

e.g.

1 + 2 //> 3

try changing it and pressing the green button

Thanks!
Bloggers. I use photos every day for my blog (usually screen shots I take myself, or Flickr cc) but getting free stock photos emailed to me weekly is an interesting alternative. I've signed up for a couple of these sites based on this list. Thanks to the OP.
I've got the book 'Learn you a Haskell for great good' and I've gone through it. But to be honest I've I have always resonated more with structural languages than functional ones.
We use Phabricator at Bloomberg and I'll take the opportunity to shamelessly plug the add-on tools we've open-sourced to make working with it even easier:

https://github.com/bloomberg/phabricator-tools
A lot of routers still use MIPS, and a fair amount of special purpose embedded systems. I still have a few now somewhat aging MIPS SoC development boards from chumby, though we never put out a MIPS-based product.

Not a lot of general purpose use anymore since the golden age of the SGI/N64/PS2/PSP.
Have you heard of Nimrod? (http://nimrod-lang.org)

Compile-time wise it is very impressive (the compiler which is self-hosting compiles in under 30 seconds on my computer). It also resembles Delphi and Pascal in some ways and I am personally very productive with it.
many of the concerns the op had where with marketing of the f# ecosystem.

For example the tooling issues he mention are solved with a Visual Studio Extension

http://visualstudiogallery.msdn.microsoft.com/136b942e-9f2c-...

His concern with Roslyn seems like a non issues, a f# compiler is also opened sourced and was written in f# on day one. And there are many tools already taking advantage of it being open. So in this regard f# is farther ahead in c# in rubric.

As far a c# being ahead of f#, its funny, as most of the new features the are being added to c# seem to come from f#.

The op approach to hiring dev seems backward to me, you hire smart people and train then on your tools. There are so many good recourses for learning f#, having candidates without f# on their resume does not seem like a issues.

over it is great the he was able to bring f# into his environment. as more people adopt f# for there needs knowledge will spread and his concerns will fade.
It's true that the grid has to balance its own generation, but that happens today - the frequency of the mains changes constantly, and it's the grid controllers' job to bring on supply as required. There are some storage options - pumped hydro for example - but I absolutely take your point that the grid is designed for a classically understood demand/supply environment.

Certainly there is a risk that all these intermittent renewables will end up causing the most dirty of generators to be spun up more often, in the least efficient usage pattern.

The dream has to be a proper demand response system, with electric cars being a key sink for excess generation.

The work of David MacKay at Cambridge University is excellent on this topic: http://www.withouthotair.com/
Because American companies don't do any training.
Only in america would you see this frankely crazy line being run.

1 Your pay is not tied to how many hours you work as we are overwelmingly talking about sallried profesionals on HN.

2 Your pay is calulated including the holiday stautory and or other wise.

3 you are not getting a bonus by geting paid holiday - its part of the package.
Ahh... please leave this in as an option. The funny terminology is one of the best parts of Phabricator! I think removing this is sad...
At least you have the chance to debug everywhere. Current native tools often are just fundamentally incompatible. Even if we just had hacky cross-os standards that'd be better than nothing.
+1 for the 'Ye reference.
I can confidently answer "yes" to this question, because Tachyus, the first Silicon Valley start-up in the oil and gas industry, http://dealbook.nytimes.com/2014/04/10/tachyus-a-data-start-... , chose F# as the core software language. How did this work out? We went from absolutely no software written to deployed as the core operational software of a regional oil production company in 12 weeks. Our management and our customer's management are so happy with the results we are "all in" and not looking back.
We learned MIPS and wrote a compiler for it. This was in 2002, so the compiler was in Java. Still a lot of fun. What were those two tools? LEX and YACC? Nostalgia.

(Had to look those two up, I remembered them as LACC and YEX)
Enterprises are not using Qt.
I guess I just prefer my tools to stay out of the way
What's wrong with having wifi onboard? You don't need to have it turned on.
I reject the premise of the question. For the most part, I find HN far more usable than most web sites1.

My operational definition of "usable"? It is easy and effortless to scan headlines, to scan articles, and, when I find something of interest, to switch mentally from scan to read mode. And - and this is very important to me - it works well with the FF extension I use to mark all unvisited links as read, so that I don't notice them next time1.

Most other web sites are simply too busy, too loaded, trying to hard to impress to usefully support this scan, open-in-new-tab, then read mode of operation (I still do it elsewhere, but it requires more effort on all other sites than HN).

Is HN ugly? I honestly have no idea. Maybe it is, but it stays out of my way, so I don't care.

1 use hckrnews.com to find articles to read - by opening in new tabs - simply because it has more articles on one page than HN; really, that's it: If the main HN page was longer, I'd visit it once, just like I do with hckrnews.com, then alt-f2 to mark all as read - as it is, I have to scan-open-altF2-next-repeat, which is tedious. Not effortful, but not seamless, either.
Could you elaborate? What is wrong with Qt?
"The difference is the company isn't legally forced to grant me the same rights to their modifications. "

Yes, so GPL fans go by "today me, tomorrow you" and this BSD-fans go by "freeeeedooom" but then dont really put their code in public domain - instead maintain their copyright over it - which grants them the rights to revoke or change their license at any time.

BSD-license can be revoked by the copyright holder you know.

So if all these BSD fans really are "freeedooom", please public domain everything.
I have this vague recollection that for a while, MIPS was sort of in the running against ARM for more things, but has now been pretty much completely squeezed out of certain markets, like phones.
I really would love to go the immersion route, but just cannot do so. In my 20's, I was always far too poor. Perhaps I should have gone the student loan route and tried harder then, but unfortunately I didn't.

In my 30's now, I have some money; but I'm also married, have a stable career, a home, two cars, etc. The best I can hope for is to simulate immersion as much as possible. Watching TV Japan, playing games, listening to music, etc.
I still use the redmine which supports git well for me, for all my software stuff plus acting as a nice project management tool. I wish it's not developed in Ruby, so I could have one less language(and its dependencies) to maintain on the server side.
how does this compare to redmine, or gitlab?
Well, when I say that they retrofitted unicode elegantly, I'm ofcourse comparing it to how unicode was retrofitted into PHP. Elegant is in the eye of the beholder I suppose.

The same goes for maintainability. Upgrading the codebase was a sizeable effort for sure, but in my view it was less than it would have been had it been developed on another platform.
The problem is that you can't just take an inherently centralised asset and sprinkle some blockchain on it to make it decentralized. If an asset is backed by a vault of gold bars, it is inherently centralised because the gold is in a central location and has counterparty risk as well as being prone to confiscation.

In this case, there is no point in representing the asset in a blockchain. The blockchain is probably the least inefficient datastructure we have seen in modern times. A centralised asset is much more efficiently represented by a centralised ledger. You can still use triple-ledger accounting.
I love MIPS, wish it did better in the commercial side.sigh.
Actually (and I am being ultra-critical here, but that's sort of the point of this, right?), [0] sucks a lot more than [1]. On [0] the white balance is all fucked up and the composition is lazy, there are also some annoying (yet easily fixable) technical issues due to the resizing (like the banding in the sky color).
A Solution For Graphene Production
Not bogging down your service with unneeded features is a feature in it of itself. And often times the best feature.

Also, ditto with it not being the rule that customers know what's best. Customers are for the most part good judges of their own happiness, but it's a heuristic, not a hard-and-fast rule : take it with a grain of salt. If you know what you're doing, you, as the designer of the product, should know more about it than the user, the layman who uses the product, so you know what'll be the best in the long term better than the user.

But another thing about being the designer of the product is that you spend so much time with it you start staring at it from a millimeter away, losing sight on the grand purpose. It's something you can't prevent even if you're aware of it; as the artist, it's your job to focus on detail. It's why programmers initially thought Dropbox was just "rsync and ftp with a neat UI, what's the big deal?". The more you focus on detail, the less you focus on the big picture, which is an important perspective to have -- which is why it's also important to keep tabs on what the user says h/she wants.

They hated the News Feed when it was originally released and they shat on the iPad when it originally came out.

But they also thought OK Soda would be a good idea.

Maintain a balance.
I'd think this is because in a bad job market, people are sold the idea that getting an advanced degree will expand their opportunities later. Unfortunately not many people know that obtaining a PhD != easily finding a job afterwards.
What's with the high-pitched noise in the videos? Is that coming from the robot or the camera or what?

I'd like to see this robot be built: http://youtu.be/cU-cO0RvpwQ?t=23m31s FlexBot by Jamie Hyneman
I did mention that extension; and the bug I found right away :(

Roslyn isn't just about being open source; there's functionality like the Diagnostics/CodeFixes that make it trivial to do some really useful things, which are significantly harder using the F# source.

Overall my conclusion is not that F# is bad; I really love it; but there are some niggles for me still... Mostly around the level of investment from MS :/
One of the things which we decided when started up was to not use any stock photography. I think we have mostly managed. Instead we focused on taking a lot of pictures. It feels to us, and we hear a lot from others, that it gives a genuine voice to our comms work. Which is really important for us. The photography is spread over a number of Flickr accounts, but we know where it is.

My colleague Mark has a bunch of it: https://www.flickr.com/photos/charmermrk/collections/7215760...
You as a user may work for a company which feels it can't afford the risk of GPL-licensed code getting into their products, and may thus forbid you working on GPL-licensed code while you're working for them.

Or somewhat lighter but no less bad is the case where your workload could be eased or better results achieved by incorporating BSD-licensed software into your company's product where your company feels it couldn't allow GPL-licensed software.

These cases show the GPL is better for hobbyists than working people.

Then there's the fact that the GPL doesn't restrict the authors of the software. Some companies release under the GPL to get fixes, features, and kudos from the open source community without making life too easy for their competitors.

Overall the GPL does do some good, but it's certainly not freely giving to the world in the way MIT and BSD licenses do.
unlimited PTO is saying that "we would like to give you something that you can't potentially use". the sad reality is that in countries like France or Brazil where you have 30 days, it is actually guaranteed that you can take that many days off, while unlimited PTO startup employees end up using 10-15 days per year of the "unlimited PTO". it is like a bait to get more people to work for them without actually giving anything. I would argue that we need 4 days work weeks that would be fair. The reason why we have 5 days is purely based on the greed of the corporations. if i open my startup I am going to offer 4 days workweeks instead of unlimited PTO, that is a better way to respect your employees that giving a useless bait.
upvoted based on the sentiment of the title (because what to do with things that suck? make them better.) and domain name alone. there are similar listings at http://suckless.org/sucks and http://suckless.org/rocks . i found a pdf viewer called zathura as a result of that site, and it's been really useful (despite pdf sucking as a whole vis. djvu).
> At least you have the chance to debug everywhere.

Good luck with mobile and set top box browsers.
I was working on such system for performance measurements. Basic assumption was that user would never see any mention of tables, joins, column names nor any other SQL concept.

1.Table selection - there is predefined set of joined tables we call views. Views have descriptive names e.g. 'Temperature measurements', no underlying tables are shown.

2.Column selection - user selects columns from views using descriptive names , not actual column names . UI clearly indicates columns that land in 'group by' section by calling them dimensions. There is predefined aggregation strategy for all columns that are not dimensions - e.g. average for temperatures or sum for number of measurements. In some cases more that one aggregate is available e.g. average or maximum temperature. User just selects maximum or average temperature not aggregation operator.

3. Filters: user can select simple filters on columns: =<> and string matching for text. All filters are ANDed

4.Sorting: user can select columns to sort on.

5.Display: results are displayed as tables or charts. More that one section may be placed on single report.

The real system has tons of additional features but basic design as design as described above has worked great for years.
Interesting tool.

I'd use it, but perhaps I should first help you fix a couple of things.

1) Go into beta. You need testers first. Give them the stuff for free.

2) Don't link me to documentation to learn more. Create simple, easy-to-ingest screencasts/videos/pictures that I can quickly understand how the software can help me.

3) Build stuff with it. Time is a major sell point for developers who are tired of spending 40 minutes getting some package to work before actually writing code. Show me how I can build Twitter in 30 minutes and you have a winner.

4) Don't only focus on startups. A lot of other companies like APIs these days. Showcase the versatility of your product to big corps/medium-sized enterprise/NPOs/etc on how they can easily get their APIs to be accessed on multiple platforms.

5) Make it easy to get my data in and out. Nobody likes a lock-in these days, so make things more "open".

6) Understand that this is a crowded marketplace. There's a ton of variants around, with Parse/FireBase/etc all competing in a market that feels a bit crowded to me.

7) Target frontend hipsters/lovers of all thing JS. I may sound coy saying it here on HN, but deep down, that is how they are identified as a niche, so target them.

Hope that helps.
This is how most exempt jobs work in the US. Paid vacation but untracked personal time. generally speaking, untracked overtime offsets the cash value of the benefit, which is sort of the point.
>I've used awk extensively and am aware of everything you've told me. I never said awk was analogous to sed, they're quite different, which is why you'd use both, as I mentioned.

I can't see any way to parse your statement such that it matches your claim of being experienced. Either you feel sed is on the same level as awk and rc, hence mentioning it together with them (unlike say, ls or grep or any of the other commands you didn't mention) as being one of the tools you would use instead of general scripting languge X. Or you meant using them together for one specific task rather than as a general "sometimes you would use one, sometimes you would use the other". In which case you don't realize that there is no reason to ever do that since awk can already do everything sed can.

>I've not used the rc shell

That's precisely what I pointed out was a problem. "I have no knowledge of one of the things I am comparing" is not a rebuttal to "you have no knowledge of one of the things you are comparing".

>My comments apply to all of those

And all of those are listed in the same category. This makes it rather self-evident that yes, he considers rc to be significantly different. Hence my suggestion that you try it and find out how you feel about it, rather than just assuming it is the same as bash.

>Also: plan 9 is Unix-like

No it is not. Linux is "unix-like". Plan 9 is a completely different OS, designed as a spiritual successor to unix, which was seen as having been corrupted. It is no more unix-like than windows is dos-like.

>So yes, it's a new(ish) thing with a naming conflict with something already well-known.

I never said otherwise. You asked "who names something new on Unix 'rc'?". I pointed out the obvious fact that it simply isn't the case. It is not something new on unix. Being upset that an operating system has a two letter command that another operating system also has is silly.
Murdering a Meme: A Case Study in Promoting Cultural Diversity in Online Forums
Very nice introduction! MIPS assembly was part of my OS II course at the university back in 1997.

Never used it afterwards.
Chasing SSL certificate chains to build a chain file
Autocomplete of entire Linux kernel using Redis's new ZRANGEBYLEX
Nice work.

Scala worksheets are a joy, REPLs in comparison are quite weak, IMO.
check out the Algorithm Design Manual by Steven Skiena. It's fun, accessible and very practical.
Probably because it's not as popular. Given enough popularity, anything will start deviating from its originally clean and pure design and turn into a monstrosity...
While it may almost always be in the company's interest to have employees well rested, sometimes employees want to schedule vacation that can't be rescheduled at a particular time that may coincide with an important deadline.

In this situation, you run into some awkwardness that could screw over the employee.
Agreed employment law should be reformed and have one binding federal set of employment laws instead of 52 state + Federal Laws.

with say 4 weeks stautory leave plus public holidays.

Of course thise meas a few less jobs for HR and lawyers but hey thats what you call a win win suitation.
What we learned from the current hacking attemtps