codewright

Citus

It doesn't cost that much either. [1]

[1] Ex-CTO

Those ratios are for average salaries, not $125k salaries.

No, it's still common to have in-house "find a good node" code that fires up and takes down machines until one that will be reliable is found.

>because it is quite expensive to collect and organize

Right so why aren't you working on pivoting Referly instead?

I do enjoy hearing from members of the community but I'm reaching the point where I feel like you need to have a blogging intervention or something.

Do you need one?

Silencers aren't illegal at all.

And really the proper term is sound suppressor, they're far from silent.

Not sure why you'd think benefits are involved here. And a $125k salary does not cost $250k.

I don't think Pittsburgh has the funding to do it. You're looking at a budget of ~$450mm.

I think the funding, rather than the locale, is the blocker here.

The problem is that most local governments that want a tech hub are either focusing on tech already and will think they don't need this, or are on the other end of the spectrum and simply don't care.

The key is to find a city on the cusp of making a serious decision to pursue becoming a tech hub. Google Fiber could be an incentive, or it might make them complacent, who knows? Maybe Provo? You can't really aim too small, small towns have serious conservative budgets and for good reason.

Austin would be nice, I'm not sure how insecure they feel about their status as a tech city compared to NYC and SF. What I can tell you for sure is that they are seriously affordable. You can trivially get a house for less than $200k in a decent neighborhood. That they're already competing for the tech city thing is a bonus.

Google Fiber in Austin could end up bringing in some fresh blood, even if it doesn't make that much of a difference on its own.

Austin has a $3.1 billion budget, which makes this more feasible for them than a sub-$1bn budget city. $25mm planning and development budget.

https://assets.austintexas.gov/budget/12-13/downloads/Vol_I_...

See here to see their job development efforts.

Anything involving as much money as this does is going to have be sold as a job development play. I don't know if that argument can be made yet or not, I'd need to discuss it.

Disclaimer: I'm headed to Austin as soon as I'm freed up in my consulting work to do a startup.

I was giving advice to the general audience.

I have to admit, I find the jargon of this particular sub-culture of analyzing corporate politics somewhat annoying despite being a fan of Church.

Your job is to produce surplus value for your employer in exchange for reduced risk and possibly to specialize into work you find interesting. (Machine Learning doesn't happen without division of labor.)

You do not owe your employer your sanity or anything above and beyond what's reasonable. (As decided by your personal satisfaction and the standards/mores of your culture.)

If you're seeking to put more into the pot so you can extract more later, save money and stash it in a mutual fund or start hustling for yourself. Employers are perfectly happy to ignore you for decades on end, if they even keep you around that long.

Don't pretend value will present itself to you just because you're putting in the hours. Like thinking you'll get a date just because you're a good person.

Edit:

Don't let employers/management guilt you into working more hours than they deserve from you.

Good to know. The package management is going to be particular interest to me.

Okay? But when is somebody going to fix the documentation and keep it in sync with the language's development?

I've never once had a problem with Go's documentation and it started out as a relatively casual project that is more peripheral to Google's interests than Servo is to Mozilla's.

Making a language be able to get picked up by the wider programming community means somebody has to spend time on things other than the compiler. Lots of time.

I've spent some time in their IRC channel and tried to use the language at a few points. They're nice people but not really interested in helping anybody use the language that isn't an intern working on it. Or at least, that was the case at the time I was on Mozilla's IRC server.

The language isn't positioned for wider use the way Go was when it was first announced.

I think this speaks to conscientious language design combined with the use of LLVM as a backend.

Pretty excited about Rust, it's the best (virtually) no-compromise developing option for systems work.

Curious to see where it starts to actually bite people as popular use grows. I really wish they'd put more effort into community/outreach though.

PC users had similar games like Solar Wolf.

FUSE can be really ugly sometimes though, kernel modules are better if you need any real reliability.

So, what's their upgrade path situation? Are they going to try to hold out indefinitely on 2.3? Upgrade at the last possible moment? (Ick) Switch out of Rails when the situation becomes intolerable?

I have an emacs macro that redirects stdout and hooks in ipdb, the i here is important because it's an ipython wrapped pdb session. It's amazing.

JS is the usual Chrome debugger instrumentation.

Clojure is a mixture of REPL, println, and Ritz. Tbqh, Clojure needs an ipdb equivalent. Ritz is really ghetto. I realize the REPL suffices for most people but I'm accustomed to injecting my full programming environment dynamically into my runtime, not having two disjoint realities.

It really saves your ass when you're using underscore templates too.

Prolifically in Python, JavaScript, and Clojure (sorta. I find Ritz annoying.)

You haven't read "Lean Startup" yet you're leaning on it as a source of authority?

And you sign your comments as if we can't see your bloody username?

I have read Lean Startup and guided the development of products based on it so let me tell what (some of) Lean Startup says:

1. Make the simplest possible thing that could validate your hypothesis (a well formed one) against the market.

2. Use real data and principled hypotheses backed by data to guide product iteration once you've established a market response to one of your MVPs.

The key part being here - MAKING the thing.

What the book doesn't say is, "sell ice to eskimos, hire outsourced coders, hope for the best".

I've worked at startups dictated by salespeople or their sales process, it was a goddamn mess.

They're pretty clueless.

The rate at which I can consume material definitely varies depending on the material. I read philosophy a good 2-3x slower than literature.

It's a little bit disingenuous to suggest those speaking of speed reading are saying, "1,000 WPM ALL THE TIME ALL THE ABSORPTION IRRESPECTIVE OF MATERIAL!" - I don't think anybody is saying that.

Design reviews were big at my last company partly because the designer was DYING for feedback.

The "effective" part is a measurement of the retention. In my case, we're talking about 95-98%.

I don't understand why people are so scornful of speed reading :\

> (up to 1000 wpm with 50% reading comprehension if you believe speed reading websites)

My effective WPM (meaning take the reading comprehension as a coefficient and multiply it by the raw WPM) ranges between 800 and 950.

Why do I keep running into people doubting speed reading is a thing? I had to practice at it above and beyond a love of reading.

Do it when you can see the fuckers and run if you need to.

When I was 12 I once took out a hornet nest with a water hose by simply doing rounds of blasting them with water then running away while they tried to chase me.

I do my share of spreading the good word. :)

To be a Lisper is to know sorrow and pain.

Our best hope is a slave to an alien runtime.

Really? No appearance from Zed Shaw? This is like a perfect storm of his interests.