skysight-inc/HackerNews huggingface dataset:
> just because a bunch of other people swoop in and drive up prices around them.

Because they are now wealthier, and can convert the wealth of that house into liquid assets (through sale, remortgage, etc), or income-generating assets (by becoming landlords). That's one of the points of property taxes: to encourage people to do productive things with their asset instead of just sitting on it.

An equally anecdotal counterpoint: "Why should a real estate speculator who bought a house twenty years ago not be forced to pay increasing amounts of property tax on it as they wait for its value to go up?"
>I love [...] science

>So guess what I think about these studies.

My guess is that you think your experience alone is not statistically relevant.
That's a pretty amusing example, but I'd be surprised if prepending 'ruby' to your query wouldn't have fixed it.
Can you imagine how uneasy the people at DataSift might be this morning as Twitter buys their only competitor?

I'd imagine it will be interesting when their license renewal to the Twitter firehouse comes up next time.
From my point of view, this is due to lack of tech education. There just are not enough people graduating/learning the technical skills necessary for medium to large size software companies to employ.

I am a manager/developer/architect at a relatively large software company, and we have to task our developers with devops-type tasks constantly. Not because we want our developers spending time outside of coding, but because for lack of ability to hire the competency needed.

As you stated, good developers can generally perform these tasks so when you have nobody lower to perform them they become a weight on the developers' shoulders.

No it isn't necessarily fair, and yes, I believe in the future specialization will come back as the education system starts to realize there are many jobs in tech, not just a Comp Sci degree jobs.
Engineered by us, I meant. Bitcoin mining was exactly the example I was thinking of.
Any B2B SiteBuilder softwares?
Are there any good SiteBuilder softwares?
What I mean is not something maked for the final client (like Wix), but some software made for other web companies who want to provide a sitebuilder fr their own clients.
It doesn't matter if it's payed or open source, are there any?
Thanks to everyone in advance!
In the UK 'council tax' is paid at a level set, in bands, by the value of your house and your band is generally not reassessed unless you request it. Additionally, if you're unemployed, retired, or the house is 100% occupied by students, the amount payable is reduced (to £0 in some cases).

The charge for council tax is set at the 'band C' level, and scaled up/down for bands A-H. (A being the lowest property value.)

Additionally we have 'stamp duty', which is paid when you sell the house, as a percentage of the sale price above a threshold, and if you've lived in the property for less than three years you're also liable for capital gains tax on the sale.

This isn't an ideal system - but it does present an alternative to what's being discussed here. I imagine that a quick trip through Wikipedia would show other alternatives in use throughout Europe.
Very marketing-buzzword heavy.
So what does Ubuntu do that Debian doesn't?
Ah neat. Does it have regions?
The top tax rates also do not serve as a disincentive to all types of investment and entrepreneurship.

For instance, consider Mark Zuckerberg. By and large, Mr. Zuckerberg will owe his taxes when he decides to cash out. But why should he cash out? An entrepreneur can build a multi-billion-dollar company up from nothing, earn a comfortable salary doing it, and as long as he is reinvesting all of the business's profits and not cashing out, not pay significant taxes!
No need to hate on Oakland. Crime has gone down and gentrification has definitely occurred there as shown in the article. A 40% decrease in blacks has changed the ethnic landscape thereby changing the diversity in another bay area city.
> ...the old "waterfall" develop-test-release cycle is seen as broken.

Waterfall is not just seen as broken, it was always broken.
I'd believe the headline "The fall of COBOL programming in Banks" but this one just makes me laugh.
Zuta labs pocket printer
except that Kurzweil actually makes stuff that actually works, again and again and again
I hope I'm not actually expected to know what any of those is.
Yes. What would you like to know? The devices are cheap and durable and they work.
Having a full-stack developer as the head on a project, with specialists on the team, is a great idea.

In practice, though, it seems like the minimum bar for entry becomes "full-stack experience" and then understaffing, because why bother hiring when these people can do everything anyways?

That's how the HR and operations folks screw it up.
Uh. There was a source provided: 1911 Encyclopedia Britannica.

I wouldn't call that more reliable, but it's still as valid a source as Wikipedia.
Right; project management is really more about facilitating communication than anything else. Most projects have lots of domain experts who each have an idea of how things should be done. A good PM's job is to facilitate the conversations that need to happen to get everyone to agree on a plan, then communicate out the plan of record to everyone. This has the bonus factor of being able to peer-shame anyone who decides to deviate from the agreed-upon plan; which is helpful because in most organizations PMs have no real power to do anything.

And a management tool won't make a bad manager better, they'll manage just as badly through the tool. It can actually make things worse if you're the manager of a bunch of managers who all use the tool differently: your reports from the tool will be meaningless at best. That's why my preferred approach is to add project management to a workflow tool; not the other way around (e.g. we don't make development leads enter their tasks into MS Project, we put the project tracking info in Jira and manage it through there.) That way you can drive data consistency through process consistency and not piss off your developers by wasting time with multiple systems.
I think the main difference it that _you_ display the informations (instead of modifying a template).

I would say:
- You write your content in a WYSIWYG like editor (no need to build a new one)
- The content is structured: you explicitly define which kind of information you want (the editor will be adapted accordingly).
- It provides an API to get your informations. So you can build a website using your techno (say Ruby on Rails) which fetches the content from prismic.io.
- There are also development kits to make this part more easily.
- More technical: it's cache friendly. An URL can be cached infinitely, the content it returns will never change.

By the way you can use prismic.io to manage the content of an existing website or mobile application.
No, this article is very much in line with Toyota's roots.

Toyota's history is one of treating their workers as valuable participants who use their brains at least as much as their hands. They eschew all sorts of fancy technology, not just robots, because technology is relatively inflexible. This approach allowed them to kick the asses of the US car manufacturers in the post-WWII period, continuing to increase productivity per worker long after US manufacturers leveled out.

Their approach isn't to hire experts. It's to turn their workers into experts on their work, and on improving that work. This has been literally incomprehensible [1] to US car companies because it's of the dominant US paradigm, managerialism [2].

See, e.g., Toyota Kata for more on how Toyota approaches this.

[1] http://www.thisamericanlife.org/radio-archives/episode/403/n...

[2] http://www.amazon.com/Confronting-Managerialism-Business-Eco...
How about no months, 52 weeks per year with a 53rd 5-day week on leap years which would also correct leap seconds and such.

I have always organized myself weekly, so does everyone around me. I think it's much more natural than months, specially because you have week-ends which mark the end of each week, but not a month-end, you just drift from one month to the other, nothing happened (except bills and paychecks and whatnot, which can also be made weekly)
I agree that it's not a good comparison. Property tax is more like a cost of ongoing operation, so a better comparison would be to the cost of gas.
> That is true, but you have to remember that rates are often adjusted when property values increase. In other words, if home values double in 5 years, the city doesn't get twice the property tax revenues, as the rates are often adjusted downward to meet the desired budget.

That almost never happens. OTOH, in California, if a home doubles in value in 5 years and doesn't change ownership or have new construction, the assessed value for property tax purposes at the end of that 5 year increase would only be 1.1× the starting tax basis, since Prop 13 limits assessed value to increase at most 2% per year.
> When I talk about displays and batteries at bare minimum I want resolution and mAh.

If they had just put "570 mAh", someone would have posted "We have no clue what that translates to in terms of daily usage!"

They had reasonable numbers where it made sense.
Preparing for Computing’s Big One-Oh-Oh
Thanks for the offer, I appreciate it.
I feel privileged to be mentioned as the homeless guy who was living on a couch at the end of the article :)
You're describing a software lead, not devops.

A software lead is one a type generalist, as they have to manage resources that can X, Y and Z. The generalist position described in this article is someone who can and will dive in and do X, Y and Z themselves. Very different roles.

It's the beginning of project management steered by developers who intimately understand all of the work involved, even if they aren't as competent as the specialists.

People with a wide breadth of general development knowledge, once employed as developers but now managing development? I wouldn't exactly call that a new idea. Or are you talking management that also develops across all components of the software? If management takes up so little time of a single developer's time, then you're just using different words to describe the small team constraints that the article does.
In the original experiment -- see http://www.ncbi.nlm.nih.gov/pubmed/20424094 for the abstract -- the toddlers stood on one side of a slanted table, so that anything placed on the table would roll down to the other side, where the adult actresses were. Presumably, the toddlers were not able to walk around the table.

One way to replicate this at home, albeit imperfectly, is to place your toddler in a high chair, so that if you drop the toy on the floor, she is unable to reach it.
This article is pretty ignorant.

I don't think most developers have the capability to be sysadmins or QA. Vice versa, too, quite often. Joe developer ain't that special.

Devops is about taking moving the infrastructure into its own configuration-managed artifact, taking lessons from programming and computer science, and coming out with its own engineering rigor.

If you want your devs to operate builds/infrastructure/etc/etc, that's fine, but devops that ain't. That's called "many hats".
Everytime someone writes a tool to show what is possible in public, there's some jerk giving them a hard time about it. Don't be that jerk. The function of the security community is to help people realize when they're not safe. No one likes having their bubble burst, but it's important that it get burst or people don't fix the problems. We've seen this over, and over, and over. Find a good way to improve security that is nicer for everyone involved and actually works and a lot of people in the community will listen and will legitimately care, promise.
Demo videos are for extensions, I have no way without logging in to see what the tool does.
The Caltrain stops at midnight though. Make sure you don't have too much fun and stay out late or else you'll miss your transportation back. Driving is too unsafe and gets tiring as well due to distance and parking. Somehow, the majority of residents in the bay area are okay with this the status quo.
The latter. The NSA didn't have to analyze anything: Snowden was not a known target, and he revealed himself before any real manhunt or mass-analysis had started.
Movistar bug lets anybody check who you called
I don't think this is the best analogy. Understanding a "full stack" isn't so you can manage specialists, it's necessary to _be_ a specialist so you can build something that you know doesn't have an obviously inherent pitfall. It's so you can prototype something without needing the time and attention of another specialist.
And yet will be be open source ?

Probably NOT

Will it have the community and driver support of other DB systems?

Probably NOT
I'll admit my anecdote is an outlier, but I have seen a few examples of it.

Take a look at local city budgets. When housing prices doubled, the cities tax revenues didn't. They certainly went up overall (I mean, when has a gov't ever not expanded?), but my argument is that often 2house price =/= 2property taxes.
this is pretty much spot on. when you have strict separation of dev & "ops", you get what I would argue is bad service+stack design and wasted resources.

"devops" is having developers sitting with, understanding, architecting, and in the end programming solutions to what were traditionally ops/sysadmin problems. and operators sitting with, understanding and participating in service architecture, teaching about livesite realities, coding where possible, and appropriately buffering devs from noise on the livesite.

the unfortunate thing is that many companies swing the pendulum too far one way or the other. neither all devs nor traditional dev + IT/ops orgs are the best way to build a great product and run a world class service.
My experience is definitely anecdotal. I probably misspoke, my problem is with the reporting of the studies, not the science itself.
On visiting HN and other sites - it's easy to break the habit with LeechBlock for firefox, or similar for whichever browser you use.
Show me a developer who can do anything in Operations and I'll show you someone who gets the DevOps philosophy.
Interesting. What about February and leap years?

Does khom and yon have meanings?

The rest of the month's name is based on what?
Great video! Easy to understand how Bitcoin works.
We use virtual servers and all of them run different releases of ubuntu and for the life of me I don't understand why they're not running debian. You never start an X session on a server and what admin would want to use Unity anyway so what's the point in using Ubuntu rather than stable debian?
My average "devops" engineer is paid the same as the senior-level engineers within my company.
Steve Young on Building (and Balancing) Multiple Revenue Streams
Google Flow Skeleton on GAE
Same, I always want to see a demo or example before signing up.
From http://www.caltax.org/member/digest/may98/may98-4.htm

Almost immediately after passage, the California Supreme Court sustained Proposition 13's constitutionality in the Amador case (Amador Valley Joint Union High School District v. State Board of Equalization. September 22, 1978). After a series of legal challenges in the 1980s, the issue of acquisition-value assessments reached the U.S. Supreme Court in Nordlinger v. Hahn. In a stunning 8-1 decision, the court in 1992 upheld California's acquisition-value system.

The court ruled that an acquisition-value system does not violate the Equal Protection Clause of the U.S. Constitution because it rationally furthers a legitimate state interest. The court said, "The state legitimately can conclude that a new owner, at the point of purchasing his property, does not have the same reliance interest warranting protection against higher taxes as does an existing owner who is already saddled with his purchase and does not have the option of deciding not to buy his home if taxes become prohibitively high."

The court also opined that a state has a rational interest in neighborhood preservation, continuity and stability, and that Proposition 13's system of "locking in" lower tax assessments contributed to such preservation.
It's more like wanting to be a painter without knowing how paint brushes are created. Ideally I don't need to know how a system is configured (to an extent, of course), I just write the code.
That's Mountain View and just the most desirable part of it. I live in the same city with rent below $1400 for a 1 bed/1 bath and just a 5 min drive from the same Caltrain station.
RedHat has carved out a huge chunk of the in between space. RedHat sells to people who buy support contracts. Some guy running a personal email server doesn't have the money and the likes of Netflix doesn't need it because they have the expertise in-house. You see a lot of RedHat in corporate IT departments.
...right up to about 20 kHz, whereafter YOU CAN'T HEAR THEM. Hence 44 kHz sampling.

Seriously, A/B test this, you might be surprised.

Also if you think that's anything like a square wave coming out of a guitar speaker (or that that is even desirable in the most case), I've got a bridge to sell you. And yes, I do play.
I understand the need for translating it into something the average consumer could parse, but that doesn't belong under the heading "tech specs". This is a prototype device being marketed to the earliest of early adopters, and actual technical specifications are important to that crowd.
The Intel chip I was looking at while getting the numbers was J1800 with TDP of 10 watts. Wiki quotes 3.5 watts for RPi(model B). Assuming my estimate of 10x performance for Intel holds, the perf/watt situation looks pretty equal.
There is no content here. Why are people explaining themselves and upvoting this nonsense?
You can't really draw a hard line between administration and development, in the end you are just building a system and the more you know about it from all angles the better design decisions you can make and the easier it is to fix issues.

I diagnosed a few problems over the years that arose as apparent issues with a web application but that I gradually narrowed down to things like network issues, or kernel bugs, or system misconfiguration, or database issues etc. Modern stacks are very complicated and the interactions can get really messy, it is close impossible for someone who doesn't understand the whole thing to find issues that aren't neatly isolated. I perfectly know that I do not have the full qualifications of a sys-admin proper, and would not like to do a sys-admin job full time, but in those particular cases a pure sys-admin would not (and often actually could not) find those issues. As an example, I can remember many situations where the application showed different behaviour depending on which application server you hit, and typically both "pure" developers and "pure" sys-admins were having a hard time finding the issue.

Good sys-admins anyway have to learn, at least, C programming, shell scripting, and network protocols and programming, so it's should not be a big deal to add some Rails/Django/Node to their skillset. Good developers anyway have to know things about hardware, networks, protocols and so forth. You do want to have people that are specialized in one or the other area and focus on it on a day to day basis, but you also do want to have people that can understand a particular aspect of the system top to bottom when such a need occurs, and it does happen quite often.
And yet the residents of Istanbul (and New York, London, Tokyo, Paris...) don't go around thumping their chests with superfluous capitalization of the word "city".
The author is missing the fact that good developers can actually automate away a lot of those "lower on the totem pole" roles, or at least reduce the amount of repetitive stuff down to the point where the remaining work is quite abstract and basically just more programming.

This isn't counter to specialization -- in a big organization, people are certainly still going to specialize. But the "DBA" equivalent people are just programmers who have fresh expertise on the storage layer, and the "QA" people are just programmers who have expertise on the automated build and test systems.

The dentist analogy doesn't hold in software. A dentist handling secretarial work is just an expensive waste of time, due to comparative advantage. But a programmer replacing secretarial work with automation often reaps big long-term dividends.
Pure developers are a problem because they will the information do their job well.

I go back a few years, to an old, waterfall-like job. I was handed work by an analyst, that was handed a task to analyze by an engagement lead, who might at some point talk to someone using the application. The work was always handed out on time, but the product often failed, not because it was buggy, but because nobody actually had much of an idea of what we were really trying to solve.

So us developers got much work done, but the work didn't actually solve real problems: The force is applied to the wrong vector. Then the product fails, and the blame game begins: Changes are too expensive, because the developers didn't know what the real invariants are. Queries are slow, because the database architect wasn't told about the questions that the database had to answer. The business analysis just wrote documents. It was all a big catastrophe.

That company moved to Scrum, the terrible way: Here, have this self organizing team full of specialists that don't know anything outside of their domain. They are still failing to this day, but now they blame each other in retrospectives.

So I'd much rather be stuck coding less, but then being aware that my code is actually solving a problem for someone, than just writing castles in the sky, because everything I've been told about what my userbase needs comes from a game of telephone.
This is a more sensible expression of the concern. Your initial post was easily confused with a common ill-advised perspective.

I might not be able to do much with "jwr", but I could build an entire profitable identity around your SSN.

Your real concern is that identifiers and authentication must be separate and treated as such, while in practice one number/string is used for both purposes - hence the concern of "stealing numbers", as having the identifier means having the authentication. Insofar as there may be a separate authenticating token, all too often it is so weak that the identifier is used as part of the authentication; having the identifier may be enough for access, or enough that deducing the remaining authentication token may be fairly trivial (say, a 4-digit PIN); this being tax day in the USA, we're quite aware that many tax returns will be fraudulent, requesting large refunds based on mere possession of a SSN identifier and a smattering of other public data. We should be using real cryptographic private keys of substantial length for authentication, leaving the public identifier public so that having one (or a slew) gets one nowhere without the hard-to-obtain authentication tokens.

As for the downvotes and the need to craft comments carefully: yes, the need for careful wording is the norm. We're trying to cram a lot of information and opinion into a very small space, which will be read very quickly by a great many people of wildly varying perspectives interpreting the post, making it very easy to misinterpret intent (doesn't help that there are a lot of dumb & ill-advised posts, setting expectations quite low). The greatest problem is refining short easily-read posts to withstand accusations which demand encyclopedic thoroughness. One of my motivations for prolific posting around the 'net is precisely to exercise & refine my ability to post views in a concise & persuasive manner (and if that gets bizarrely construed as "he must have multiple accounts, know a lot of people, and persuades others to downvote opposing views" then I must be getting somewhere with that ability).
The cluster control is pretty cool. Reminds me of spinning up dynos on Heroku but without the extra cost.