skysight-inc/HackerNews huggingface dataset:
I'm going to assume (hope) that the mistakes in your comment are intended to be ironic.

That's just wrong though. It can be incredibly useful to think about how you communicate and try to change. Trying to ape someone else's communication might be doomed to failure, but you should reflect on your own communication, on specific cases where you felt interaction went especially well or poorly, and see what you can learn from them. If you think about it often enough, eventually you'll just start using the ideas you come up with in your regular communication naturally.
If I missed the notification that an infinite loop was costing 13 cents a minute by the end of the day I am out almost 190$. I know the rational that Amazon has is that you would want to scale your service if you were adding hundreds of people in a single day but thats a lot less likely than an error in my code flushing a relatively considerable amount of money down the toilet. If that was not a risk though I would be using Lambda, it otherwise seems like my best option. Backend is not my forte though so if the point seems crazy I'm willing to consider any advice.
Can someone show or explain:

1. An example of how this could be used.

2. How to do something other than just drawing the cards.
How World of Warcraft led to Glassdoor
AWS is the best in the game and you pay a little extra for it. If you ask me I think it's worth it.

I wouldn't waste a single cycles migrating to another cloud providing to save a little money. In the end it simply won't be worth the time and you'll miss running on AWS's mature platform.

Instead, I would focus on getting your app working perfectly within linux containers. Use some existing tools such as swarm, CoreOS, or Tutum[0]. Once you have your app properly containerized, you'll be able to quickly move between clouds or even utilize multiple clouds (provided you have the time or experience to maintain the network).

The only way you'll save significant money is if you're willing to put up the resources to run your own prem, and I would strongly discourage you from doing that.

[0] https://www.tutum.co/
Using the word belief makes it sound like we're discussing religion here rather than politics. A belief is an attitude toward the likely truth of something. It isn't possible to literally believe in guns or abortions, one can only have opinions regarding their proper usage. This is likely why OP finds political discussions irrational - he is investigating political "beliefs" and when it becomes a debate of Truth by believers rather a debate about the best policy for the context from people with varying perspectives and opinions then of course nothing can be conceded; beliefs are fixed by faith while opinions can vary considerably.
Think they missed editing out the final "Text Magic now to get started:" at the bottom of the page.
I agree - Defining a 'Stack' class is useful even if it's just a wrapper over LinkedList, because stacks have an expected way to act, and while a LinkedList fits the bill it does more then a stack actually has to do. And with that, nothing says you have to implement a 'Stack' with a LinkedList, it's just an easy way to do it. By defining the 'Stack' class, you could always go back and improve it to not use LinkedList and instead do it yourself.

That said, I do agree with the author that, in the context of a programming class, writing the 'LabStack' class is absolutely useless because it teaches you nothing about actually using a linked-list to implement a stack, which I'm sure was the real intent of the assignment. The 'LabStack' class is useful in the context of being used in a larger program, it's not really useful for learning how to actually implement a stack because it just passes the implementation off to 'LabStack'. (That said, because Java doesn't support defining objects as value-types, using the 'LabStack' interface adds an extra level of indirection you may want to avoid - You have to access 'this.list' to get the LinkedList object, instead of just accessing it directly. This is more a fault of Java then anything else though.).

The note about programming class isn't really relevant to programming as a whole though, which is where the disconnect happens.
Seems to be the case, I see.
JavaScript to Elixir
Try launching a few programs (double-click the floppy disk after each one to open the MS-DOS Executive again) and then move them around.

It's a tiled window manager!
Another important thing is to know what is more engaging than a text message to your conversation partner. (If the answer is nothing, then maybe stop talking to that person.)
The man can't even grasp the differences between special forces and special operations. Sensitive comm gear most definitely would have been smoked, but not with concussion grenades.

So manyittle things wrong here that I can't give any credit to anything in this dumb article
Wouldn't be the first, or worst, marketing whore-out to happen these days
I think example 9. (the stack that wraps a linked list) is not a necessarily an antipattern. Removing degrees of freedom and adding obvious constraints make systems simpler and easier to comprehend.
What It Will Take to Create the Next Great Silicon Valleys, Plural (2014)
I like how the first three or so anti-patterns are in the exact opposite direction as the last three or so. The art of being a programmer is literally "don't waste time over-thinking things, but also don't ship under-thought trash". For all our fixation on simplistic and ease of use, programming is actually incredibly difficult and way more art than science.

And it's exactly this requirement of masterful manipulation of balance that makes me love this field so much and long to get better at it. Getting a handle on the artsy spirit of programming is really what separates the wheat from the chaff in terms of programmer skill. There is no formal programmer guild in real life, but if there was, and there was some sort of test a journey-man programmer must undergo in order to become a master programmer, it would be the test of being given a large project and then deciding correctly exactly how much technical debt to take on to be able to ship a product within a reasonable time-frame and yet have its internals not be complete unmanageable spaghetti.
Go Lang: Comments Are Not Directives
Go 1.4 starts to use comments as directives. I think that is a realy bad path to go on the long run. You see its beginnings in following 3 examples:

# used to set a canonical import path for a package:
//import "foo"

# used to generate code:
//go:generate bar

# used to document the result of a example function:
//Output: foo

Comments should not be directives. Comments are free form, they do not have a syntax (as demonstrated in the examples). Comments are for humans - programms should ignore them or threat them as - comments!

It is my optinion that if Go needs some kind of annotation, than there should be a new syntax for it.

I would propose that directives to the tool chain will be marked with

#TAG: DIRECTIVE

a tool would be able to register the TAG with the go build environment. If a TAG is found in the code - the tool is called to do what ever needs to be done.
Well there's an entry point of course, but it shouldn't know much. Your entry point knows about your option parser which knows about the high-level actions your program performs which know about the sub-processes involved in accomplishing them, etc.

It's important to keep this graph as acyclic as possible, and to try not to have any one component directly interact with too many other components, because then your abstraction is too fragile.
Be inspired, as we were, by the terrible and strange creations at the original (NYC) Stupid Hackathon.

And the topics (the problematic ones of which I listed) clearly suggest they are anticipating similar content. If you want to defend both hackathons, please do so, but don't try to win this argument on an irrelevant technicality.
> Which is why the message of "Not Invented here" is a good one to repeat over and over.

So, there is a problem where many developers would rather work on abstractions rather than concrete value-providing things. I suffer from this myself - if abstractions weren't interesting to us, we wouldn't be working in software.

However, over the years I've discovered that many software projects are gaining negative value from some of their libraries, and I'm not sure which is the larger problem.

http://yosefk.com/blog/redundancy-vs-dependencies-which-is-w... describes the essential problem.
The site looks good. I feel that the devops world is hungry for a _full_ replacement of graphite/zabbix/reimann, etc, but the pricing hasn't been appealing enough for the best tools.

Per-host pricing schemes punish large installations and engineers who've created services that run on small, horizontally scaling instances.

In the end most of us end up with some wacky combination of different services.
Coincidentally, I'm reading "IBM's Early Computers" and this book says the first personal computer was the IBM 610 (originally called "Personal Automatic Calculator"), introduced in 1957! It consisted of a desktop keyboard with tiny CRT, along with a typewriter-style printer. (Off to the side was the freezer-sized cabinet full of vacuum tubes.)

Personally, I think it's hopeless to try to pick the "first personal computer", since the term can mean almost anything.

More info on the IBM 610 is at http://www.columbia.edu/cu/computinghistory/610.html
Right, but your window size example would be a case of using the same value in more than one place, so it would be better as a named constant.

Actually, the whole example smells ripe for refactoring. Where are there multiple windows throughout the app all sharing a default starting size? Sounds like it's time for a base class or something. Once you've eliminated the redundant sizing code, you will find that your default size values now exist in only one place (the base class). Since they are only in one place, you can write them as numbers again instead of named constants.

I've played this pattern out more times than I can count. The problem isn't magic values sprinkled through the code; it's having redundant code in the first place. Once you solve that, the magic numbers tend to evaporate.
Yes it is! Wow, small world. I will reach out to you actually, I am interested in learning more!
It would be interesting to see this group do a similar test on speakers. They have a nicely designed experimental setup.

A speaker test should show a clear cost/performance relationship.
I think it was just a fun side project. But as to how it could be used.. just a few weeks ago we were at a hackathon and built a quick poker texas holdem game. A library like that (arguably a bit more comprehensive) would have saved us a few hours.
That's what I've been wondering - why don't the browsers add a few more scripting languages, like python? If IE didn't exist, Chrome and Firefox could do it, just for fun, they're very open to new features.
I've found DO is great for running RabbitMQ as a hub to process background jobs across multiple VMs. It's relatively simple to hit DO's API to spin up new "droplets" as needed so your queue never gets overloaded. I use this architecture to create over 1MM website thumbnails per day across 10+ VMs and it's been extremely reliable.

I currently use App Engine to handle front end requests and storage so I can't comment as much there, but DO's integration with Mesosphere sounds promising for scaling and reliability.

More here -
https://digitalocean.mesosphere.com/
https://www.digitalocean.com/community/tutorials/an-introduc...
Al Raha Beach Apartments
This doesn't work if the conversation is important to you but not to them, such as if you need their input on something.
It was covered in depth at http://lists.gnu.org/archive/html/parallel/2013-11/msg00006....
I think it matters because Zero Dark Thirty created the impression of heroic American intelligence operatives tracking down Bin Laden and engaging his body guards in a firefight. The reality is it was a mob style hit on an elderly man. We Americans have a tendency to glorify behavior that is in reality very ugly. This is a bad habit that leads to self-delusion.
It reminds me of the quip:
"I can deliver your project quickly, cheaply and of good quality - pick two".
That said, in my experience, clients tend to see software quality as the least important attribute of the three.
Why conform to arbitrary conventions when they don't make sense? Personally I think the best reason to conform to REST is because the user expects a "good" api to conform. Other then that is there any hard reason as to why it's "better" to strictly follow REST or even follow it at all?

Is an api that is consistent, fast and documented well, but uses only GET requests for everything including state changes really a horrible api?
I also think it is weird that they don't start with trains.

In Denmark the Metro is operated by a computer, but the whole thing is built around this. The next step to me is not a truck, but a "normal" train that still has to interact with the rest of the train network around it. Then we can move on to trams and then trucks and buses.
I really like Spolsky's take on it:

> If it's a core business function -- do it yourself, no matter what.

http://www.joelonsoftware.com/articles/fog0000000007.html
AWS will send billing alert notifications via SNS. Theoretically, you could write a script to listen to the alert queue and shut down processing if you breach a pre-defined threshold.

Of course, you then need to make sure your billing script successfully terminates any processes that are costing money.

I'd love to see AWS implement hard cost limits for services like this. e.g. specify you want to spend a maximum of $10/day, and once you reach that limit your service is temporarily suspended.
I built a blog on wordpress which contained a story written by 6 writers. It turned out very well actually (Check the story section http://viehebdomadaires.com/blog/). I had to do this by adding a new writer as editor on the blog every week. It was more challenging but having something like this would be great.

There were some rules for the writers:

Each writer who follows the first writer, will have the opportunity to take the story forward during their week. They can work with the characters already introduced in the story and have the option of creating up to 2 new characters. These extensions to the story would have to be under a maximum of 1000 words.
> Now, when was the last time anyone who didn't work at/own a tire shop, mechanic's garage change their own tires?

Even if that's the case, your analogy is broken, because with tires you can go in just ANY tire shop and have them replaced, so it's actually a free market more or less, and that drives costs down for the consumer to the point that they don't bother doing it themselves. You don't need to go to Audi-approved Store only.

With Apple you don't have this choice. Even if you wanted to replace stuff by yourself. You are left with a useless brick once the battery dies out.
The source is obviously Robert Gates.
Press Me: The buttons that lie to you
That's great Microsoft. Debian has been doing this for over a decade now. I have Debian 'testing' installs which I've been using regularly now for over ten years and they are still up to date. Don't even reboot sometimes for a year. Nice to see the comercial guys catching up.
A) the joke was that atheists are exhibitionists, not that they are ranters. BAD joke.

B) In case the joke was meant to include ranters, the same case can be made that religious people are generally more ranting inclined. BAD joke.

C) I do not say anywhere that I (the ranter) am an atheist, which makes the whole point moot
These days I'd be far less surprised to see Microsoft and Google co-implement something with regards to new scripting language support than I would be to see Mozilla get involved.

Mozilla is basically cultish about JavaScript's place as the One True Web Language.
> JMS, JPA, Bean Validation, CDI, EL, JAX-RS, ... NOTHING of that needs wrapping by Spring to make it usable. It's perfectly fine as-is.

LOL, JMS. I take it you never actually used JMS. Where should I start? Ah yes, checked exceptions. JMS (of course) doesn't support Java 1.5, the API still uses raw types. Also JMS (of course) doesn't even support Java 1.4. You see JMS predates Throwable#getCause so JMSException#getCause is undefined and you have to use JMSException#getLinkedException. In addition the only way to wait on a Queue without blocking or polling is to use an MDB but there is no (!) standardized way to associate a RAR with an MDB. On top of that JMS is six APIs in one. There is the part old API that you're only allowed to use in Java EE, there is the part of the old API that you're only allowed to use in Java SE and then there a part of the old API that you're allowed to use in Java SE and Java EE. How do you know which methods fall into which category? Since Java EE 7 it's a comment in the Javadoc, otherwise you have to be familiar with the spec (yes, it is on a per-method basis, not an a per-interface basis). Then there is the new API (JMSContext) which follows the same "pattern" but uses runtime exceptions for certain parts until you're at the point where it uses checked exceptions again.

Yes, JMS, perfectly fine as-is and doesn't need wrapping to make it usable.

> But Spring doesn't have an open design process, where Java EE has.

I take it you're not actually a JCP member and tried to get a feature into a JSR? It you were you wouldn't make statements like this. Java EE is open only by name.
I found DO's support lacking when my VM instance was down and unable to be brought back up (it eventually came back up on its own a few hours later, without any explanation for the downtime). It's something that has kept me from recommending DO for production use to companies.
The State Department's credibility with Pakistan was dead the moment Panetta overruled (then-Ambassador Cameron) Munter and Hillary on the drone strikes (signature strikes as a name came later). You think Pasha was in DC visiting the State Department? The ISI was talking to DIA and CIA via Panetta and the American brass were dealing with the Pakistan brass.
Could each draw return a draw_hash, that is usable only once? Not only could you then have idempotent draws, you could easily embed it as hypermedia,a previous hash could be sent to a hand_history to return an array of point in time data
Skynet, the US top-secret program to track terrorists
I'm not sure this kind of yes-anding makes the speaker appear smart.

Isn't the purpose of yes-and to help ego to undercut alter's frame-setting through one-upmanhip? And isn't the purpose of the comic effect to divert the audience's attention away from alter's point, because because for some reason ego don't want that point to be discussed further?

To be sure, all of this can be effective in a jocular, conversational social setting, especially when the audience is not yet primed to detecting yes-anding, but I doubt it imparts the impression of intellectual superiority upon the listeners.
I remember where I was when bin Laden died; watching idiots prancing down D.P. and Pardall Road in Isla Vista waving American flags and honking horns, with my jaw dropped stood on the sidewalk.
Those cards look great! Much better than the OP's raster images.

But they seem familiar. I can't help but wonder, are they infringing on any copyrights?
will really love it if it is open source.
What were some of the big things he got wrong in the past? (I'm curious since he's got a good reputation among the news publications I read.)
The Mystical Properties of Programming Languages, or Why I Chose Haskell
Even in WW2, there are plenty of reasonable arguments about methods and whether they were necessary, proportionate, and effective. Look not to fighter command but bomber command: to what extent was widespread strategic bombing necessary and effective? Firebombings of Dresden and Tokyo?
The Secrets of the Chief Design Officer
Wow, well said. I also feel that many people use their diet choices as a way to excercise control in their lives.
Find a few friends who also would like to quit using filler words. Monitor each other. Have some keyword you say when somebody just said a filler word.
That of course doesn't delete it from the history :-)

You can do that via https://help.github.com/articles/remove-sensitive-data/, but once it's been cloned, the file is of course out of the toothpaste tube so to speak :-)
The Man Behind ‘Solarized’
I think it's just that the audience is full of programmers who are always curious about how stuff is implemented.

Pretty sure there have been plenty of posts saying "written in Java", though of course fashionable languages get more of this.
Of course the underlying assumption here is that putting people out of work will negatively effect the economy or the well-being of individuals, which isn't necessarily the case. This is currently how our system works (so it will in the short-term), but if we want to collectively progress as a society I think most would agree that the average individual should have vastly more amounts of leisure-time in the future than they do today. Perhaps that means not everyone needs to work.

I believe we're fast approaching the need to re-evaluate how we treat (un)employment and the role of individuals with an imposed obligation towards economic contribution, particularly due to the automation and/or efficiency we gain through technology. Will we always have enough work for everyone to sufficiently provide for themselves without "redistribution of wealth" programs? More importantly, if we force everyone to work to provide for themselves, is the work done actually creating value to society? Is it necessary?
This is one of my concerns. We have spent years becoming AWS "experts" and while I want to save money, I also feel really comfortable with Amazon and their offers. We don't use a lot of custom solutions from AWS and are not heavily invested in devops peeps, so the dev staff serve both needs.

I can't say our bill from AWS is horrible, but I have challenged our team to reduce costs to try and make our process more cost effective so I can hire 1-2 more people. DO came up as an option. Not that we are spending that much with Amazon alone but that it may be an option to help save some money. To be totally honest, AWS has been so awesome to us it is hard for me to imagine leaving them, but I can't be blind to saving some cash. Thanks for the opinion and option.
by repeatedly excusing yourself from the conversations, it's likely you let the a*holes and rude ones dominate the situation and let them exert more influence in work places or other social avenues.

I have been struggling to find out better solutions, if they are out there.
Yikes, that sounds totally unfriendly. In fairness so far you are the only one I have heard say that.
Dev laptops can be bootstrapped, build from Salt/Puppet/Ansible, and made to look extremely like a production server.

The difference in the metal is not a difference in the software (unless you happen to be doing something very specific to the hardware), and the difference in desktop environment basically does not matter.

It's very easy to have laptops that are similar to servers... stick Debian on your server, and (X)Ubuntu LTS on your laptop.
You are giving up on things because they are things you don't truly enjoy. You want to become good at something for no reason, other than to be good at it. The world is not a competion, even though some people make it look like it is. Just find something that you like doing and do it for yourself, not to be the best at it.
The traditional way of putting it is, "tell 'em what you're going to tell 'em, tell 'em, then tell 'em what you told 'em." It's an awful lot older than Powerpoint. It was probably old before Carnegie got hold of it.
Broken, Abandoned, and Forgotten Code: Prologue
Probably doesn't understand the network itself is already run by Linux machines.
Sentinel’s Mission to Find 500,000 Near-Earth Asteroids
I always fall into this.