skysight-inc/HackerNews huggingface dataset:
How We Built GuruFoo.com – Lessons Learned from Our Recent Launch (Part 3)
Part 1 (https://news.ycombinator.com/item?id=9605966) and Part 2 (https://news.ycombinator.com/item?id=9605991) focused on the architecture of GuruFoo.com. Here are some of the lessons we learned along the way...

Understanding your platform is a must. Early on, we did some very simple SQL access, and basically just relied on what JPA provided. This was done because we were really focused on getting the whole of the application developed. In the end, we made heavy use of native SQL queries for some items. The performance was night-and-day compared to trying to shoehorn JPQL in there somehow. The same holds true for JSF. If you don’t understand the JSF lifecycle or how pages are rendered, you can end up really wasting resources. Unnecessary CDI Conversations, too much in Session, full-page reloads when you could’ve used Ajax… We’ve run into all of those problems and more.

Always spend a lot of time thinking about your application architecture. Design patterns exist for a reason. Conversely, anti-patterns are called anti-patterns for a reason, too! Case in point: The Open Session in View pattern for data access. We made the mistake of leveraging this early. While it does have its merits, we found that it masked a lot of latent problems in our architecture. Sometimes you want that transaction to commit right now! The result was a LOT of additional headaches and testing to pull that code out and replace it with proper transaction management and lazy resource loading.

Okay, that’s it for now. Please feel free to post your comments, questions, and especially criticism! See something you think could be handled better? Go ahead and say it! We’ve got thick skin, and always enjoy looking at things from a different point of view.

And, as always, we’d love for you to check out our site. Take a look at GuruFoo.com (http://www.gurufoo.com) and let us know what you think!
Given that there is no download link or price, I'm going to assume that 18F is not the kind of place that was going to pay top dollar for a cruddy, expensive third party service.
If I heard such statement in a debate I would stress that word harder.
my biggest problem with keyboard layouts always was, that with a german QWERTZ layout it was pretty much impossible to use (){}[]<> efficiently.

i tried NEO and DVORAK but somehow the english layout worked best.i still need to type umlauts (äöü) and ß, so i made a custom layout.

you can find it on github: https://github.com/bmaeser/coDE (osx only, sorry)
> battery life that would probably outlast 3-4 iPhones.

And functional life as well. iOS 8 crippled A5 devices which had previously chugging along quite decently. Planned obsolescence sucks (in iDevices' case, it also affects present performance, i.e. Safari constantly having to reload tabs because the device has little RAM to spare). Unlike a smartphone, a simpler device won't be reduced to be unable to perform its more basic functionality decently a few years down the road...
We make our money on support.

A nontrivial amount of bugs fixed upstream are found and reported against in-support versions of RHEL. But in a broader sense, there's no "immediate return on investment" pressure here.

We work with upstream communities. So there are upstream planning meetings which set feature development, which anyone is free to participate in, or we directly participate in apache/openssl/gnome/openstack/whatever meetings. New features are set and developed by the upstream product, where we (as developers) spend a lot of our time. We're not doing it in-house and pushing it back.

We try to make sure they're tested and stable through CI and QE testing (foo-1.2.3.noarch gets marked as the version in which bug #1234 is fixed in -- QE tests and verifies this before release).

There's some emphasis there because Satellite, Openstack, RHEV, and other "server" product entitlements and support are our revenue stream, but there's a significant desktop team, and kernel team, etc. We as a company are much less focused on what makes money and more interested in "what's the best tool for this job" and "how can we push Linux forward".

To that end, there's a heavy lean towards GTK/GNOME solutions over QT, but that's more culture than corporate direction. And there's a "disproportionate" amount of effort towards server products because that's what people use Linux for and that's what we work on, but the community drives our priorities, not the other way around. We're a relatively small company (for our revenue), and people work in one area. If I'm working on Openstack (upstream and downstream), pretty much all my effort is going there and none is going towards Firefox (or whatever). But being on a product team/niche isn't any different at Red Hat than anywhere else.
> Yes, but computers are not whats important in calculation. Algorithms are.

That's not correct.

> The physical properties of the computer don't matter in this regard.

That's not correct.

> You could do exactly what a computer does with pen and paper (it would just take a much longer time).

Yes, and that time matters greatly as it's the difference between practical and hypothetical. Beyond that, programs that can evolve their hardware have been shown to come up with optimizations no human could have created and thus the physical properties of the computer do matter.
>>> There are a lot of advantages to using web tech (cross-platform, easier to develop, easier to push updates)

Yeah. This shouldn't be overlooked. In some cases (solo founder, bootstrapped, etc) a hybrid app might be a great choice for v1.0. Sure, it won't be fast on the phone... But it probably will be pretty fast to develop and release on multiple platforms. Especially if you don't have experience in iOS/Android dev but plenty of background in Web. Sure, if it gets traction you should rewrite it in mobile at some point. But as a prototype, I am totally cool with hybrids.

I'd guess these are not the cases that the OP meant, but still I wouldn't say that the web lost. It has fair share of use cases.
I'm using arch, currently and it looks rock solid aswell, even that it is really really bleeding edge
I love companies that say they are "pre-revenue" as well as pre "product/market fit". In the infamous words of Kevin O'Leary you are pre-business, or what some might call a hobby.

Nevertheless, I don't say this just to rain on your parade. Businesses all start somewhere. But what you are saying is you have no cash on hand or ability to take on debt to pay for a software engineer to build your main product. Let's make it relatively clear, you cannot pay a person in equity in lieu of monetary payment. Why not? Because your equity isn't worth anything right now. If you have no revenue, no product, and no investment, you have no value. So if you were to "hire" an engineer who, at market value, might make $100,000 per year, how much would you pay them in equity? You cannot make the equation work.

So you are stuck with some other sort of agreement. You can make them a co-founder. But you don't want to dilute your equity. That's a major issue. The question then becomes how much benefit are you bringing to the organization in comparison to them? I've been asked this, personally, a number of times in my career. "Will you take 5%? If we take off with this production we will become a $1,000,000,000 company and you'll be worth $50 MILLION!" My answer, when the company is at your stage is no, I will not take .5%, 1%, or 5%. I will take 50%.

Of course, co-founders choke on this. But I have a lot of issues to weigh as a potential co-founder. First, often times the other co-founders aren't working on the product or the company full time. The aren't making any revenue and so how will they live without a second job? On the other hand, as an engineer, I must get that product out the door quick, so I am heads down full time. Second, this is a huge risk for me and I do not want my co-founders making poor decisions while I stand there with my tiny, non-voting amount of equity.

Some might say "But what happens when we need investors!" and this is a reasonable question which does come up. I give up a percentage of my equity to gain investors at the same rate as my partners. If we need to do a raise as 20%, I now have 40% and my co-founders have 40%. The math follows down to just about any level. We make those decisions together.

Anyway, I just wanted to give you the other side of this sort of discussion. Most entrepreneurs want to value their idea very high, while reducing the value of product execution. By sticking to my principles, I have been quite successful, starting 2 businesses and partnering in 2 others, all sold successfully. I hope you find the right fit for you!
> Using Angular is a bad idea, but lots of companies are using it anyway because The Herd stampeded towards the new shiny thing

The most ironic thing in all this is that your comment is still full of Herd mentality, except that it goes the other way.

Angular is a framework, period. Using it is neither a good or a bad idea, it all depends on the people who actually use it.
Indeed, that's why I think it's a mistake to copy native with problems plaguing it (when we don't know how to add these features without the downsides).

I'd prefer the Web to stay safe and hassle-free, and use native apps—with the risk of letting malware in—only when I really need more powerful features.
That's how I see it too. I try to at least stay aware of what's new but I don't dive deep until it becomes apparent that this new thing will be of use to me.

I imagine most here have day jobs with projects that last more than a few months so I doubt the need to learn things faster than your cycles of your job.
IIRC you can hit escape while booting to view the script output.
It would also act as a good filter from employers that I don't wish to work with.
Surviving in the Public IaaS Cloud Market
I've always felt that (with respect to desktop work specifically), the reason we're in the web-app world we are today was in part due to the stagnation of window management in the 90's - 00's Windows era. Tabbed browsing for web browsers was created pretty much to overcome having a gluttonous and unusable taskbar after opening just a few applications. From then on, I feel users were primed to want an alternative, which web apps ultimately gave.

Further, to talk about the speed hit associated with web apps, laptops and desktops are still primarily sold with old-school hard disk drives instead of solid state (unless you pay a big premium, which most people don't want to do). Frankly, opening a native application on an older machine (and for most users, one which hasn't been defragmented even once) was an awful waste of time. But Google Docs? Heck, you didn't even need to be on the same computer to access those files. Not to mention trying to update these apps being a massive chore on these slow machines. Heck, most people didn't ever update their browsers until Mozilla and Google imposed it upon users.

While I'd like a world where the browser is not an abstraction layer for an OS, I do recognize that these web apps exist for a reason.
"We now have the one true data representation format: JSON." huh?!!! We just moved from protobuf to JSON.
Show HN: Dock.ninja  host GitHub projects for short duration for demo purposes
Hello All, this is my first submission to HackerNews. It took me a lot of convincing myself before posting this entry here.

http://dock.ninja is a proof-of-concept application, to host git projects without project page for a short duration.

The intention is to save time:
1. instead of cloning a repo locally and hosting it just to know the workings
2. create a gist page and maintaining it

One sample entry:
https://github.com/lukehaas/css-loaders.git

As i am learning python & django, i tried developing this application as POC. It would be really helpful to get your reviews and feedback on this application.
I had a Nokia 6310i when I was younger, and on average (short calls, a few texts per day) the battery would last for 2 weeks. It had a small (but perfectly formed) black and white screen, a distinct lack of apps, and no 3G. All helps.

Interestingly, the claimed talk time, at 7 hours, was no better, and in fact possibly a bit worse, than a modern iPhone. Draw your own conclusions.
>>> Given that there is no download link or price

Like everything 18F produces, Tock is a work of the US Government and is in the public domain. There's a link to the GitHub repository in the blog post (https://github.com/18f/tock). We don't intend to launch Tock as a service, rather, it's something we made for internal use that is open for others if they find value in it.
http://math.stackexchange.com/questions/349155/how-often-doe...
Munchery Is Valued at $300M in New Funding
This just continues to prove that copyright law in the US is tailored to serve one group of people - those who already have a stake in the game.
http://ivory.idyll.org/blog/ is a good one if you're into bioinformatics and academic programming in general.
TeamViewer 10 Crack, License Code and Activation Free Download
I wish Vue were more popular. It has one of the nicest APIs of all the JS frameworks and offers good performance.
Tail recursion with asyncio
He means, I think, that method dispatch (i.e. function resolution) in Lisps is less dynamic than in Ruby/JS, where you resolve the call target by searching for the method name in a map -- at least as an abstraction -- belonging to the target object at runtime (or Ruby's method_missing). I am not familiar with all Lisps, but their method polymorphism is usually much more structured.
> Linux for me is very much a CLI-only experience.

What's it like in 1999?

>really do not need to deal with the random issues of Linux desktops (e.g. getting wifi to work, dealing with sound driver funkiness, getting drivers/off-brand productivity apps

Personally I have bigger problems with Apple products. OS X has all sorts of random issues(and even worse driver support). People like to pretend like Apple products "just work" but the reality is that OS X is just as buggy (if not more so) as Linux. The fact that Apple curates the hardware for their devices and has their OS coupled tightly to their ecosystem means these problems are inexcusable, they only need to ensure the OS works on around 5 models but they can't even get that right:

Sound not working after upgrade on OS X:

http://apple.stackexchange.com/questions/151045/why-is-the-audio-is-not-working-after-upgrading-to-yosemite

http://www.iphonetopics.com/no-sound-after-upgrading-to-os-x-yosemite/

https://discussions.apple.com/thread/6606695

[the list could go on]

Wifi not working in OS X:

http://www.macrumors.com/2014/10/30/yosemite-wi-fi-connection-issues/

http://osxdaily.com/2015/01/30/os-x-10-10-2-yosemite-wi-fi-problems/

http://fieldguide.gizmodo.com/the-worst-bugs-in-os-x-yosemite-and-how-to-fix-them-1652690924

[the list could go on]

Upgrade disasters:

http://www.macworld.com/article/2837811/bugs-and-fixes-solving-a-yosemite-post-install-disaster.html

http://apple.stackexchange.com/questions/161368/mac-os-x-yosemite-broke-my-imac

There are over 500 Ubuntu Certified PCs whereas there are ~5 current Apple models.

It's astonishing that apple users go out of their way to buy specific hardware just to get OS X up and running but refuse to do the same thing for other OS's, then go and claim that OS X "just works". I assume most apple users attempt to install Linux on their macbook only to find that Apple has made this process extremely hard and deliberately chosen hardware that uses closed source drivers that are hard to get on other operating systems, then they blame Linux.

Imagine if the situation was turned around and you were trying to install OS X on your Ubuntu Certified PC. Would it still "just work"? I'd wager installing OS X on anything that isn't a mac is a bigger headache than installing any other OS anywhere.

It would be like me building a custom computer, creating my own OS that only works on that computer, and then claiming my OS is good because it "just works" on my one specific machine.

OS X has the worst hardware support of any OS. You can get better hardware support and a computer/OS that "just works" by taking the time and energy you took to buy a PC specifically made to run OS X and use it to buy a PC specifically made to run Linux.
Check out: https://qzprod.files.wordpress.com/2015/05/powerbankphone4.j...

It's 10,000 mAh.
As a former subcontractor that was forced to use Deltek for a couple years, I will agree that it's the most popular... but I haven't the faintest notion of why. It wasn't the worst option available, but that didn't stop it from being terrible regardless.

Time-tracking keeps getting reinvented because no one's solved it definitively yet. I don't think anyone ever will, either; time tracking relies too much on individual context for it to be wholly standardized.
Self-publishing AngularJS book – Q&A with author Tero Parviainen
When did having my own data stored in regular files become "strange"?

If the data is tied to a browser, how do I back it up/save a copy of it? How do I persist it when the browsers local settings/cache are cleared (either by clearing or eg. when the OS is installed)?
Refactoring to Microservices
Ah, the golden era of RealPlayer.
I think he was referring to Deltek, not Tock.
They dropped Upstart for systemd in 15.04, after the decision was already made over a year earlier. They're also going to replace it in Ubuntu Touch as well.

It's worth noting that Upstart came at least four years prior to systemd, so it wasn't NIH.
Maybe I'm misunderstanding something here, but I don't think the argument is to cede the web to documents, but I also don't think the idea is to cede all functionality to apps.

I think the problem is the hype about native apps and everyone wanting an app without understanding their purposes, utility, and unique characteristics. There are situations where a web app / site is the exceedingly more appropriate solution, but there are other uses where a native app is equally exceedingly more appropriate. The problem is that people are having a difficult time discerning the two and the appropriateness of each.

I don't agree with this article and the sentiment about the critical question being whether people want your icon on their homescreen as being the differentiating characteristic. What is not discussed is the possibility for putting the icon on the home screen as a link to a web view that can function the way a native app can function. It even addresses a question regarding distribution if you simply ask your user whether they want to "install" or add an icon to their homescreen to install your "app" / web app / site. It can be designed in such a fashion that it is indistinguishable from a native app of a certain type that has rather narrow requirements.
If you have philosophical objections over H.264 because of patents etc., then this won't help.

If you have the HTML player enabled, and if your GPU supports hardware H.264 decoding (most do these days), this plugin may help:

https://github.com/erkserkserks/h264ify

Otherwise Youtube might send VP8, which your CPU has to decode.
To me, it's almost the same (but not quite exactly) as someone posting code on stack overflow, and developers using and relying on that code for their job.

The idea of what part of information is owned and what is shared is a concept that fascinates and bewilders me consistently. Art has all these emotional attachments to it, this personal affect, and not many stop to think that for some people, code - even mathematics, is exactly the same.

Why is there a difference between someone who posts a solution on the internet, versus someone who teaches a course and publishes a book, versus someone who traces a drawing using a projector for art? Public and cultural education, myth, and superstition, mostly. But in quantity and quality - these determine the success or failure of any venture business; even the start of a lifelong friendship.

How do people come to the thoughts they conclude with? How do people get ideas? I guarantee you, if you lock yourself up in a little room and wall yourself off from society, you will either arrive at some derivative of absolute truth or you will go insane, possibly both.

If I post this comment, and then other people have ideas that are profitable as a result of my comment, does it matter how similar their idea to my comment appears? Do I own those ideas that result from my comment? I would say no, because that's absurd, but yet, we live in a world that has opinions that cover the entire spectrum of this dialogue, and then some.
The $6.5B Plan to Turn the Mayo Clinic into a Destination Medical Center
I was working for an early-stage startup during the summer of 2013 as the front-end developer. While I was there, we fired our iOS guy, our backend guy switched to iOS and the company now needed someone with full-stack experience to cover the gap, so I got the axe at the end of my contract.

Personally, I was lucky: it took me a total of 4 days to find another job. I didn't have to retool myself because I had kept up on the latest trends within the scope of my skills, and the job market was heavily in my favor at the time.

While I didn't have to learn new skills, I did learn that external factors beyond my control can affect my continued employment. It has made me more mindful of my surroundings and observant of the business direction.
From watching the video, the theory says that your mind is restricting blood flow to other parts of your body to deal with stress, for instance. Just the fact that people learn this is usually enough for them to stop their minds from doing this.

Sounds a little hard to believe. We need a few hundred people on HN to try it to get some anecdotal evidence.
Thank you! This will require some study.
Start Learning with the Summer of Data Science
You are right.
I was consuming large amounts of caffeine. Usually 4 to 5 espressos per day, 0.5L of filter coffee, plus large amounts of beer on Friday and Saturday nights.
At that time, I was in a gym, 3 to 4 times per week. I was told, by the doctor, that it would help me to clear my mind from work.
Regarding medication, I was consuming some vitamins.
I'm typing on a TECK right now, and I've been doing so for over a year. I still hate it.

I use the Workman layout, and I like the layout... BUT THE CHATTER!!!

At first I had to get used to the layout, then supposedly wait for the keys to "break in", then clean the switches.

It's not so bad... just annoying enough to barely not buy another keyboard. It was only last week that I ordered http://atreus.technomancy.us

If that one has chatter too, I don't know what I'll do. Go back to rubber dome maybe. Despite all the bad things people say about them, my old kb never missed a single press.
Kubuntu and Ubuntu at odds over leadership
We looked at doing things like logging git commit frequency to try and provide realistic estimates to users of their time that they could then confirm or alter. Realistically, with the diversity of talent we have here (both technical and non-technical) and the time it would take to do well, it didn't really seem too practical.

It would be awesome if WakaTime and others provided some way of interfacing with an API, so that individuals could track time in a way that made sense for them while reporting in a relatively consistent standard to a central system used for accounting and billing.
So why do we all set the nominal bar at 40h for a 5 day week, why not 32h and 4 days or some other mix?