skysight-inc/HackerNews huggingface dataset:
I've worked for a medical laboratory as a courier for eleven years. I don't think all of these jobs will be completely wiped out, for several reasons hit on by people in this thread.
Many of the things I do on a daily basis can be automated, (I know because I've been able to automate parts of my job), but other parts will prove to be such a high bar, it will be twenty years before they will be cost effective and/or the technology is created. I worry more about low cost, easy to use scanning technologies displacing my job more than I do automated vehicles, at least in the near term.
Retraining those of us who want it really wouldn't be as daunting a task as it sounds. I've been able to listen to thousands of hours of audio while I drive, both audio books and university classes, and I encourage my coworkers to do the same.
Most of us understand that this line of work will be disrupted at some point. Places like Uber will lead the front of the change. Business like where I am at, where I handle hazardous materials, and places like ups, which have unions blocking automation, will take quite a bit longer in switching over to autonomous vehicles.
If google home uses the same tech as google now, I've told my phone to specifically play songs on spotify before as opposed to play music.
This sort of cartelization would most likely be illegal under antitrust laws.
As a network operator, this might be kinda nifty.

I'll never know, though, because I'm not registering / signing up just to see what it looks like (and -- in case you're thinking of somehow monetizing it -- I'd certainly never pay for it).

For a "Show HN", there's really not much to see. I knew as much about it after reading the title as I did after clicking the link. Uh... good luck, I guess.
Those cane fields on the way from Kahului to Kihei, while beautiful, seem like a massive wasted space. I like the idea of a decently-sized solar farm to replace the power plant just above Kihei.
I would call your description a stereotype, excluding the flying car and robot, but I'm sure there are also white, hip hop dudes that fit there as well.
Floridian here! The only lobby more powerful than the utilities is the sugar lobby.
Actually that's untrue. There's very little domestic cane sugar (beet sugar only can be turned into white sugar). Government has been limiting sugar imports with a tariff regime because a single family runs the Dominican refineries and they lobby Congress to keep tariffs up everywhere but there and thus secure a monopoly.

https://en.m.wikipedia.org/wiki/Fanjul_brothers

If you are a small household cook you may not know this but you should buy all of your white sugar in the fall when the Montana beet crop comes in and drops the price (though commodity options trading may have smoothened that out a bit in recent years)
And yet the same people who say that developers are not interchangeable cogs in a larger machine will fight tooth and nail requirements that they attend meetings, interact with business analysts or users, or generally do anything other than programming.
Great post - with a very huge caveat: being out of the office means you miss a lot of nuance that is very, very important.

There is a cultural language, and a lot of facts outside the scope of normal direction.

I've worked remotely often and this has always been a huge issue: requirements can almost never be communicated succinctly, they come in waves and indirections.

So if we can solve that one ... this makes more sense.

As for the 'open office' concept, I can't think of anything more absurd. When I visit my clients I can't get anything done.
yes you should have. less of you in our industry the better.
Snap has acquired an ad tech company called Flite
> only to have the projects scrapped because they weren't what the business needed.

That is most definitely not the programmers fault whatsoever. Scope, feature set, product/market fit, and current status should be reviewed on a weekly basis by a product owner or project manager. If a general contractor builds you the house you demanded 6 months ago but your not happy with it now, who's fault is that?

> remote meetings are simply worse than in-person meetings

You give no explanation as your reasoning for this. Generally speaking, all meetings need to have an organized flow. I work on a team of 15 people where we can easily cover all our checkins remotely in under an hour. One meeting per week.
No, because the profits exceed the cost of liability for commercial software.
I suspect this is one of those cases where it starts out as just a quick fix, and soon turns into a challenge where buying a better feeder feels too much like cheating.
Just wanted to offer a counterpoint to the general negativity in this comment thread: for my small OSS project I've always received respectful comments/issues on github. Some more or less helpful, but I've never felt used or abused.

Not intending to cast doubt on any of the experiences here, just to highlight that there's good experiences to be had too :-). I suspect one difference is that my project is dedicated towards education. As far as I know no-one is relying on it for their income.
Rust is intended for applications where you need speed, concurrency, and safety/correctness. In some senses, "use Rust where you would use C or C++" makes sense, but we're also seeing a lot of usage from programmers who have rejected C or C++ for various reasons.

One angle that we've been focusing a lot on lately is productivity. Think about some feature of Rust that provides safety, like out borrow checker, which ensures that pointers don't do bad things. One way to think about this is safety, but another way is productivity: if your application segfaults, you have to track down what actually caused it, and then what caused the cause: "oh this pointer was null because I did something incorrect in this other part of my code." While having the compiler do these checks can sometimes feel like a productivity _loss_ at the beginning, you do a lot less debugging later, so it's a productivity _gain_ overall. (Or at least, we feel that way.)

Other features of Rust make it feel productive as well: a focus on iterators and composable iterator adapters is often more productive than manual for loops, Cargo and crates.io enable wide-spread code re-use[1], we've been working on good tooling for IDE integration for those that use IDEs, and "zero-cost abstractions" help you have nicer interfaces while not having to pay the cost for them. Like this: https://news.ycombinator.com/item?id=13117608

One interesting area where we've seen lots of production Rust usage is embedding Rust in other languages. Since Rust can expose functions that look like C to the outside world, you could write a Ruby, Python, Javascript, or whatever extension in Rust instead of C. And Rust's safety features are appealing here, since you may not be the kind of person who writes C all the time: that's why you write Ruby/etc in the first place.

Soon, we expect to see more usage of Rust on the server: the "tokio" project is gearing up for an initial release, which provides a foundation for asynchronous IO. Even before tokio is released, people are playing with this: crates.io is Rust on the backend, and "npm recently began replacing C and rewriting performance-critical bottlenecks in our registry service architecture with Rust": https://medium.com/npm-inc/npm-weekly-73-no-love-for-http-ur...

Basically, lots of places. We'll see how things go into the future!

1: Anecdote time: my favorite package is https://crates.io/crates/x86, which provides low-level bindings to various x86 platform details. Writing an operating system? No need to define your own IDT entries, just grab the library and http://gz.github.io/rust-x86/x86/irq/struct.IdtEntry.html has you covered. Re-usable packages in operating systems is super cool. On a higher level, this kind of thing is enabling Firefox to re-use Servo components more easily; Firefox can just pull chunks of servo with (relative) ease.
> Another question is: who will be getting their money?

Everyone. The vast swathes of humanity who use transportation services (deliveries, taxis, etc.) will see the cost of said services decreased.

Fairness is an arbitrary and stupid metric. If we give every American $10 and 5 Americans $1,000 that's obviously "unfair" but also obviously to the benefit of everyone.

> In the long run, shouldn't technological progress benefit us all equally?

No?
> Citing a raspberry GPIO pin to do that shows that guy does not know what he is talking about.

Agreed, but I wouldn't rule out the possibility that a crazy individual with sufficient hardware and software signal processing experience could make it work, where "work" allows for a significant tradeoff or two compared to a modern commercial machine.

DAC is probably the easy part -- use a LFSR and maybe some jellybean filters to get spectral content where you need it. 10MHz is slow enough that you could probably phase it in software if you handwrote everything in bare-metal assembly, paid attention to interrupts and DRAM, etc, etc. At first I thought you'd need a coprocessor (and in that case it might as well be a proper Spartan 6) but perhaps it can be done with a dedicated core. ADC is the probably the harder part. You can't kick the can down the road anymore. Both cost and value are tightly coupled to 2^(bit depth)*(sample rate). If you try to make a shitty ADC out of GPIO pins, you just wind up with a shitty ADC, you can't really hide the flaws and play up the strengths like you did with the DAC.

Or maybe I had it backwards and you could use a good DAC and some sort of sigma-delta like trick to make the shitty GPIO - ADC work.

Fun stuff to think about, but I suspect the real innovation will happen when someone in hardware realizes that DAC/ADC/FPGA technology has slowly and surely advanced far enough that they can do to the ultrasound market what the DS1054Z did to the oscilloscope market.
Like the Luddites?
There are a lot of good code review tools. If you want to do pair programming then do it async using code reviews. Doing it sync is just wasting two peoples time.
The only thing making me hesitant to give a simple yes/no answer is the implication of tieing my example to a "hip-hop mogul wearing a half-pount of gold chains around his neck and $400 basketball shoes on his feet" - are you trying to imply these people are systematically black? And if so, are you trying to imply that most rich black men dress like this?

If you are (which I don't think you are), I think you can answer your own question.

If not, then I don't think the comparison stands: you're implying a wealthy individual ("a Hip-Hop mogul") is representative of a whole race when his circumstances are (for lack of better wording) merely an exception to the rule, whereas "rich white men" is, objectively, a non-misleading statement, as white men are statistically the wealthiest demographic.

Of course, I could have read to deep into your question entirely - I'm not an expert in this field. Thank you for the thought provoking discussion regardless, though.
You're making a number of assumptions yourself.

>For one, TortoiseHg isn't windows only. It's a python+qt based application that works uniformly pretty much everywhere.

Yeah, admitted this mistake elsewhere.

>That fact that you made that assumption makes me thing you may not have explored many alternatives. I'd recommend trying out some other VCSes, just to get a broader picture of how they function. I think doing that helps to get a grip on what your specific needs actually are, as well as a better understanding of the tradeoffs for whatever tool you pick. None of them I've seen are 100% superior.

I have used, in this order, visual source safe, TFS, SVN, Hg, git.

>Secondly, I love tortoisehg specifically because of the command line. Doing a simple commit with mercurial just takes `hg ci`. Doing a commit using the gui just takes `thg ci`. The latter one pops up a gui for me to stage the commit, and then I'm back in the console again.

Doing a simple commit with git is just git commit. What am I missing here? You could alias it to git ci if you want.

>There are some things which I think are just fundamentally better with a gui -- whether it's a curses-style "TUI", or proper graphics. Under tortoisehg, if I'm cherry picking for a commit, I can double click to open up a file in meld to make last-minute edits, shelve bits away for later, all kinds of one-off actions which are much more complex from the command line. Not to mention performing complex searches on VCS history.

These aren't more complex on the command line, they're just done differently. They aren't as intuitive as a GUI, where the button is presented to you rather than having to read about a flag in the man pages. But VCS is a tool you use all day every day, it's worth it to learn about it in depth.
As a relatively new Rustacean (since May 2016), I have to say that Steve has been one of the most influential people on my Rust coding style and understanding of the importance of community in a language. Prior to talking with Steve on IRC, I believed that community was secondary to language quality, but now I fully understand the importance of strong community in a programming language.
A) the human feeds the cat, with delicious wet food, every morning. Many cats are only fed once daily anyway, this cat is fed twice daily.

B) When traveling, one is not at home to feed the cat, at all. If fed, cats are quite content to have the house to themselves for a few days. If a cat is disciplined about eating, you can just put a lot of food in the bowl and leave it alone while you travel. If not, you need to build a machine to dispense food, or pay another human to come by and feed the cat.

C) I often enjoy reading stories about the process of engineering (iterated problems, solutions, new problems, etc.), even if the final result is 'over' engineered.
That is amazing. I'm so glad I can just free feed my cat with out her getting obese, or even fat.
This was previously submitted before by the author: https://news.ycombinator.com/item?id=11938405

His homepage: http://mapmeld.com/
Fascinating person. Has worked with various languages and does educational work throughout the world with OLPC laptops.
It was the Renaissance and the French Revolution. And yes, the printing machine helped the spread of ideas. But so did Voltaire, Thomas Paine, the Quakers, etc. You cannot have progress and freedom without humanistic disciplines.
I really am doing it (I also really am publishing a bunch more challenges). I just had dinner with Patrick last night and talked about it a bit. I've got a lot on my plate at the moment, though.
simple systems can appear complexed because there are many buttons. You often only have to use just a few buttons, where the rest are for special ocations.
When visiting Maui, I was surprized how sugar cane spread like weeds in many places around the island. I don't think it was classified as "highly invasive" but it looked invasive.

But I didn't get a chance to ask any Hawaiians about it.
What does this mean, "specifically compromised"? You bought it compromised if we are being congruent with these sorts of accusations or precautions. If you assume the Echo is always listening, you should also assume that Apple, Google, and Facebook are also always listening... and, in fact, I recall earlier this year a quite vast conspiracy that Facebook did exactly that[0]. This was denied by Facebook, for the record – or do you not believe them?

0. http://www.independent.co.uk/life-style/gadgets-and-tech/new...
I think the problem with consumer Wifi routers is that they pack so many features in them (that few people need or use, but hey, if you're comparing specs and one router is also a USB print server and the other is not, you may as well get the one with the extra feature even if you'll never use it... just in case). All of those features lead to code bloat, bugs, and dilutes development resources so they spend less time on core Wifi functionality and more time on features that I'll never use -- I know I'll never use my Access point as a cloud storage server.

I've been much happier with my home worker after I traded in my all in one AP + Router/Firewall with a discrete firewall (pfSense) and Ubiquiti AP that's only an AP, nothing else.
You're right, it's not moved across remotes. I'm just confused to why the information would ever be needed. It seems to not have any real use case. You can recreate a branch any where at any point in the history, why would you care what commit a branch originally came from? It seems like a solution in search of a problem. Or maybe even a solution to a problem that shouldn't need solving in the first place!

>If I make a fresh clone of a repository, that doesn't tell me what the branch was like a year ago.

This isn't true with Mercurial either. A lot can happen in a year, and it might even make the information misleading (having similar named branches, history deletion, etc). It's useless at best and misleading at worst.
The fear would be palpable, but on most of those instruments, the modifications were done in the 19th century, as the modern violin was developed. They changed the size and shape of the bass bar, and the geometry of the neck. Also, the materials and construction techniques all lend themselves to repairability.

Just holding one of those instruments would make me nervous, but in terms of both maintenance and use, they were made to be played. This is just something that people accept.

I obviously don't play a Strad (he didn't make double basses, that's my excuse), but when I got a nice new bass, people asked me if I'd ever take it out of the house, or if I'd use my old bass for performances. I tell people the same thing, it was made to be played.
With USB-C now common for power, you could power the laptop off a USB PD capable battery like this one:

https://www.amazon.com/30000mAh-Portable-Charger-Outputs-Mic...
It'd be like deploying an update before leaving for your honeymoon!
>GUIs are better in the exact opposite case: when you have a constrained set of actions to perform, but a large number of subjects they may be performed on. In that case, the problem isn't expressing the action, it's picking which subjects to act on (pick these lines to commit, oh except let me edit that one, put that one aside, ok back to the commit i'm staging...).

Those examples are not only possible, but easy to do in the CLI for an advanced user. I do that sort of thing every day.

I agree that some tasks are better suited to a GUI and some are better suited to a CLI, but your VCS is firmly in the latter camp imo.
Having a feeding machine that operates on a regular schedule when your schedule is anything but does not mean you're being a delinquent pet owner. It doesn't mean you're oblivious to your pet's health.

Some people have automatic coffee makers that run on a timer. Does that make them indifferent to their own health?
If you want my money you have to tell me what I am getting otherwise its just extortion. You could argue that state sell market access (which is perfectly ok) then yes its ok for states to compete.

> they pay taxes because we all have to pay taxes to do the things we want to do

What others do with their money is not my business.

> (provide education for our kids, have a police force to deal with crime, build and maintain bridges and roads, etc.)

I would argue that it does not cost that much and the services/goods being discuessed are _extremely_ overpriced. And the price does not just include money but personal freedoms.

But ofcourse how would we know that its overpriced. Hence why I suggest compitition between states is good thing and should be encouraged or It might be you who become the next target for majority's whim and then nowhere to go.

I am not judging people who want to live under socialism/capitalism/any-ism. I am just saying more choices/compitition is better for everyone.

Also read Private Cities [1].

[1] https://fee.org/articles/private-cities-a-path-to-liberty/
> You also sample at a rate > to the centre frequency

To be clear, a sampling rate that is only greater than the center frequency isn't very useful. You need the well known nyquist rate, twice the maximum frequency to avoid aliasing

https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampli...
Congratulations on the work to make our computing infrastructure safer.
The red light is from optical digital audio, as the 3.5mm audio port is actually a combined 3.5mm+mini-toslink port: https://en.wikipedia.org/wiki/TOSLINK#Mini-TOSLINK

You can easily get rid of it by deactivating the digital audio port. Still this problem shouldn't exist from the beginning.
A question to all of you who only work remotely, and I'm sure it's been covered by HN so forgive me, but where do you find reliable work that's remote? I can see getting lucky maybe and scoring one maybe two gigs that allow remote but a caterer doing it? When my wife's gig is up she would love to work from home. She already works from home two days a week.

But she has no idea how to make a career out that reliably. She started out doing QA/testing, now she is all into oracle and DB2. Using oracle tools and IBM tools for managing/writing SQL for enormous databases. Government sized databases.

She is making low six figures now here in KC.

Thanks for any advice or leads on remote only work as a career!
Feature Flags with a Git backend.

https://github.com/vsco/dcdr

Disclaimer: I don't work at the company anymore, but I worked on a previous incarnation of the tool.
The only rational reason to work as an employee of a startup is for better job titles, working conditions, and professional development (from tougher challenges). Getting paid in lottery tickets is not sound investment strategy.

You may be a better informed investor if you pick the locks on the filing cabinets in the C-level offices after the bosses go home, and bug all the conference rooms, but it is unlikely that will make you better at estimating the future market value of the company, or at evaluating potential buyout scenarios. In any case, I never thought that spying on my bosses was a good idea. I just heard the lies, saw through the BS, and started sending out resumes. Or I got blindsided and started sending out resumes.

You should only work at a startup that will support the lifestyle you desire. If you were really critical to the company, you would have a contract and genuine equity, rather than being "at will" with a promise of options vesting later. Your primary concern should be "can the company continue to pay me for my work this month?", and your secondary concern "can they pay me next month?", and so on. As an employee, you are a replaceable worker-for-hire.

If you want to win big at the startup game, be a co-founder with undilutable equity. If you want to invest prudently as an employee, you can play the entire market rather than just one small, potentially volatile company, and a bigger cash paycheck makes that easier to do.

Employee option grants just seem like a con to make peon-level employees feel like they have more agency and more emotional connection with their employer than they actually do. The anecdotal success stories of option grants that actually pay off are necessary to keep the game going, just as state lotteries have to blow some money on oversized checks, balloons, and confetti whenever someone wins the jackpot.

The company's money does not come from a vacuum. No matter what amount of profit you get from an option grant, the company could have given it to you in a different, less complicated way. If you exercise 1000 options, and have to sell 500 of the shares to cover the exercise price, the company could have just granted you 500 shares directly, and still had 500 left to give out later. The hand-wavey sort-of-options are 100% there to benefit the company, and its owners, and their tax preparer, not you.
> Which branch was commit `B` made on

You can do some basic heuristics to figure it out, but I'm not sure what the point of knowing this is.

>What did the `bugfix` branch look like one commit ago?

`git checkout bugfix; git log bugfix^1`