skysight-inc/HackerNews huggingface dataset:
Face time - Some people thrive in a social environment. The same nut watching you work will find another way to track and impede you virtually.

Technically/Socially - An issue for all offices. I don't see my TFS to git migration going as well virtually. In person groups worked well. It's works well for a lot of things and often.

Productivity - Chat/SCM/etc are the hub regardless of physical location. In person we have access to white boards and pairing stations.

Commute - Every cyclist and public transit commuter gets a workout and decompression time. I still set my own hours with a core hour preference and accepting meetings that fit in my schedule.

Don't assume it's a technical and social issue. There's a spectrum of personalities and needs. I tried working from home with all the tools and a competent team socially. It was one of the worst positions in my life and had nothing to do with the work. I prefer my home away from home.
Did you even try googling? https://www.fcc.gov/consumers/guides/human-exposure-radio-fr... https://www.fcc.gov/engineering-technology/electromagnetic-c...
Why should this discussion be limited to out and out software companies. Think NASA. Think New Horizons. Think about the nuclear reactors and what would happen to them when a sensor gives a wrong reading for reaching critical level. These are some pretty serious use-cases where Software Engineering processes are highly developed and rigourous.

The computing systems used in a car itself (what do you think triggers the airbag on an accident?) can be trusted because of maturity in Software Engineering.

Startups don't choose to follow these methods to keep costs low and stay lean. I say that in the broadest sense, because a banking startup will be different from your average SaaS startup.
Thanks. It's been rocky at times, jealousy does get in the way from time to time. But it's been an amazing learning experience getting to know her and build a friendship with her. Both of us are only going to evolve and grow over time, both together and apart. I wouldn't trade that for anything.
If I were doing it that way, I wouldn't give the outer blocks' curly braces their own lines. For example in C#, where pretty much every file has a single "namespace" block containing a single "class" block, I write it as:

namespace SomeNamespace {
class SomeClass
{
//...
}}

Which avoids having shifted the whole file an extra indent level to the right. But I haven't seen anyone else doing this.
The urge to violence is built into our DNA. Not everyone expresses it fully, but it will always be a part of our culture. Anything that redirects that urge in pro-social ways is a good thing, in my opinion.
CITY+ESCORT+TOURS+STASY+-+Athens+Escorts+Babes
There is no effing way this is true. Everyone I know under 40 checks the RT score of a movie and factors that into their decision to see it.
Maybe it does work, and they were just able to get away with it until adblockers (and earlier, popup blockers) started to reach a critical mass.
Former professional snowboarder to stealth CTO: Nicholas Bellinger talks DevOps
This article has a hint of "C-style memory management is good for you"—implying that you might want to write in something like JS and then go back and write in C++ in order to "tighten the screws". I think that's wrong—by and large, it's been a very good thing that people have stopped caring about memory management in production. That's because correct C-style memory management never† scales up to large software projects in a way that doesn't result in crashes and, worse, vulnerabilities.

So, yes, we've traded performance for automatic memory management. But we've gained reliability, safety, and security. For the vast majority of server-side apps, that's a worthwhile trade.

† Unless you use the processes like NASA and the like use, which for most apps are infeasible from a cost point of view.
We got frustrated with the UI on Loggly and wound up moving to Logentries (https://logentries.com/).

I've not used Papertrail, so can't compare to them, but it's significantly easier to use than Loggly, they've been kind to us through the odd overage, and it does what we need it to do (Centralise a load of application logs and allow us to search over them and set alerts). The live tail feature is nice as well.
Some other missing compilers:

* Idris : http://www.idris-lang.org/

* Ivory : http://ivorylang.org/

* ATS : http://www.ats-lang.org/

* Mbeddr : http://mbeddr.com/
I don't have the data, but that's intuitively correct. Time does matter some when it comes to the corrosion of the underframe (in states that salt roads), dried gaskets, weather damage to paint. But miles matter for everything else including body damage from accidents.
> Everything seems unnecessarily complex.

This impulse to find a simpler land of software is what I relate to in the Suckless stuff, and Terry Davis' TempleOS.

What these have in common is a large degree of separation from "the industry." There is no commercial reward in following this impulse. But I think it marks a certain level of maturity as a person who is passionately into computers and software and thinks about them a lot.

Computers aren't the problem. Software isn't the problem. The culture of people who write software is only part of the problem. The problem is "the industry."

If you really can't stand the unnecessary bullshit anymore and aren't going to become a hermit on a mountain you probably should at least find other hobbies, if not change careers.
You didn't ask if it would work in a big box retail chain though. You asked if it would work via the Internet!
Sure, if I felt no benefits I wouldn't even talk about it. I'm the opposite, without these drinks, mundane discussions, which means relating to the people talking, not having an intellectual challenge, is borderline impossible.

I too feel no negative effects the morning after. I wake up earlier and eager for the day. Still surprises me ..
If one is choosing C++ then performance is probably a part of the requirements equation.

These books discuss performant (and sometimes complex) C++ code - in the domain of computer graphics.

http://www.amazon.com/Physically-Based-Rendering-Second-Edit...

http://www.amazon.com/Real-Time-Collision-Detection-Interact...

About how to use the new threading standard:
https://www.manning.com/books/c-plus-plus-concurrency-in-act...
Whenever a cashier asks me 'How are you', I reply 'Oh you know, it's my DayOfWeek'.

Most people that never spent time in retail are confused by this. 'It's Wednesday for everyone, what do you mean by it is your Wednesday?'

If you spend time working a 35 hr/week job (just little enough to not qualify for benefits) you know that your weeks and weekends can be totally different from the rest of the world's, your family's, and your co-worker's weekly plan. Oh, and that changes from week to week too.

Coordination of weeks and the days of therein has to start from a labor perspective. If you want to buy groceries or shoes from a store, it has to have a cashier, and that cashier's family and friends have to understand that the cashier's life is scheduled differently while in that job.
But the guides aren't just how you build a package. They're how you package something for official distribution. The requirements for the former aren't nearly as stringent as for the latter, and by obscuring the former behind the latter, Debian makes its packaging guides less useful.
This doesn't take into account the following transactions:

- The time and money it takes to find said $30-50k engineer

- The risk (and therefore potential cost) if the engineer doesn't do the job correctly

- The unknown cost of "occasionally fixing" could be $50 or $50,000. Given how nebolus the DevOps position is, you also can't be sure the stuff this individual is doing is considered best practice.

- There is overhead time spent on managing such a resource (teleconferencing, IM's, etc)

- There is potential that the resource is unavailable and therefore a potential downtime that could cause your business loss

There's a reason Heroku exists and has been successful, and these are just a few of them.
Since it is a web server we are talking about here, let's assume it is the backend space :)

I guess the answer is obvious: it is nice, but might not worth the effort. 1.2 million requests/s is pretty good, but in reality, you probably would still need 2-3 other hosts as a failsafe backups, let alone there are other factors, like memory constraint, in which case, less optimized solution might be just acceptable because it is sufficient. So under common usage cases, the need for scalability outweighs the urge to squash the maximum performance from a single machine.
If there is going to be violence at least moving from kill-at-a-distance weapons to fists is a step in the right direction.

Kill-at-a-distance weapons are often considered to be an equalizer, since it is possible for people with wildly different body types to weild a gun with similar stopping power effectively. Using fists is the bare definition of "might makes right", which isn't desirable either.

The value in fist fighting is that there isn't a proxy for the damage done, you are literally hurting someone with your own hands, which is arguably less humane because it can take longer and perhaps more brutal. Compared to long distance weapons, a gun is impersonal. A nuclear weapon even more so.
Malware-containing apps have millions of downloads, and there are/were thousands of them. One might argue if that is an "infestation", given the much larger number of apps in the store, but it also isn't something that has only happened once or twice.

And when it comes to e.g. games there isn't much of reputation information outside a very small set of hits. No need to download "smut".
There is also https://sendy.co/ which uses Amazon SES. It's a lot cheaper than mailchimp.
My worst experience with Amazon yet is they've locked the Amazon video Android app from every Android TV device except a few select smart TV vendors and their own Fire TV devices. The result is I can't watch content I paid them for (and would continue paying for) on a device I bought through Amazon (Shield TV). They're treating lackluster Fire devices, which were supposed to be loss leaders to get you into their ecosystem, into privileged, Apple-tier garden walls. Since they lack the Apple polish and simplicity, the result is making customers like me, who are already in the garden, want to leave.

Between this, inscrutable device compatibility of Kindle content, and 2-day delivery becoming unreliable, I'm cancelling Prime after a decade because the value is gone.

BTW, Netflix lacks voice search in all of its apps. Normal Android TV is at least reasonable enough to just bring up the Netflix text search if you try to voice search, rather than kicking you out.
Free will is basically the feeling of experiencing a mind that operates in a certain way. Just because you don't know what the requirements are doesn't mean it doesn't exist. You could just as well say "love doesn't exist" because physicists don't have a great model of what causes it.

Sure free will exists; it just isn't a objective natural phenomena to be studied under the domain of physics. It's an emotion. It's what happens when you brain builds counterfactual models of its own behavior. It's really no different from things like pride and regret -- you experience them only because you can imagine a reality different from the one you are in. There needn't be any physical mechanism for predicting the construction of those realities.
In Praise of Idleness, by Bertrand Russell
What's inefficient is devoting large swatches of useful real estate to parking lots, when the same number of cars could be accommodated in much less space.
A lot. It's the largest pain point shipping on iOS. More specific details and some suggestions:

http://christian.legnitto.com/blog/2016/01/02/ways-i-would-f...
Apple has tools to see whether your app is loading external content and modifying itself, though. I think you can deceive them by making it seem as though it does so in an allowed manner (e.g. no code execution) during review, but they'll definitely know that your app has the theoretical capability.
While true, it also highly dismissive of structural problems which you have noted. The subtext with this line, whenever I hear it, is essentially "this city is for rich people only."

The "needless to say" bit was on the presumption that SF should not try to imitate Dubai.
This exists already in a pretty intelligent way, check out http://www.caloriecount.com/cc/recipe_analysis.php and paste in an ingredients list.
Everything you need to know about Vim
I suppose I'll just stick to the plan of living out of a van then...
I used to agree with you, while still running an openbsd router for home use, but the last upgrade went quite smoothly so I would say they've put a lot of work into that aspect.

Yes there were manual steps to perform but they worked so well and were so simple that I couldn't help but think about automating them in a simple script. And finishing up I just did a pkg_add -u to upgrade all packages.

The only thing missing from the example imo is dnsmasq, much easier and lighter to use.
Exactly. I can understand uninformed consumers accepting this kind of bullshit because they don't realize it could be so much better. But it boggles my mind that people who have used a real package manager will put up with the exploitative, arbitrary, restrictive app store nonsense and put down real money for copies of software.

So much work in the phone ecosystem goes into trying to tame the beast of closed-source, untrusted, adversarial code trying to show ads, track the user, sell them in-app purchases, and so on. These are all unnecessary complications that a fully open-source phone ecosystem (with no app store, but a real open software ecosystem like Linux) would solve.
Are people supposed write an extensive in-depth review for everything they rate? Surely you wouldn't want the plebs buying games to put you out of a job.

If someone's honest opinion is "disappointed, not worth $18" then who are you to say that they shouldn't leave that comment and rating? If you don't like the text perhaps you should ask Steam to allow rating without a comment. I think you would still complain that a bad rating might cause bad sales. Does it ever occur to you that the game is just bad?

You aren't going to get me to spend more money by trying to make me think of the team that made it. You claim that isn't your intent but I think it clearly is. You are advocating in favour of changes to get more sales.

I'll wait years and pick the gems from among the rubbish for a pittance.
I am not a lawyer and I am not an accountant. But really the answer is more difficult than a multiple choice question. The real answer comes down to the terms of each investment and how that specific investment is laid out. It all comes down to how liquidation is spelled out in the terms of each specific investment and the investments as a cumulative.
On this topic, I always like to point to this illustration from The New York Times:

http://graphics8.nytimes.com/images/2005/06/15/business/arm3...

Notice the date: 2005. That was around the time I started asking around, "How can I short the housing market?"

I felt relieved reading The Big Short because it revealed that there wasn't any way to do so at the time, especially for a little schmuck like me. And even the guy who eventually figured out how to do it, Michael Burry, ended up fantastically wealthy and, according to Michael Lewis, deeply embittered.

On this article, I agree that trying to treat the Housing Bubble and Financial Crisis as independent events seems disingenuous. (Are there really serious people trying to do this?)

Nevertheless, I question this claim:

We are supposed to feel good about this because it saved us from a Second Great Depression. But there was nothing about the collapse of these banks which would have condemned us to a decade of double-digit unemployment.

I abhor Wall St. and the industrial-finance complex it has created almost as much as any Teapartier or Wall-Street-Occupier. But I don't understand the scenario where those firms collapse and civilization as I know isn't put in, if not serious peril, then unnecessary peril.
See what did this girl in the shower. This is amazing  CLICK THE LINK TO S
Ahh I see, you hate regulation, taxes, and don't think a city the size of Dallas really needs mass transit in practice. So this isn't really about San Francisco at all. The only thing that really surprises me now is that you speak highly of New York.

I could describe how much more "social dysfunction" there is in Texas than California at length but I sense its going to be an uphill battle. Suffice it to say that my friends just got back from Austin where they witnessed a "mock shooting" at the university in support of the new open carry gun laws. When your legislators spend time expanding gun rights after repeated mass shootings, you're looking at social dysfunction. These same legislators also found the time to carefully craft anti-abortion legislation recently in an attempt to force all abortion clinics to close until the Supreme Court can overturn the decision. Meanwhile they don't seem to mind all the fake clinics being set up which use tax money and tax benefits to confuse and lie to desperate women who are under extreme stress already. You can have your 0% income tax rate "paradise" and try to remember that Texas has among the highest property tax rates in the country to make up for it.
> desktop applications are still 99% C/C++

In the Windows world especially that's not even slightly true.
Dividing your architecture into separate components will probably cause you more downtime and have much worse performance.

Less servers and components mean less things to break.

Grab a dedicated server and host your shit on it (have a DB replica because losing data sucks, but that is easy). You will be able to run like that for much longer than you probably suspect and the chance of downtime will be massively reduced.

Why? Because a single server has a very low chance of having anything going wrong.

Not only that, but there is a lot of overhead in performance when you split everything up into components. You will be surprised how many requests you can handle on a single inexpensive dedicated server when you haven't put too much effort into "architecture".

When you actually find yourself running out of headroom on that setup you will know much more about your application and it's requirements then you did at the start, so you will have a better idea of what to split out, and a better understanding of what parts of your app need more performance anyway.
There's a huge difference. An URL is an absolute black box, a binary that you have to give Apple for certification on each change and that has to call Apple APIs to do anything useful (like network) is not.

Apple will scan your App to check for basic violations, that's all automated. For instance is there a specific flag that you can initialize a socket with to listen in background. This is only allowed if your app is supposed to stream music in background or do some VoIP thing. So if you're app is not that and the software detects you have that flag set anywhere in the code no way you will get it through the certification. There's simply no possibility for such analysis with a URL.
"San Francisco is a baby town, a joke, compared to what's going on in Manhattan."

I don't particularly have a soft spot for either city, but I agree with you on the note of maturity. Manhattan has a far better idea of what it's doing compared to SF.
Needing to think memory management turned out be a bit un-expected you might say. There were a few things that went well and few that were a bit unexpected.

Things that went well:

1) RAM got ridiculously cheap: 2x 8GB is now what $60-70? So it would seem, in that regard, yeah you shouldn't care about memory.

2) GC languages and runtimes. Believe or not there was heavy skepticism that GC runtime could be ever be a serious strategy in practice. It was an exotic technology that many thought would left for academia and fringe research area. But most popular frameworks and languages today are GC based.

Some things were a bit un-expected:

1) Memory access speed is fast but it didn't keep up with CPU speed. A cache miss will costs hundreds of nanoseconds. CPU speeds may have been doubling every 2 years or so, but memory access speeds have only been increasing by 10-20% or so.

In the 80s and 90s you just didn't care as much about cache hits and misses. But those are the forefront of performance optimization strategies. "Align your struct members","use structs of arrays instead of arrays of structs","think about cache lines and strides when you loop through your data arrays..." etc.

And because CPU speeds go so much faster, memory access also stands out on performance charts. So GC languages and runtimes can still seems slow and sluggish for applications that don't pay attention to memory.

2) Applications got more concurrent and servers are expected to handle a larger number of clients / connections / requests. That means each one needs a context, so it needs memory. So memory is again at the forefront. Accessing it and its latency, GC pause times are important.

3) Mobile happened. Mobile devices have proliferated so the needs for fast, small footprint applications never went away. Even as there are serves witih terabytes of RAM around, there are even more little arm cores and then everyone talks about IoT. That means langauges/runtimes which compile ahead of time will never be 100% displaced. Heck even on Android, ART (AoT copiling) is replacing JIT.
You'd be surprised how easy it is to get a gun in an urban center. In certain neighborhoods you can even rent them for a night.
I also run into this problem all the time. I hope that with the networking TS standardizing on basically boost Asio and the incorporation of coroutines into C++ we should start seeing some unification across all network/do client libraries in terms on non-blocking use.
I had a Gigabyte board (GA-Z170N-Gaming 5) that was very unstable with Skylake. The newly released beta BIOS update resolved the issue. Not sure that it's related to this issue directly but it did involve random freezes.
As our world intersect with more and more lives on the lines like with self-driving cars, we need to understand how these things interact in terms of development cycles and process.

We (as software developers) don't need to adopt their models and processes, but we need to figure out how to work with them to ensure higher reliability across the board.

The alternative will be formal certifications/licensing pushed on us by legislators who don't know how to send an email and think mathematics is a weapon to be regulated.
Your stock price is typically inversely proportional to how well you treat your employees (except Google).
await is coming, maybe even in C++ 17. Visual Studio already implements it. Way more efficient than the C# implementation too (coroutines)

Promises are already there.
Yeah, I compared his paid to other paid. afaik not all companies are OK to use free SSL since it seems it is still a novelty.
This is what happens if the compiler glitches or the os fails; people dig in to find out why. Normal code is much more like doing a service - if the breaks don't fit it's because the person fitting them has screwed up, and you take them off and fit them (or a new set) back on again. Maybe there is an inquest in the team about using spanners properly, maybe the old fella in the shop tries to communicate some wisdom about checking things first.

At the end of the day it's about money and risk.

But, the interesting difference between software and mech eng isn't the attitude to faults, it's the fact that software isn't designed to work within tolerances. We don't build software around dimensions or stresses, we expect it to work always like maths, but it isn't, quite.