skysight-inc/HackerNews huggingface dataset:
It's every six weeks rather than every month, and the fact that it's like clockwork is what's so impressive! I've actually implored the Rust devs before to slow the release cycle for their own sake, it seems to be quite brutal. They must be masochists, because at least some of them have told me they enjoy it. :)
Google Loses Top Hardware Executive It Poached from Amazon
You do realize that that wasn't intended to be a serious argument about the points of Ada vs. Rust... right? Have you seen "MongoDB is web scale" (https://youtu.be/b2F-DItXtZs)?
Not cool bro
http://www.webmhs.com/2017/04/prediksi-skor-real-madrid-vs-v...
Ok, I've used TS while contributing to OSS written with TS and I've used Flow extensively in production settings.

The main takeaway for me is that TS is much much less sound than Flow. That means it checks less invariants which in turn makes you less trust it...

Consider the following code which is valid (!) in TS:

let promisedString: Promise<string> = new Promise(
resolve => {
// Perfectly valid in TypeScript!
resolve(42)
}
)

Another downside of TS is poor type inference. It requires to annotate each top level function while Flow only requires to annotate exported functions.

Even the following simple piece of code will make TS ask you to annotate doAddition function:

export function addition(a: number, b: number) {
return doAddition(a, b)
}

function doAddition(a, b) {
return a + b
}

I'm really glad Flow doesn't force me into it.

Edit: spelling
Agreed on all points.
"h*ckin"

That's some intense censoring
Yeah. That's definitely something we looked closely at. I'd say the main difference is that OctoDNS abstracts away the details of the specific provider so that you write a single config that can be pushed to one or more places and changed over time without having to touch the records themselves.

Terraform requires creating a resource for each record and provider pair. It's good for orchestrating a single provider especially when you're otherwise creating associated resources with Terraform.

The custom DSL for each provider varies thought and I wasn't happy with my attempts at trying to abstract away which provider(s) things were going to using modules. The result wasn't simple enough that anyone at the company, not just engineers, could submit a PR for.
I would definitely side with it being okay. I like how string are modeled, but it doesn't mean it isn't painful sometimes. Making some common string operations like &str + &str defined but linted is a good balance of ergonomics and efficiency (that'd be a rare bottleneck, but the lint would make it visible).
It is possible that adding two str slices like ("a" + "b") could be implemented in the future to produce a new owned String, but there is a technical obstacle to doing this in the near term:

https://www.reddit.com/r/rust/comments/67rjii/question_about...

The basic problem is that str slices exist in the "core" library, which can be used on targets without an allocator (for example bare-metal embedded systems), while the owned String type exists only in the "std" library, which requires an allocator. Rust has rules that prevent one library from stomping on another library's types in certain ways that could conflict with future API additions, and those apply to the standard libraries here. (One solution would be to allow the author of libraries A and B to declare that A is allowed to treat types from B as though they were its own.)
I respectfully disagree with everything you said here. Firstly, you are speaking in vast generalizations about what being a "developer" means. You don't need 10 years of experience with 5 distinct languages to be effective or not a liability. That's bullshit.

I am curious - what kind of development are you referring to here? What kind of things do you think people need 10 years of experience with multiple languages to be effective at?

OP - don't listen to this guy. Focus on writing clean, simple, non-abstract code that reads like a book. Make sure your code reads well and is written with performance taken into consideration and you'll be fine.

To answer the original question - common things I have seen from bad developers are the following:

1) Over complicating/engineering solutions to simple problems.
2) Not using readily available libraries that solve 99% of the problems you'll run into.
3) Naming methods and variables abstract things that don't accurately explain what they're for.
4) Not asking co-workers for help/domain knowledge before they start coding.
"Astroturfing is the practice of masking the sponsors of a message or organization (e.g., political, advertising, religious or public relations) to make it appear as though it originates from and is supported by a grassroots participant(s)"

So pushing articles on HN and other outlets doesn't qualify I guess?
PATH runs on its own tracks, between the IND local tracks on 6th.

The cross-harbor tunnels are cast iron, and are not straight.

The PATH and NYCT systems are incompatible. I think they use the same track gauges, but NYCT cars (either division) are too long to navigate some of the curves on PATH.
Indeed. Being stuck with the fixed page format is like being stuck in the "horseless-carriage" mentality. A4 or whatever paper sheet format should be completely abandoned in favor of dynamic text formatting - not unlike what browsers can do when displaying HTML.
Why not use Protonmail? They even have an IMAP bridge these days..
Disappointed. I was expecting a dictionary or something with a bit more structure.
sys.version_info gives you a tuple, which is way more convenient for comparisons than sys.hexversion:

if sys.version_info >= (3,):
... # Python 3.X code

Or you could check whether str is bytes:

if str is bytes:
... # Python 2.X code
How Ajit Pai's Plan Threatens Small-Town America
"Harsh realm" = "bummer"
I'm a firm believer in using the right technology for the problem rather than simply the technology that you know best. I'm actually hoping that .Net becomes more appropriate for more tasks (especially on Linux) but for now that's not the case.

But the point is that having a bunch of radically different technologies for every task is far from optimal. You simply can't master them all. Right now I made a bunch of technology purchases and I'm looking at Unity development, Tizen development, and Android development all at the same time along with the usual day to day .net stuff and it's way too much. Having a single language/framework would make it a lot easier to produce a result.
Slidium – Mac Markdown presentation editor
From the moon you can more easily mine asteroids for raw materials.

From the moon you can launch 1960s tech Orion pulse nuclear ships to the rest of the solar system with 1 month transit times.

From the moon we can build out more space station infrastructure in earth orbit.

From the moon we can build a space elevator.
This is actually being discussed on /r/rust, see https://www.reddit.com/r/rust/comments/67rjii/question_about...

Turns out my assumption (like C++, make expensive things more verbose) isn't the complete picture. The big blocker is a technical issue preventing `"" + ""`

See https://github.com/rust-lang/rust/issues/39018#issuecomment-...
People were building things for the hardware they had back then. No need for smooth animations when nobody's managed to display an image yet, etc. No need for flexible scaling web pages when all the screens are generally the same aspect ratio.

Where am I going with this comment... I have no idea. I guess our tools have scaled as the needs have scaled? More complicated webapps led to more complicated debugger tools (I personally would find it extremely hard to do my job without 1. Chrome element picker + CSS editor and 2. Chrome Debugger).
Don't worry about it. Some of these things hit at different times, and this place is often a chaos engine for timing.

The song is nice, but I think the story of the song and the sidebar with the story of anoncvs is a pretty cool point in OS history. The idea of an active code control available to the public had to evolve like all the other ideas and the origin is pretty interesting.
And note that if you're using rustup to manage your toolchain, you can now use it to install and manage RLS for you as well: http://www.jonathanturner.org/2017/04/rls-now-in-nightly.md....
Chrome will start marking HTTP sites in Incognito mode as non-secure in Oct 2017
Personally, I prefer the look of old-fashioned suspension bridges.
Treats other people like crap. The better someone is, generally the kinder they are to other folks. Crap developers seem to have an edge to them- it's as if they're afraid they're going to be found out as not being as skilled as they portray themselves as, so they try to avoid that by demeaning others.
What bullets do to bodies
Barrett Brown Arrested for the Most Ridiculous Reason Ever
Hey there - I went down a similar road as you about a year back when I looked for a file backup solution.

I started with Dropbox, and attempted a sync of my local files. Within minutes the Windows app crashed.

I switched to Google Drive, same thing. Synced a large number of files and the Windows software crashed.

Even Tried Insync, still had crashing issues.

Researched the issue and found that both clients are limited in the amount of RAM (32bit vs 64bit) and this limit is easily reached when syncing tens-of-thousands of files causing the software to crash.

Neither provider offers a 64 bit version, or a version of their client software that handles syncing jobs this large.

I finally settled on Backblaze which was affordable ($5/month), and "just worked". The files aren't as accessible as Dropbox or Drive, but I still use those for the files I need/touch often, and use Backblaze for my "entire PC" cloud backup solution.
There have been many military crashes with nuclear weapon material on board, some resulting in its dispersal.

https://en.wikipedia.org/wiki/List_of_military_nuclear_accid...

I'm not sure why this alleged one is particularly noteworthy.
This is an issue even with non-GPU-based OLAP engines. See, e.g., Clickhouse (https://clickhouse.yandex/reference_en.html):

"We'll say that the following is true for the OLAP (online analytical processing) scenario...Queries are relatively rare (usually hundreds of queries per server or less per second)."
My personal Gem in this release: Generic parameter defaults. [0] This makes altering a generic interface or a generic type alias in a non-breaking way much easier which is very powerfull in a large code base.

[0]: https://github.com/Microsoft/TypeScript/wiki/What's-new-in-T...
This makes me feel slightly less lost than when I am watching episodes of the pengest munch. I am totally uncool.
If you are interested in Open Hardware, it is worth to take a look at the CERN's Open Hardware repository:

http://www.ohwr.org/
It's been a long transition, yes. So long, that 4-5 years ago, developing a new application in 3.X was a non starter. Hence, 2.7.

Now, you have 2.7 apps that are very mature, stable and reliant on lots of little things. Okay, big job.

Now let's throw another wrinkle into this. You can pay good money to develop your next feature, or to port your system to 3.x. One adds real value to your customers and improves your bottom line. One lets you say you are on 3.x and gets nods of approval from random programmers.

What do you think a business is going to do? Exactly.

When will we eventually port? Sometime shortly after 3.x becomes the overall standard. THIS is actually what we are seeing right now, which is great, but that hasn't been the case up until the last year or so.

>Any technology that lives long enough eventually has to transition its customer base.

While true, this costs money, time, and effort. So you better be damn well sure there is a good ROI that is something more than "This code that nobody but programmers see is more elegant and properly structured".

There's a reason banks are still using COBOL after all...
Make one team responsible for maintaining logs and they get to decide the "how". This is most likely Ops. Devs are now a customer with requirements and Ops should find a solution that will both meet their needs and the needs of devs. That will at least stop the bikeshedding.
In defense of the person you replied to, I had the original question framed around my situation more but edited it to be more generic. Thank you for the information!
Smartphone-Controlled Cells Could Pump Insulin for Diabetics
> Remember that while Steve Jobs infamously called Dropbox a feature, not a product

Which is the best selling point of Dropbox. It doesn't try to be an office app suite, a photo editing solution, a cloud collaboration platform, etc. It just syncs files between computers and phones, and has simple UX because of it.
Mr Wernquist made some excellent shorts. Would pay to see a 2+ hour feature in Imax. Sagan commentary/mix would great, but not required.

http://www.erikwernquist.com/
The 3.1 version[1] of Systemagic was always a fun one to blast in a server room. I remember the song it parodies being an early video music channel favorite but the name escapes me.

Quite a few of them tell the history of the OpenBSD project and some of their thoughts on others. I also love the illustrations.

1) https://www.openbsd.org/lyrics.html#31
This has a lot of problems.

First, legal problems: you can't have a unisex multi-stall bathroom in the USA. I'm not sure if it's actually illegal (it probably is in many states), but it'll never fly even if it is. Honestly, what you really need is a male restroom that's about 5 times the size of the female restroom. Again, that won't fly politically, but practically it makes sense because there's so few women in software. Better yet is to just ditch the shared bathrooms altogether: they're nasty and smelly, and it's inhuman to have to sit on the pot next to someone with only a crappy divider which doesn't even go to the floor so you can see their feet and their pants around their ankles. You also have to worry about Idahoans playing footsie with you in there. Whoever came up with this idea has serious mental issues, and somehow it's the norm almost everywhere. Instead, just have separate 1-person unisex bathrooms, and put little showers in at least 2 of them for the cyclists.

The walled offices with giant windows: these windows are much too large on the inside. The whole reason for a walled office is to have privacy, and you're taking it away with those windows. Also, you're distracting the people sitting inside because they'll see all the people walking by their office, since that office will most likely open into a high-traffic corridor. Make the windows much smaller, maybe enough to see the top of the head of someone sitting inside and that's about it. Or just get rid of them altogether, or maybe have frosted glass. Windows on the other side are nice, but there's only so much space along the outside wall of the building, so who gets to sit here? Likely only managers.

The dedicated "quiet alone-time" places are great, but there aren't nearly enough of them. They're going to get monopolized, while all those "team spaces" are going to get ignored mostly. How about just having only the quiet 1-person places, and just one or two of the team spaces for the people who really like that or in case something comes up where people want to work as a team temporarily?

The library isn't a bad idea, but it's not nearly large enough.

The "townhall" is a massive waste of space. You don't need daily stand-ups, that's a patch for lousy management. The building should have a large meeting room shared by all departments for events where you need everyone present.

Honestly, we'd all be better off if we could go back to the way offices were in the 70s or 80s, minus the smoking inside part.

I do like his illustrations though: it reminds me of playing Duke Nukem 3D.
It was considered career limiting for my generation. Don't know if it still is now, or if the younger generations simply don't care.

Outside of the "Why I Left" posts, a lot of younger people put a lot of content on social media that my age peer group would consider "career limiting".
How to fix a sticking door
Show HN: A Python, Mongodb and JSONSchema based object model wrapper in ~300 LOC
Intense books on nation building
Is this SOAP 2.0 ?
i, too have a lib in this space (color quantization):

https://github.com/leeoniya/RgbQuant.js

playground: http://leeoniya.github.io/RgbQuant.js/demo/
The main reason was the YAML config file could be easily understood. Since switching things over to use OctoDNS a couple months ago we've had nearly 75 PRs to make changes, mostly internal/testing/dev, but plenty of real stuff too. I don't have an exact number, but skimming over those there's probably ~25 people who have made those PRs.

In order to make it possible for anyone at the company to make PRs, not just SRE team members, we had to minimize or eliminate the learning curve and YAML was the best option for that we could think of. In the past those 75 PRs would have instead been issues asking an engineer on the infrastructure team to make the changes. It's been a huge and positive shift.
> Paxos.com

I'm confused by the relationship between Paxos, the company, and Paxos, the algorithm. Do the authors of Paxos work for Paxos?

Edit:

https://en.m.wikipedia.org/wiki/Paxos_(computer_science)

Ah; both are named for a fictional financial systen
If only it were symbiotic. It's parasitic.
https://twitter.com/Pinboard/status/857662627496906752

"“EBITDA profitable”, n. Technical term used in accounting for companies running at a loss"
If he shoots you and takes your land, then he may be rightfully punished for murder and theft...

I never claimed I didn't want laws. Only that property does not issue forth from the state.
Like CORBA, EJB, RMI, and a pile of other rpc libs and specs that died over the past 40 years.
Twilio Video 1.0.0
It doesn't mean anything, at least not anything correct.

REST defines media formats, and the relationships are described by hyperlinks in the media.

GraphQL is much the same in that it has a relational schema.

The difference is that GraphQL has filter and join capabilities. Vanilla REST is usually all-or-nothing for a resource.
Cellulo Introduces Classrooms to Tangible Learning with Robots
How would you rate your young self on the "hello-my-name-is-scale", as I like of to think of Stroustrup's notes in his short article from 1999[1] -- in C and Ada at the time? Would your C code "blow up" differently from your Ada code, do you think?

I'm not much of a fan of C++ myself, but I often find myself looking back at that short note, as a pretty valid criticism of how C tend to mix some parts that appear simple with some very complex actual behavior (eg: printing strings, reading in strings and integers).

[1]
http://www.stroustrup.com/new_learning.pdf
"Learning Standard C++ as a New Language"
Idyll makes it easier to author interactive narratives for the web
I've been using both for a few years (TS at my old job, es6 at my new job but we're moving to TS so now I'm using both depending on what I'm working on).

The use case I like most about typescript is it makes refactoring and making changes really painless. For example, in an angular app, you may have a service that several components rely on. When changing a method signature in the service, you'll get compile-time info about any other usages of that service, and you feel a lot more confident about making changes without something dumb slipping through the cracks and causing bugs in production.

This confidence generally lends itself to less fear of change and more willingness to refactor, which leads to a better/cleaner codebase.

Aside from that, I love the JSDoc comments showing up as you type, especially if you're working on a team in which you may not know 100% what everyone has worked on.

Other features I use every day and love:

-automatic/generated import statements

-type definitions for libraries (most have solid documentation)

-control-flow logic checking (you'll find more bugs than you think with this and it encourages more defensive programming)

-transpiling down to support older browsers (babel does this too but it's nice to have it built in)

Edit: I forgot to go into the "cons" list here.

-there's some finagling you'll have to do with some of the more poorly-written npm packages that strap themselves onto globals

-there's a slight learning curve

-you'll require a build step (with es6 if you're targeting es6-only browsers you can deploy just static files, but most people use webpack/babel anyway for older browser support and other things webpack gives you like bundling/minification/etc)
used as a dependency in another lib: GIFter based on omgif & RgbQuant:

https://github.com/leeoniya/GIFter.js

demo: https://cdn.rawgit.com/leeoniya/GIFter.js/9b888495/demo/inde...
> Sometimes heck is censored as h* ck. Matt Nelson, who runs the WeRateDogs Twitter account (@dog_rates), says tweets from WeRate popularized h* ck and its derivatives. "I'm sure someone else did that before," he says, "but it was something original to me and I used it to such an extent that people associate it with [@dog_rates] now."
You will always be stuck to a certain stack, specially in countries like Germany where what HR department cares about is what language/tooling you did use during the more recent years before the interview.

Usually knowledge learned on side projects are not taken seriously by them, as they weren't on the job. Oh and they love paper (certifications of all sorts).

Algorithms and data-structures always transfer to any stack. Learn the CS mathematical foundations of them.

A good way to avoid being stuck with a certain stack as you put it, is working for a consulting company. It is way easier to jump stacks when switching projects than than trying to convince random HR department of what you actually know.
South Africa's proposed cybercrime and cybersecurity bill
What about the cartoon scenario where there are 2 people on the Moon and 1 kills the other?

Is some Earthbound rule then in effect?
Max for Live is probably particularly relevant here, as you get the full compositional power of Live, plus the flexibility of Max/MSP
that's the joke
that is a truly beautiful bridge. there's a very nice looking one in dallas as well, though i didn't have the words for its type until just now: https://www.google.com/search?q=hunt-hill+bridge+dallas&clie...
Android: Getting up and running on the iMX6
This is hardly a new bridge design, nor is it new to regions that have winters. Chances are ice has been accounted for.
"Pai argued that rolling back the rules will encourage ISPs to spend more on their broadband networks, speeding the spread of high-speed Internet across the country. He also claimed it would create new jobs and help protect Internet users' privacy by returning some authority to the Federal Trade Commission to sue companies that violate their own privacy policies."

So, "create new jobs" is the new "think of the children" in politics. If you want to get anything done in the current political climate you just have to utter that magical phrase and everything is OK. Based on this, I'm going to view any policy that claims to create jobs with the same sceptical eye as I used with the children fear mongers.