skysight-inc/HackerNews huggingface dataset:
When I was in college, like many struggling students, I didn't have much money, my means of transportation was a 3 speed Stermy-Archer 3 speed bike that had the best security system ever, I never locked it. It had something wrong with the 3 speed and if you stood up on the pedals it would slip and the rider would end up with their taint on the center bar, ouch. It was fine if you were not in a hurry and took your time. There were a number of times when I came out of class and would find it laying on the ground about 30 feet from where I had parked it.
I can't say I'm surprised. They hired a lot of people for a niche product that isn't a huge seller. Sure it sells pretty well for what it is but, at least from the outside, it never looked like it could support the huge influx of people that they hired.

Also the number one complaint about the Pebble that constantly comes up with every single release is the huge bezel and then their latest watch, the round, almost appears as if it has more bezel. Sorry but I just don't think it looks attractive that way and I honestly really want one.
I've been in the same situation as OP many times (although in most cases I've been brought in fix someone else's code).

In the Ruby ecosystem, library authors didn't really start caring about semantic versioning and backwards compatability until a few years ago. Even finding a changelog circa 2011 was a godsend.

I think this was mainly caused by the language itself not caring about those either. 10 years ago upgrading between patch releases of Ruby (MRI) was likely to break something.

At least this is one thing JavaScript seems to do better.
I actually like this because it's probably challenging and ammo at review/promotion time. If it isn't appreciated monetarily then it will just be used as interview content for my next job.
I want to use cloud speech api for various reasons
If you are looking to establish your brand as relevant, it's a poor choice. It's hard to take Medium seriously as long as they are designed to troll for (and track) reposts by adding fake fragment identifiers to all of their URLs (which they also use to defeat dupe detection). Legitimate venues don't need that kind of evasion.
Not sure why it is "scary", any more than it would be scary being an anchovy in a school of anchovies. I think it would be interesting if they added in pedestrians who had to be avoided.
FYI, you can reply to my comments if you click on their timestamp, in case the reply box isn't showing up

> So if you're going to troll a solid argument by nitpicking, do it properly and get the details right.

First of all, I don't appreciate you calling me a troll. Someone who mentions "5kb functions" clearly has no idea of what 5kb represents, period.

And second, this is not a solid argument at all. There is logic behind it, which is why we usually have high quality stdlibs in popular languages. Javascript lacks that. So instead, javascript gets this absolute mess of an ecosystem, where things like this can happen.

Several people have brought up various issues with the way it's done now. Dependency hell, for one. Lack of discoverability, which in turn leads to duplicate libraries, which in turn leads to a system where you have 1000 dependencies, but despite your "modular" idealism you still have hundreds of duplicate dependencies. Not to mention all the duplicates of different versions of the same dependency.

This "saving lines of code" math is completely broken exactly because this stuff is not in the stdlib. The various issues with the JS ecosystem mean that the actual results are nowhere close to ideal, and have a net negative impact.

I also love when people mention how much "one time cost" is saved and back it up with similar math, completely forgetting the amount of continuous time wasted downloading and installing these dependencies every time.
What tends to happen is an executive makes an offhand remark in a meeting about a technology and five mid-level people pick up on it. They each tell 2-3 low level managers to work on it. By the time the project gets to individual contributors it has been distorted and several other groups are trying to deliver a similar project. Individuals just think, "why are we doing this?" because each level hides their intent to impress their boss's boss.
tinfoil pocket liner
five.js was missing something. I fixed it. https://github.com/jackdcrawford/five/pull/234
Here's Why Online Classifieds Are Fascinating
I live in Fiji.

We stopped this last year. Non-citizens can't buy residential properties within town boundaries. Outside of town boundaries, they can buy residential property but must build a home within two years... and there's a minimum $ amount they have to spend building the home.

The law was enacted because locals just couldn't compete with the Chinese.
There's a lot that those 5 year old PCs can do that those shiny new iPads can't. In most other cases, they get the job done anyway.
>Smartwatch pioneer Pebble is laying off 25 percent of its staff amid increased financial concerns.

>letting 40 of Pebble’s 120 employees go.

What the math?
Robotic Chef
White racists accept to mingle with non-white despite their beliefs, surely non-white can return the same curtesy?
Satyajit Das: Innovative destruction, not disruption
The difference is game developers generally don't care about the small Mac market and have no problem leaving it behind, that's not true for web where ios makes up a decent chunk of traffic.
You must have had a nice grin seeing that. I also read reverse psychology tricks on biking boards such as not locking the bike, which convey a sense that the owner is not far / in sight and scare most robbers. Requires balls.
I make $250k/yr but still can't afford that
I would have bet on "yes" until a day ago.
SoundHound released Houndify[1], their voice API last year which goes deeper than just speech recognition to include Speech-to-Meaning, Context and Follow-up, and Complex and Compound Queries. It will be cool to see what people will do with speech interfaces in the near future.

[1] https://www.houndify.com/
It must be one of: Elm, Purescript, GHSJS, Faye or Haste
Yes you should!
Not even prodigies know they are one.
Taking your first steps in anything arise a ton of questions and you may miss being an amazing grogrammer just because you dont understand interfaces.
Go learn the basics from someone who theoretically knows how to code!
Well he is got balls. You were supposed to be on the side of the developer
Wasn't the Vancouver property also fueled by some kind of citizenship granting process from purchasing property in excess of some price?
Meaning that they can then use the money they're making launching satellites and restocking the ISS to pay for the development of passenger rockets.

Boom can't do this. Unlike SpaceX, they need enough investment money to take them all the way to passenger-safe.

Also passenger safe for a few highly trained and risk aware astronauts is a lower bar than passenger safe for the general public.
Incidentally, behavioral questions are common in nontechnical interviews, since the entire interview is spent analyzing a candidate's skills in the abstract.

How will I know if this person is good at, say, sales or biz dev in a vertical with long lead times? I can't vet that skill set directly; I can only ask the candidate about it. Behavioral questions give me something to cross-reference in the absence of on-the-spot performance data. So do case questions, which (at least ostensibly) tell me how a candidate thinks, and how she organizes her thoughts. (And of course, domain-knowledge questions help me assess the depth and quality of a candidate's experience in the field.)

Behaviorals aren't perfect, though. They can be gamed. It's not too much of a stretch for a candidate to memorize a half-dozen anecdotes to trot out in response to any question that begins with "Tell me about a time when..." (Nevertheless, you'd be surprised by how few people do that sort of prep work.) Canned responses are especially common with candidates straight out of school or grad school, where they are often trained in how to answer behavioral and case questions.
Correct me if I'm wrong but this just seems like the next wave of gentrification. If you make a place nice and safe, people with the most disposable income buy it all up.

Everybody feels this way about the next wave. I'm not unsympathetic and am similarly unable (and/or unwilling) to buy a house in this overheated bay area market.

Reminds me of an article I recently read:
http://www.atlantamagazine.com/homeandgarden/the-gentrifier/
There's nuance to the discussion that both sides are missing. People argue forcefully whether these small modules are good or bad, but I'm not seeing much evidence that they understand the other side.

First: why small modules are bad. Lots of dependencies complicate your build, and you end up with the dreaded diamond dependency issue. Failures in a dependency become more likely to affect you. It gets you in the habit of using prebuilt modules even if maybe it's not quite what you need and it would have been better to write yourself. With `npm` specifically, we've seen how its mutability can break the build, though that's about `npm` and not the idea necessarily.

I think most software developers' gut responses are that something is wrong and crazy in the npm ecosystem.

That said, there are benefits that this blog post and others aren't mentioning, related to the javascript situation specifically.

The first one is that javascript is a surprisingly difficult language to get right. Sure, the final solution is only a few lines, but which lines are hard. You have to navigate the mindfield that are is V8 in nodejs, v8 in chrome, spidermonkey, chakra, etc. I've had code work in Chrome before but blow up in IE, and it's really hard to track down and test.

The comments in the blog post are illustrative:

One line of code package:

return toString.call(arr) == '[object Array]';

Crazy right? And my first stab probably wouldn't have been to implement it that way. Why not:

(testvar.constructor === Array)

that a commenter suggested, which should be faster? Well another commenter said:

The constructor comparison will fail if the array comes from a different context (window).

I've run into issues before with cross-browser compatibility stuff, and it's frustrating and hard to test. If there's some de facto standard package that implements it for you, hopefully the community can iron out edge cases.

The other thing that people don't bring up, is that there's not much JS standard library, and in the browser context you have to send all your code to the front end.

So maybe you write these 11 lines yourself, and then another package writes these 11 lines, and another... it adds up. But if everyone uses the same package, the code only gets sent once and they all share it.

Lastly, people talk about how `sin` should be a part of a "trigonometry" package and not by itself. Well, again you're faced with sending a bunch of unnecessary code to the frontend. With webpack2 and tree shaking, or e.g. Google's Closure compiler, it can strip out dead code and so this issue will go away in the future, but we're not quite there yet. So package authors still bundle all these things separately.

So pros and cons.
It's not about programming, it's about fast progression.
Some interesting things to note:

NPM claims intellectual property issues had nothing to do with their dispute resolution.

NPM disregarded Azer's unpublish request by restoring `left-pad@0.0.3` from a backup of Azer's original publishing, not by repackaging the liberally licensed source.

NPM claims the full dispute resolution policy is still in place, yet many of the packages that have been taken over currently have no usable code and/or are being 'squatted' in direct contradiction of that policy.
npm over twitter? A site populated by trolls and spammers. What could possibly go wrong?
Small modules are easy to reason about

They really aren't, when I'm reading is-positive-integer(x) and wonder if 0 is positive I need to hunt down the definition of positive through two packages and as many files. And it gets wrose if both your code and one of your dependencies required 'is-positive-integer' and I have to also figure out which version each part of the code base is using.

If you had written (x > 0) I would have known immediately, it also wouldn't be doing the same thing as is-positive-integer(x) but how many calls to is-positive-integer are actually correct in all the corner cases that is-positive-integer covers?

And then there's the other problem with dependencies: you are trusting some unknown internet person to not push a minor version that breaks your build because you and Dr. is-positive-integer had different definitions of 'backwards compatibility'.
It sounds like they've made some truly incredible progress and I can see demand. But how are they going to get to a fully developed and built aircraft for a fraction of that cost?
Aide: Nixon's war on drugs targeted blacks, hippies
This is cute as a proof of concept, but it needs severe performance improvements if it's intended to replace Launchy.

Launchy sits there with 30mb ram used and no cpu used when not in use.

This launcher sits there with 170mb ram used, and 1% of a core in constant use.
I agree with you, but they weren't saying that JS is unique for having dead-code elimination, but rather for having to be served over a network connection nearly every time it's needed (not accounting for caching and offline apps, etc), which presents an entirely new set of problems that webpack and others attempt to solve.
3 reasons that, in early stages, startups have customer service at their HQs (IMO), and why it makes (financial) sense to move them to lower cost areas when a startup reaches a certain size:

(1) at the early stage basically everyone is part of customer support in that they are addressing/solving a slew of new/unanticipated problems together in real time and therefore its beneficial/valuable to have everyone in the same place. they also (usually) don't know how to run a customer service organization and are learning how it goes on the fly, esp. for the new product.

Later, the product matures and the majority of customer issues and their solutions are known and the process for addressing them can be (mostly) crystallized into a pre-determined set of responses, meaning that the customer service team can be separated from the rest of the organization. This is usually identified (or forced) by a more experienced customer service manager trained at a larger organization.

(2) at an early stage, costs associated with customer service are still relatively low vs. other investments (ie. product development, customer acquisition, technical hiring) so it seems relatively cheap to grow (you can hire 3-4 CS people for the price of one eng. in SF)

Later, as the organization grows, customer service can quickly balloon into a massive, expensive organization that grows in a more linear relationship with business/customer growth vs. product or dev teams, which (ideally) can be more leveraged.

(3) at the early stage, they are focused more on growth than profitability, so they aren't looking to optimize for lowering customer support costs and are more focused on the speed at which they are solving customer problems, aka. resolving impediments to growth.

Later, when it comes time to pay the piper (which is what appears to be happening with many, many on-demand startups..), customer service is a very easy place to try and cut costs, esp. when up until this point they had been run very inefficiently.

conclusion:

Once a company realizes that their support teams don't need to be at the HQ anymore, that the teams are inefficient and (oh shit!) they want to (try and) be profitable, it makes a lot of sense to move the customer service team to a lower cost location, or outsource it entirely. there's a reason most large, mature corporations do it.
All (most?) bombers are subsonic too.

To answer that

https://en.wikipedia.org/wiki/Tupolev_Tu-160

and

https://en.wikipedia.org/wiki/Rockwell_B-1_Lancer

The only long range strategic bomber developed after the 50s that wasn't supersonic was the B-2 stealth bomber (not that there have been very many strategic bombers developed after the 50s).
Would be genuinely interested in methods for making an area appear less safe
You love VR that much :P ?
> Curtis Yarvin is a professed fascist who has written about his belief that some races are more suited to slavery than others.

Having read a good deal of his unqualified reservations, I wonder if you can source this quote for me please?
The fact that lead positions in a software company are being filled by salespeople and PowerPoint/Excel 'wizards' says a lot about the company, doesn't it? Still remember attending Google's presentation during the 2015 SAP DKOM conference:
"Who would like to see some awesome code of what we've done?" -- blank stares from the audience were the replies ...

/ disclaimer: the opinions expressed in this comment are my personal thoughts on the matter.
The problem is that KIK (the company) has no registered trademark for this use. If they had, they (or you) could point to the specific registration that the `kik` project infringed upon.

Any talk about trademarks is irrelevant (and npm even claims in this article that it had nothing to do with their decision).

Additionally, the `kik` package now has this description:

'This package name is not currently in use, but was formerly occupied by a popular package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we\'ll probably give it to you if you want it.'

So...why did this happen again?
New learning procedure for neural networks
"necessarily to tinker" - i suppose is done by tech guys. Normal people would use it as it is. There are so many low-end to high-end Android mobiles sold in India. Most of them don't tinker at all. As long as it does the basic call/browsing/videos/music its fine.
Works for me... I'm fairly intovert and used this approach in the lead up to my first professional speaking gig last year :)
> The fact that lead positions in a software company are being filled by salespeople and PowerPoint/Excel 'wizards' says a lot about the company, doesn't it?

The lead position in a large company (in any industry) generally requires little in-depth knowledge of the product. The lead positions (CEO, CFO) are there to report to boards, shareholders, and regulators. Sure they might know and be interested in the product, but the CFO of MS and Apple generally isn't going to be a software engineer, just as the CFO of Audi or GM isn't going to be a mechanic.
That just moved things up a bit - they were already winding it down.
Must watch new in-depth tech series called Hello World
Because you can get ideas from other people. Then you can merge your customization with others and have the best of both worlds. I moved my bash customization to a personal oh-my-zsh theme & .zshrc and didn't look back.
Launching really old code written in 2006
We have a project written in 2006 with old tech stack like Struts1. It has lot of frameworks written based on hash maps which can be replaced with good frameworks available. For example they have written workflows frameworks for validating a use case by executing different struts actions.

For some reason management did not gave launch signal at that time in 2006 and project was closed.

Now we are starting that project again and the plan is to use the same code base and migrate to struts 2.3.24.

They have written different modules as separate projects and creating jars and referring them which is good, but they have cyclic dependencies as well, which is my concern.

I have gone through code and the code is not good. Not written properly and lots of performance issues. All UI related written in plain javascript, no jQuery.

The old code does not work and not getting up, because some part of the code is missing. No documentation. No old team member.

Everyone is new. New team is very much frustrated with working on such code and delivery schedule is very tight.

I think even if we migrate and work out that code and get it up and running. The maintenance of that code will be huge task and will be difficult to add new features.

We already had discussion with client And looks like he does not want to use new technologies or re design it.

How should I convince my client to write using new technologies and re architect the solution. We can use some part of code they have written.

How should I come up with new solution which he will like and can at least think about doing a POC to demonstrate.

Please anyone faced with such challenges. How you guys convinced your management or client?
You're mixing up development time & bandwidth used by client browser. I was addressing the latter. Not having to download a 500 kilobyte library in order to use a single function is a big reason why the node.js ecosystem is the way it is today. Yet it is completely unaccounted for in the article. The author did not go into how the Node.js community came about to this practice in the first place, before going on a rant about it. That is what I was criticising. Whether having minimal modules maximises utility in society is completely irrelevant, because I was addressing perspective and etiquette.

You are a troll because talking about the actual number I used and how good a grasp I have in my mind completely misses the point. You're criticising the javascript ecosystem, I get that, but you completely missed the point of my comment. If you're not going to try to understand how Node.js conventions came to be, what it's strengths and weaknesses are, what the trade-offs made were, then it's inappropriate to focus on particular weaknesses of its practices.

It's like going on about how Objective-C development sucks because it's hard to do on Linux. But you're missing the point about what Objective-C's strengths are that attracted Objective-C developers in the first place.

The author should spend some time acclimating to Node.js best practices before writing this article. And you should do the same before you start knocking down straw men to prove how right you are.
Go to a Trump rally and tell this to a "Black Lives Matter" supporter, I dare you.
Oh easy. Go sleep on the sidewalk. The Justins will be beside themselves.
Sigh, smh. The statistical flaws in this "back of the envelope" calculation are something else.

This was a study based on "a Financial Times multiple choice survey of 77 high net worth and affluent mainland Chinese individuals, 'admittedly not a statistically significant sample size,'” According to this survey, 9 individuals out of these 77 Chinese bought property in Vancouver. After some more mathematical shenanigans, this is extrapolated to imply that Chinese mainlanders buy 33% of the Vancouver real estate market. Really?!? And this statistically baseless extrapolation becomes newsworthy?

http://www.vancouversun.com/business/chinese+investors+third...
Every web app I've used has required a painful sign-up process, which is usually where I bail out of the process.

How do you feel about using Facebook or Google accounts to sign into third party apps?
i really love these launcher apps.

this one sort of illustrates the problem with developing windows apps:

- you either learn complicated c++ and windows api and have to write your own rendering framework for custom components

- or use C# and xaml and get terrible performance with systems with no gpu acceleration

- or use VB for terrible performance and CPU usage

- or use javascript and node for huge memory usage and slower rendering than c++ (VB has the same issues)
> without realizing that Tweets can also be deleted.

Yep, just like NPM modules.
Gravy train or mercy dash
PMTUD broken on v6 happened to me too... in 2015.

http://rachelbythebay.com/w/2015/05/15/pmtud/