skysight-inc/HackerNews huggingface dataset:
Yes, I agree with you that not everybody may be able to have some best selling ideas.

What I meant to have something to pursue is not necessarily some successful technical or business solutions, it could be any hobby or interesting things.

If it were me and I didn't have a great idea, that's fine. Since I have energy and capability to work out things, I can invest my energy into something or some idea other people have. Actually it's lower risk but may have some return in the future.

I really encourage people to participate in any sort of interesting projects available on HN, including mine.
> a large time commitment

No. Solving the first 12 PE problems should not take a competent programmer more than 30 minutes.
There is another well-known game/tool that has had this effect for decennia: LEGO
Good thought but the numbers they're playing with and hence pressure/expectations are much higher.

$5.1m invested dollars in from big VCs already
http://www.crunchbase.com/company/famo-us

VCs were betting on the longshot that famo.us delivers and actually works as a layer/graphics engine for non-native apps (a $100m+ play for sure). We all saw those bets and the founder certainty as a guarantee this technology would actually live up to the hype where I think we should look at this one more like the VCs did. A 1 in 20 shot and changes everything if it happens vs. expecting it to happen and factoring it in our plans.

Hate to say all this because I'm building a browser limit pushing project myself that could have used famo.us...
I'm not sure I'd describe Bedrock Linux quite like that.

Rather, the idea is that you can install packages from just about any other distribution, including things which are typically seen as mutually exclusive. The majority of the system can be comprised of packages from something known to be stable like Debian or CentOS, while still having easy access to things like packages from Arch (including Arch's AUR), retain extremely good library compatibility with popular Ubuntu for precompiled non-distro-provided things like proprietary software, and still get to leverage the flexibility tools like Gentoo's portage provides.

So, yes, you could use binary packages unless you need to build from source - Bedrock Linux can fit that design if you want it to work that way. That's a perfectly fine way to use it. But I would frame that as one of a number of ways to go about things, as the system is quite flexible.
I believe the main reason for the failure of the Weimar Republic was that most people actually didn't want a democracy. Right-leaning people saw it as a decadent and weak form of government and wanted the monarchy back, and left-leaning ones were split between a dozen different brands of communism or anarchism.

And of course it didn't help that previous military leaders had been worthless cowards who continued a losing war to a point where they could not longer sue for peace, then leave it to the newly formed democratic government to accept the onerous conditions imposed by the opponents and end up getting blamed for something they had neither caused not any choice in.
I watched a lot of their videos, and until now they were pretty honest. This video is trying to be astonishing by explaining high level math to regular people without clarifying that holds true under different circumstances. That will make people confused over what the sum really is and feels deceptive, since they don't explain that if you are not in a special field of math/physics, the sum is divergent(inf).
BarSense - use computer vision to analyze your lifts and improve your technique
2013 Mac Pro-style Hackintosh based on actual trashcan
Seems the MR technology was intended for about 5 minutes of use - a really intense short period where a hand-waving space was faster for a very specialized complex set of gestures than a generic keyboard or mouse. Not sure I can think of a faster way to juggle a set of videos looking for incriminating information, given that it must be completed within minutes - and no more than those minutes. Yes, muscle fatigue would set in fast & hard after a few minutes, but by that point the work would be moot anyway.
Public speaking is tough
TL;DR Straw men and fuzzy math.

Lots of absurd assumptions in here. Many of them were acknowledged, but the author seems to think that this `millions of lines of spaghetti code` with `little use of existing libraries` will be rewritten as millions of lines of spaghetti code with little use of existing libraries. The rewrite should decrease the workload to a fraction of what the author used for his fuzzy math.
The UVA Online Judge [1] is one of the largest and oldest programming competition sites on the web. They have a huge library with problems in pretty much any CS area. However it can be a little overwhelming at first, so is better to use UHunt [2], which categorizes problems according to difficulty and area, such as Data Structures, Computational Geometry, String Manipulation, etc.

[1] http://uva.onlinejudge.org/index.php
[2] http://uhunt.felix-halim.net/id/339
I am reminded of a chart of sorts that described "what the software engineer forgot" when describing how long a task would take.

"Oh that's 5 minutes." You forgot logging in, powering on the computer, searching for the particular lines of code, a quick test that the fix didn't break anything, and then [if applicable] shunting over to version control.
Right. Keyword here being 'salary'. Most business owners pay themselves only enough of a reasonable salary to keep from getting audited and compensate themselves through other, technically non-salary, means, for tax purposes.
Much of what he desires out of his ideal programming environment sounds eerily like CL or SmallTalk (though possibly closer to CL).

The textual representation of CL code IS the AST. You can change it to be whatever you want. You can programmatically manipulate the code objects represented by that tree using the same forms and idioms you use on plain old data. There's very little magic that happens "under the hood."

I can't even imagine how awesome the CL ecosystem could be with someone like Paul on its side. sigh

I've been putting in some time to learn Scala but he elucidates much of what bugs me about the language in this talk. I'm hoping to see a, "Good Parts" book but I'm not sure if that's a good sign.
How to win at email
CSS also has serious issues with its design (not just syntax) - it's a pretty awful markup language, because it was created apparently without reference to hundreds of years of graphic design and text layout and missed out some essential typographic and design concepts.

To pick a few examples, until recently you couldn't have grids, multiple columns of text (still pretty broken), embedded fonts, and the box model is unnecessarily complex, which led to loads of bugs in the browsers. That's easy to say in retrospect of course, and lots of the problems are now being fixed or worked around, but it's a pretty gnarly language, and many criticisms of it are not based only on ignorance but on substantial flaws in the original design. CSS is awful to work with, and is only slowly getting better.
> Why not just let them focus on the engineering?

This is why I sincerely believe secretaries are important. Managers... do the managing. Secretaries... take care of the administrative. Life is so much better when this stuff "just works".
You can write a million lines of code that do arbitrarily little, particularly if you're following poor development practices. I've seen a million-line codebase that could have been replaced with 10k lines of python. Depending on what functionality they actually need and how much they need the developers, Acme could well be making the right decision.
As someone who's done a huge amount of front-end development, I disagree completely, at least when we're talking about graphic design (as opposed to interface design, and even then it depends).

The job of a good designer is to come up with a "look" for a page that feels a certain way, that communicates certain ideas, with careful consideration of clarity and emphasis. Their skillset is emotion and communication. Knowing the technology beneath it helps them exactly zero in this, except in just a few instances of knowing what is and is not technically possible in the browser.

In fact, I have found it more difficult to work with designers who have learned some HTML/CSS, because it's a case of 'a little knowledge is a dangerous thing' -- writing HTML/CSS for a blog is a totally different thing from creating a clean, extensible front-end architecture for a large site, and you're constantly having to explain to them that, yes, you can do that on your blog, but it's not that simple to implement on our site, because this component is used in multiple ways in different places, and no you may NOT edit our source code directly, because changing the <h1> on that page will change it on the whole site, which is not what you're intending. Or it breaks the object-oriented CSS model we're using.

The only thing I ask from designers who provide PSD files, is that they remember to draw hover states as well, and explicitly indicate what happens to text that will inevitably outgrow the area they've given it -- should there be ellipses, should it expand downwards, should there be a character limit, or what. And to stick around afterwards so I can ask them about if inconsistencies in their design, like close-but-not-exact font sizes or spacings, are actually intended. Really, that's about it.

And the analogy of a designer who uses Photoshop but doesn't know HTML/CSS is like a photographer who doesn't use a camera is just plain silly. Photoshop is their "camera". The end result is just pixels in a browser anyways, it's not like they're giving us webpages on oil canvases. And guess what -- print designers don't know how to run printing-press machinery either. Because Photoshop/Illustrator/etc. are their "cameras" as well.
Exactly this. If you are a PM at a Valley outfit & can't code right now, your team simply pretends to respect you, while going off & doing its own thing. Its just one of those empirical things. Doesn't matter if you "used to code" once upon a time. Things are moving at a breakneck pace & if you don't keep up, you are really going to get left behind.
I will also say that if you are a PM at a non-Valley outfit like a bank or one of those outsourcing firms, the exact opposite holds true. You should probably not code & spend all of your time managing. IBs especially frown at MDs & VPs taking on hands-on roles instead of managing & filling out gantt charts. My Manager at Goldman used to write compilers using javacc to automate risk algebras - he regularly got the stink eye. He used to tell me "they just want me to run the spreadsheets" :)
I've been a f.lux fanatic for a long time. Recently, though, I've been getting headaches that seem to be relieved by turning it off. I think it has something to do with getting a variety of color input rather than mostly red or mostly blue, but an expert I am not.
Wait, the technology landscape solely comprises out of a bunch of successful internet companies?
Airware (S13) Demos Its Drone Platform By Protecting Rhinos From Poachers
someone comes in and does it 10x better

That was the rule of thumb I heard quoted in Business Studies, too. I think the key point was that a customer base tends to have a lot of inertia. To overcome that, you need at least one element of your competing offer to be dramatically better, and for quantifiable things like a price, an order of magnitude is significant enough to achieve that (and by implication a factor of only say 2x or 3x wouldn't necessarily be enough to dislodge an established brand).

Clearly there's a lot more to market dynamics than that in practice. On the one hand, we have supermarkets competing over prices for commodity household products by the penny/cent. On the other hand, at least here in the UK, we have industries like mobile phones, personal banking and household utilities that are all notorious for having poor customer service yet also all have surprisingly low numbers of customers switching brand.

I'm not sure where on that scale a typical consumer Internet service would fall, but in all cases it seems highly unlikely that a service with an inherent element of lock-in (even if you can move your data, it's going to take time and effort to do it) has anything to fear from an occasional screw-up that affects a few customers. It's obviously undesirable, and hopefully none of us thinks it's OK to dismiss anything that damages any paying customer out of hand, but it's not some sort of doomsday scenario that is going to bring down a whole company overnight.
I agree with everything you're stating here, I just wish it was that easy in practice.

Some of the problems with deliverables is managing client expectations, they expect or have gotten used to seeing output of a PSD that counts as 'what their site will look like'. The creation of a PSD as a deliverable for the 'final design' is boilerplate for every agency I've ever worked with.

Responsive design has finally started nailing the coffin though; it becomes too cumbersome for designers to create renderings of different viewports, let alone understand the intricacies of how media queries work or how assets are delivered to different devices.

There has been a lot of creative thinking about deliverables (Style Tiles, Atomic Design) which is helping us get over the hump.

I would hazard a guess that most of the sites in the SMB space are either WordPress templates or custom designs that were then handed off to a service or an outside developer to make into functional websites. Sometimes, the developer doesn't get to see anything until the client has signed off on the design. I see this happening with large companies which do multiple millions of dollars a year in agency work.
Have you completed the Ruby/PHP/Python track on codecademy?

You say that you are beginner, which is fine, but you should at least have done 1 of those 3 courses already.

Also, what is your email? You can use boun.cr to not expose your real email address out here.
Knowing When to Flip.
The Story of the Ping program
Startup Team Building Party
What I wish would happen is that organizational forces were focused on breaking up ISP monopolies over the pipes. Essentially, building a firewall between infrastructure and content. It would create a market...remember that thing we think controls America's destiny...that would lead to faster bandwidth and also ISPs that offer free, open, and protected services.
The Minority Report interface was based on actual working prototypes at the MIT Media Lab. After the production of the film, the original researchers (and advisors for the film) launched a startup (Oblong) to develop a product (g-speak), which is about as clumsy as Siri.
Discovery unveils Curiosity.com to inspire everyday learning
Ok, that's fair.

If I am going to give myself wriggle room, its that the vast majority of problems I have seen in poor software management have not come from a ex-Developer who has lost touch with the codebase, but from the other issues you / OP make - delegation, focus on team growth, structure and process improvement etc.

If someone is self-diagnosing and saying "aha the reason this is all falling apart is because I am not coding more" its unlikely to be the correct answer.
RVM 2.0 fundraiser has just 12 hours remaining to hit stretch goals
My hazy recollection was that at some point people doing flat, non-interactive design called themselves "print designers" or some variant. E.g., magazine designers, book designers. I'm wondering when they dropped the medium-specific notion of design. Are you saying that goes back before the 1950s?
with tools like edge reflow, the human part of PSD to html is going to be dead. HTML/CSS/JS will become the assembly of the web that no one is directly programming with. Designers will keep working on psd and use edge-like tools to export html/js files, and coders will be using clojurescript/fay/coffeescript etc.
"X is dead" is dead. Just because you don't use X doesn't mean others don't use it.

A very large number of people who do web design for a living are much better at making their visions a reality using PhotoShop than HTML/CSS.
"...make design iterations much faster..." as if!

Say you want to swap over the search box with the account functions (sign in, cart, etc.) in a header on an ecommerce site. Chances are that you need only change a couple of lines of css to effect this layout change. Minutes later you can then run through the customer journey with the client and get a few people to test it. You learn quickly if this is better for usability and if it does not work you simply roll back the css to what you had before.

Compare with the PSD approach. You can spend a minor age fiddling with the umpteen layers, then you can hide/show layer groups for the homepage/category page/product page/basket page/checkout and so on, saving out some flat jpg thing along the way. Then present it to the client and ask them to imagine if it is better. If they go ahead then you hand it over to some developer that will then have to make what was signed off pixel perfect.

However, along the way you discover that the account functions are in a dynamic list, e.g. the basket shows how many items are in it, as does the wishlist, and, on some pages, e.g. checkout, there may not be all the links shown. So it changes around. Consequently the area/box that has been designed fills up or gets empty, impacting the design in ways not understood doing it with Photoshop mockups.

Note this is a simple example with no fancy responsiveness involved, just plain regular desktop view.

Put simply, Photoshop is a useless tool for any meaningful design. It results in very poor workflow. All clients have already had websites, they all know that PSD mockups don't look like that once they are implemented, and, if they do, there is a whole lot of stuff that is not accounted for. It is much better to be honest with a client and involve them in an iterative design process.
Security and NaN tagging
I used to, but now I prefer http://www.insilmaril.de/vym/; both have acceptable export to org-mode.
Mads Torgersen on the Future of C# (6.0)
Currency Abundance and the Tip of the Iceberg.
Npmjs seems to be down half of the time
The real problem is with the app stores. They are terribly organized for discovery of any apps, the iTunes store specifically. How are you supposed to find new apps if they're not in the "top XX" portal?

1: If search is how you access the huge variety of apps, why is the search bar hidden all the way in the top corner? When you open the app store on an iPad, you have a beautiful, but ultimately very limited view of apps.

There really needs to be, and I believe there is room in the market for, a service that helps discover new and upcoming apps. Both Apple and Google do a poor job helping users find apps they might like.

2: "Genius" is useless if you have to find apps you like first. It may help provide limited exposure to apps similar to ones you've tried, but it provides poor results if you don't know what you want in the first place.

3: Each of the categories provides only the "top XX" or "newest XX" apps. This incentivizes a cutthroat market and disincentives large investment into apps. Sure, there is a ton of VC money to chase many different app ideas, but ultimately, successful apps will need to make a return on investment. Both Apple and Google do no favors to developers by fueling the "turnover" game. You get one shot on the "new releases" board, then you're on your own for marketing outside of the app stores. In the long term, this will decrease the quality of apps on both platforms. Amazon has a shot at getting it right, and I believe this strategy may favor them in the long-term.

If you really want to win, find a way to improve discovery or "browsing" of apps. The market will follow the incentives to their logical ends, and right now, both of the big players are missing the opportunity to incentivize discovery of quality.

Nick

P.S. I don't know the solution to these problems either, but look for yourself and tell me they don't exist.
Cool. I like all tech stuff related to working out. Tracking apps, logging apps etc. has been a great motivation for me.

It was unclear for me how the tracking is done. My first thought was that I had to mount the phone to my arm or the bar. After following the link to the play store, I see that it tracks with the camera.

Watching yourself lift from the side is great, even if not using this app. I recommend having someone film you or put your phone on something. Personally I have discovered that I didn't end with the bar straight up when doing bench, and that I should go deeper on squats.

Edit: Clicking the "coming soon on app store" displays a form flickering and then "[object Object]". Fx 26.0
Is that documentation sufficient for a full-featured open-source driver on par with their proprietary ones?

I ask so because, for the past decade or so, I've been using Intel CPUs and GPUs exclusively for their excellent Linux support. If AMD can provide the same or better level of support, I'd consider switching.
Am I the only one thinking that the results are pretty bad (yeah I know, one week only). But, what I understand: no user engagement, bad questions, not enough answers.

Nice idea, but what this metrics says to me is: time to pivot.
> AMD now needs either a Google or Microsoft to commit to optimizing their operating system for HSA to seal the deal, as it will make software that much easier to write.”

I'd say this is perfect for Android, especially since it deals with 3 architectures at once: ARM, x86, MIPS (which will probably see a small resurgence once Imagination releases its own MIPS cores and on a competitive manufacturing process), and AMD is already creating a native API for JVM, so it's probably not hard to do it for Dalvik, too. It would be nice to see support for it within a year. Maybe it would convince Nvidia to support it, too, with their unified-memory Maxwell-based chip next year, instead of trying to do their own thing.
Even if the integrated GPU is the limiting factor, it still saves you CPU cycles to spend on other things, and has the additional bonus of simply being compatible with code that you would run on discrete GPU's. T'would be awful if games built with Mantle just couldn't run on APUs.
DRM destroys the possibility that the contract of copyright can be upheld.

The contract is that we, the people, give - through our respective states - content producers a limited monopoly on reproduction [and modification, etc.] of artistic works in exchange for them being release in to the public domain at the end of that limited term.

With DRM a content producer (or at least the rights holder) destroys the ability of the work to pass in to the public domain [effectively].

In other words applying DRM breaks the contract. This means that we, the people, should be under no obligation to provide the state enforcement to their monopolistic rights gained via that contract.

There are ways the contract could be maintained under DRM [deposit an unblemished copy that can be released to all copy holders on expiry of the term] but I've never seen anything to suggest rights holders are acting to avoid breaching the central contract.

This is pertinent because it's not just linux that will be cut out of being able to present this data [DRM protected works] but also the OS of those in the future who're supposed to get access to copyright works which are currently being locked for good by DRM techniques.
Snowden only needs a German passport.
Five strategies to monetize your mobile app.