skysight-inc/HackerNews huggingface dataset:
The ELK stack is great, powerful, relatively easy to use and set up and very configurable. I'd definitely consider it for any dashboard prototyping, given that I've worked places where the 'MVP' dashboard could've been mocked up in days with ELK rather than the months it took otherwise.
Does this necessarily have to be a browser extension or is there any hope of using the video provider APIs to accomplish the same thing?
Jupyter definitely hasn't lost interest - the IPython team is currently spending a lot of time finishing up IPython 3.0 and seeking funding (grants, etc.). IPython 3.0 is due to be released soon now (3.0 beta 1 was tagged a few days ago, and the development is somewhat in a soft freeze in preparation for 3.0). The general plan is to split up the IPython repo and transition to a Jupyter repo after 3.0 is released, and have a relatively quick iteration to 4.0 (mainly consisting of the repo split).
Awesome ! Loaded, closed tab, turned off data, loaded again, still works :) (except that people think I'm crazy waving my phone in the air trying to draw the figure 8)
Haven't tried that...it probably won't work. I live in China so YouTube is kinda inconvenient. I connected via VPN to test on YouTube and it should work on most video clips.
Show HN: Gonads – Golang based front end development tools
Gonads - Frontend development with balls

So far the Node.JS/Ruby based frontend tools I've tried gave me either eye scratches or massive hairloss. All I really needed was a /simple/ way to transpile embedded JSX to react.DOM and compile SCSS stylesheets. Since none of the tools I tried made me enjoy frontend work any more than I already don't like it, I decided to solve this problem myself.
The result is (going to be) a compilation of tools I enjoy to work with. I have started with writing a SCSS-to-CSS compiler in Golang. So far, I feel like it's been an interesting ride so far, for a first compiler. I welcome any feedback and contribution if this project interests anyone to help out.

The repository includes a lexer, parser and compiler and the compiler test-suit runs against the official SCSS-specs to ensure compatibility.
Clickable: https://github.com/mamaar/gonads
I sometimes wonder whether Americans realise that "retard" is pretty much hate-speech in England.

If you're the kind of person who doesn't say things like "I was Jewed on that deal" you should probably avoid using the word "retard" unless you're talking about watch mechanisms.
Worlds Longest Mirror Carving Artwork
Oh man. CrunchBang is my go-to distro when I need something lightweight that just works out of the box. The default install is a great, well-featured system.
> How is that even possible for a competent/honest machine shop?

Because measuring things is hard.

> As if the shop doesn't inspect its output.

Of course they do. And even then it can still happen that what passes inspection at the shop (especially in early runs) does not pass muster with the recipient.

Which is why you don't want to be moving your equipment around if you can help it. Depending on the precision required it really doesn't take much to go from 'pass' to 'scrap' and it is not rare at all for the incoming inspection to reject parts that were accepted at the production facility. This is logical because there is money on the line.

> Is there some sort of CNC-vending-machine business model that I haven't heard of where clients email their CAD files to the machine and next week a freight truck arrives with the stuff?

You seen to have missed the internet revolution in machining, but yes that's exactly the model these days.

Only I'd replace 'machine' with 'machine shop' or 'production facility'.
so true about the 'MVP' dashboard
Presumably this is your first time managing programmers. Without ill will, you are most likely a very poor manager right now. Management is a separate skill and, like programming, it takes a long time before you're proficient. So, the first step is to acknowledge that, right now, you are a total newb and to tell yourself that a few times every day.

From your description, it sounds like these programmers are not as efficient in their work, or as task/goal-oriented as you'd like them to be, but not that they're completely incapable. Sometimes you will find programmers who can't program; they're hopeless, you have to fire them. But otherwise good programmers can be awful at managing themselves... and you're the manager, after all, so it's your problem to solve. Of course, you don't want to micro-manage them every hour of the day; that's not scalable.

Not every aspect of Extreme Programming is applicable to every situation. But a quick morning standup meeting can be a very effective tool. First, you will find out when people get off track and are having problems. Second, it creates some accountability to advance the ball every day. Third, while you must actively work to have the team cooperate instead of compete, it will naturally create some competitive and evolutionary pressure, where the more focused members of your team provide a good example and, over time, can share some of their secrets. Finally, the standup helps reinforce teamwork. If someone is having a hard time with a task, you can respond and say, "hey, you know, Bob's in a good place with what he's working on, why doesn't he help you out today, see whether a fresh perspective can help?"
They might be bored. They might be in over their heads and see two co-workers knocking stuff out and not want to appear like they don't know what they are doing.

Do you have regular one on ones with them to shoot the breeze about what they're working on? Find out what motivates them. Maybe they don't believe in the work going on and think the lead/manager (aka you) is just giving them busy work. Explain the broader picture of what their contributions mean to the organization. Did they get "passed over" for the role you now have?

If you work in a big company, maybe they have seen where getting work done quickly doesn't get them ahead. Maybe there isn't any room for them to grow. What do they want to be when they grow up?

When assigning work, ask them about their approach to the task. Ask them to ask their coworkers or bounce ideas off them. Maybe they think building VM's will help with testing for future work.

You may not be their HR manager (hire, fire, raises, etc.) but talking with them about non-task related stuff may enlighten you with how to better work together.
This is normal.

I managed to fix this by getting a new job where I didn't have to manage. ;)
Try reading. Maybe you'll understand. Although that seems unlikely.
Internships Abroad: Unpaid, with a $10,000 Price Tag
i once worked with a remote(with a 12+hour time-difference) team and i was the least experienced(both effectively and in the code base) in the team.
It was hard for me to both learn and work in that constraint and both of us found it difficult to continue for a brief period.But then after a while we knew the intersection of my strengths with what the project needed.Until that phase , i would often digress on things , esp Unit-tests .I was often singled out for focus(in those tough times) but these eventually played out as good learning points for me in the long run as i mastered their system that way.The manager understood my strengths early on and today we both are happy we went that path.
It is not a sensible idea.

First of, people will be able to go around your DRM by patching the firmware, or spoofing the data coming from the GPS.

Second, your proposal would require the GPS to be always on. Not every drone needs a GPS, and not every drone needs the battery drain of using a GPS all the time.
I saw MiB, it was a documentary.

do we realistically expect otherwise. Considering the amount of animal and insect life we don't have documented when you start getting down to the scale of bacteria and the like its bound to be uncharted. We spend all this time about finding life on another planet when we haven't found all ours has to offer
Just one of many obvious examples that plenty of tools are available "allowing them the freedom to improve their lot." Nobody is stopping them, nobody is "keeping your users under your thumb". Improve your lot? do it yourself, or pay the engineers accordingly.

Oh, sure, Apple et al can change their minds and charge outrageous fees and demand outrageous licensing terms. Nonetheless, lots of affordable tools are available.

And before you take the opposing view any farther: I come from an era & mindset of building advanced computers from scratch. I reject the argument you offer of "by not giving them the source code you are [oppressing them]", because I'm trained in building computers starting from sand, and writing software starting with toggling in op codes with manual switches. I've written format converters (with no guiding documentation) to overcome the bounds you imply.

If you want someone to put in the effort to create complex software, maybe you should understand that they should be paid for that effort - one price to use it, and a higher price to get the detailed source code. If you're paying the price of a few cups of coffee to use it, heck yeah you're not getting the complete body of work a team spent years creating.
Unless I missed a link to a full shootout of the 4 systems, where are they getting the scores for each system in that comparison graphic in the inset?

I ask because Google clearly beat Siri on the specificity of the 3 answers shown, yet they scored Siri higher. I'd love to see a reasoning behind that.
Is this some kind of joke webpage?
Also you've given some amazing talks in various PyCons!
email addresses aren't public in HN profiles.

*Programming language skills - really language…
Webinar: Everything You Need to Know about Google Tag Manager V2
Laptops, including Macbooks made since 2010 or so have gyroscopes in them. Originally for the purpose of detecting a fall and parking the drive head before impact.
Do you smell?
very sad to see this happen. Hopefully somebody takes over and guides the project from here. They have made a great distro with the openbox wm.
Sad news. CrunchBang was a great little distribution. A couple of rough edges, but it was a refreshing change from Ubuntu or Debian.
Give everyone in the team copies of the book "The Healthy Programmer". Problems focusing could be anything from blood sugar level or thyroid to food allergies.
Everything you need to know about net neutrality now, in plain English
give the weaker developers tasks in smaller chunks.
instead of just a goal, give them each step of the way.
meet with them every day, or even twice a day, to confirm they are on the program and to answer any questions they have.
Before you can solve this issue you need to figure out why they are doing this. Here are three example possibilities:

1. Maybe they are not in the mindset of getting to the goal, but rather they are in the mindset that work is work. Or maybe they are doing it simply because it's a habit or because it's fashionable and they heard some celebrity say you should use a VM. Then explain to them that not all work is equal, and that it's important to do work that moves you in the direction of the goal, rather than busywork that will not pay off such as setting up a VM envirnoment.

2. Maybe they actually think that setting up a VM environment is worth it in the long term. If you don't think that is the case, explain why.

3. Maybe they don't know how to solve the problems that they are tasked to solve, and setting up elaborate dev environments is a way to procrastinate. Then make sure that they have enough guidance so that they know what concrete bit of work they can do right now to make actual progress. Ex: if they don't know how to make progress because they do not understand the database schema, then the next step should be to familiarize themselves with the database schema. You could even task them with writing documentation for the database schema to get this started. Or perhaps they procrastinate because they don't like the work that is assigned to them.

There could be many other reasons, but once you figure out why they are doing this, it's likely that the solution will be relatively obvious. Try to not fall into the trap of micromanaging them. If you don't understand why they are doing this you could simply instruct them not to set up a VM dev environment. That won't solve anything in the long term because they will just find something else. It's much better if they know why they should do or should not do a that, rather than simply following orders. Following orders kills motivation and orders don't generalize to new situations, but the right mindset does.

On the other hand, in some cases the issue isn't that a developer is not doing the right kind of work, but rather that the developer is doing the right kind of work but he is simply not very good at it. This can be improved to some degree with training but you have to make a business trade off here: is this developer making a net positive contribution to the business or not. Keep in mind that a developer does not have to be super productive in order to make a positive contribution. Otherwise it's time to move him to a different role or fire him.
Patching, Emulating, and Debugging a Netgear Embedded Web Server
>But mainly this is done because the equipment is quite complicated

Magic!

>And when the failure of your equipment can cause serious property damage, injury, or death are you going to make it easy for people to modify your product's firmware?

Yes. Everyone has a disclaimer "not to be used on life-support systems, you're responsible when you screw the pooch".

>are you going to make it easy for people to modify your product's firmware?

It's not always about customizing someone's OEM product; sometimes it's about getting two pieces of equipment to work together.

ie: John Deere tractor + implement that John Deere doesn't even make, or customized implement, or even, customized JD tractor for a special purpose.
On ICSE’s “Most Influential Papers”
If the senior devs can help mentor the junior ones then at some point you could have 3 or 4 productive devs instead of just 2. Not saying take away a big part of the day but maybe a 1/2 hour or hour long meeting every morning to get the junior guys on track.

Sometimes people need development to become productive members.
One presumes that the court doesn't deems there's been a serious criminal action here. More the status quo isn't legal. I'd like to know if this means the current actions will stop. When? If the government will fight it. Or legislate around it? There needs to be an official response from someone will real authority. It's been judged as illegal...so what next?
While this may not be the full cause, it's an interesting insight.
> We spend all this time about finding life on another planet when we haven't found all ours has to offer

What? How much time do you think we spend on the former? Why do you think it's too much? And why do you think the two goals are mutually exclusive?
with quotes like "we were able to 'find' silicon valey" and findings like "the best indicators of entrepreneurial quality were characteristics like a company's name", it is surprising that the article does not discuss the role that 'correlation' and similar phenomenon might have played in this study.
I don't like how you reduce a possible difference in efficiency to different "values". Like in all other jobs, some developers are less efficient. The OP asked for advice how to _manage_ them, not how to fire them, so there's no need to defend someone you don't even know. He wants to work with the people he has and the situation he is in, not be told how these guys should not have been hired or that they supposedly have different values.
Show HN: Cloud Testing Platform – Load and Website Speed Testing, API Monitoring
Your definition of "good" and "bad" is probably off tangent. As a manager, you take up a new role of being the "coach". It's your job to help your team play at the best performance they possibly can.

Letting go of someone is the simplest thing anyone can do... but if you look back at your own career, chances are you'll find more than a couple of instances when your peers put up, tolerated, and coached you to where you are today - just don't close the doors you walked through.
Did you not ask if you coudl have the equivelent benefits added to your pension ?
Do you think OSX fits into 'free software philosophy'?
Could it be that our understanding of DNA variations is incomplete?

There was some article a few years back where a virus was observed mutating its RNA in what appeared to be some sort of algorithm, like running a virtual machine on proteins. What if DNA does the same, i.e. being not just data but also an interpreter with some changing memory?
At one point this was my favorite distro and my favorite irc channel to hang out in. It showed me a lot about the possibilities of configuring a minimal system.

Sad to see it go. Thanks for everything.
Ruby DSL Handbook
you can hire a PR firm for anything, a bug, yourself, a dog.. anything.

the main reason people engage PR firms is to strengthen their brand or to attain money/reputation somehow.

which is what Qualys was doing.
Ask HN: How to Transition from Back End to Front End?
I've been doing web development for about 2-3 years now and have been looking to expand my skills. I've mostly worked on the back-end side of things (java, scala, etc..), but have also done quite a bit of front end work. I know quite a bit of JavaScript (although still learning) and have been getting alot of experience with Node.js too.

The problem is that in all my jobs, the teams have basically worked with Jquery (was sort of hacked together spaghetti). I've recently been working a bit with React and Backbone, but feel like I'm just piecing together random tutorials on the internet. I think it's time to take the dive and try to learn how to be a Front End developer on a truly professional level. At this point I feel like just flipping a coin to choose between the crazy amount of frameworks and digging deep into it.

Does anyone have any recommended learning path to transition from the back end to the front end?

Particularly someone who's moderately comfortable with JavaScript, HTML/CSS, etc.. (ie. not completely new, but wants to level up to the professional level)
Keecker: Transform Any Surface into a Screen
Google to Close door on Gtalk from February 16 onwards
Open source movements, particularly in hardware, are difficult. No reason to abandon all hope. Though deciding between doubling down on OSE or launching a new effort is something to come to grips with.
The author was clearly discussing the recent events regarding the drone that went over the White House. For normal buyers of drones, and for drone companies, such "blacklists" make sense because it protects the drone operator. Right now if you fly your drone over the White House, an airport, and so on, you -- the operator -- are taking significant legal risks. DJI and other companies know that their average user doesn't want that, hence the "blacklist". But it (flying in restricted areas) remains against the law, and a serious risk, whether your drone complies with it or not. The author of the piece seemed to talk about that from a "normal device" perspective.

But of course everyone knows that such a list would do nothing against a real criminal who would override such functionality. It isn't really clever for anyone to point that out, and it's reacting in advance to a non-law or regulation, but hysterically responding to a company trying to ensure that their customers don't accidentally get in trouble with the law.
The link seems to be dead for me. What was the reason #! is ending? I really enjoy this distro. Very sad to see it gone.
That kind of dev drives me nuts.
It's going to be a process, but you have to break down the problem, and attack it piece by piece. I can identify a couple issues in your short description:

- Untimely completion of core tasks. There may need to be more frequent check-ins with more granular goals, along with accountability or at least retrospection for missed checkpoints. If a checkpoint is missed, the dev and you have to figure out the why of it and how the process can be improved in the next iteration.

- Lack of resourcefulness/grit. This can be taught. This is where it helps to pair someone with a strong developer or yourself. As a teacher, we modeled the learning process as I-do, we-do, you-do. It may be enlightening for an unproductive dev to see better habits in action. But you can't just show a skill and hope it will be replicated. You have to gradually shift more responsibility to the other party to transfer the knowledge.

- Misspent time. Not every subproject is useful for its own sake. Hold your team members accountable for demonstrating the value of tangential work beforehand, and put your foot down if you're not convinced. Everyone loves a side-project, but it's not a substitute for progress on the core goals.

Most people want to improve, but everyone has some mixture of compentencies where they will naturally self-improve and ones for which they will need mentorship. This isn't the sort of thing where you can make one exasperated speech and see overnight improvement. The goal should be gradual, consistent increases in productivity.

And don't forget, since just became a team lead, you also need guidance and continuous feedback. Be proactive in seeking it. Good luck!
Do you use it? How do you like it? (I visited the archbang.org site. After about 5 minutes of browsing the wiki their server started throwing 500 errors. I assume due to high traffic.)

[edit] It seems to be working again.
Develop a process that adds more openness and accountability. Hold a 15 minute daily standup meeting where each developer shares what they accomplished the previous day and what they plan on accomplish that day. Spend some time creating very distinct tasks for each developer that are 2-4 hours long. Tell the developers which tasks you expect to get completed that day and not to get sidetracked. They are providing the engine power, but you are steering the boat.

Many developers get sidetracked because they are afraid to confront the fact that they don't know how to do something. Make it clear that it's okay not to know something but it's not okay to just avoid a task in front of them. Find roles for them where they can excel. Imagine being a coach of a basketball team. Some players are good shooters while others might be good at defense and rebounding. It's up to you to find these strengths and use them together. A fast developer may get excited about doing new development but hate doing things they consider grudge work. These slower developers might like doing work like testing and documentation (and actually be better at it).
If only it was possible to hook up on single-phase house mains an arc torch-based plasma gasifier to direct those toxic fumes into. I specifically looked for access to three-phase power when choosing a residence because I don't see power consumption requirements for the metal sintering gear coming down anytime soon.
Its not efficiency its a trade off.

If your writing tests, setting up environments, and writing specs, your going to be slower than developers who just codes by the edge of his seat.

If you writing software thats needs to be correct, or maintained for many years, you might value that.

If you writing a quick prototype, you won't.

This is why star performers at one company, turn out to be duds in another and vice versa. Its quite a common thing. Switching companies can be a culture shock.

I like being a contrarian, because I force people outside of their preset view, and to see it from other side.

How many times do i see bosses calling their employees lazy, making then work over time? Yet whens its their kids, or wife having to work over time or being heavily worked, so they never see them, they think differently. A different viewing angle, thats why.
SmartDataCenter and the merits of being opinionated