mkching

I prefer the subscription model, as long as the total expected cost is not too far out of line for the service. $5/mo for every tiny utility is too much.

However, before the rise of subscriptions developers still needed income. What often happened were releases with big changes (sometimes completely changing the ui) for the sake of justifying an upgrade cost. Even worse, incompatibility between versions to force an upgrade.

Perpetual license of an older version included with the subscription does seem like a good middle ground here.

I live in an area where cable/fiber is not an option, and have been using T-Mobile Home Internet for a while now.

People in other locations will surely have different experiences, but for me it just works okay and the signal is poor. In rainy weather, it degrades even worse. Even with a Cel-Fi booster and directional antenna, the signal is worse than AT&T without any booster. While I sometimes get 50 Mbps down, usually going over 20 Mbps gets a bunch of latency and packet loss.

For backup, I have an AT&T hotspot, which performs much better but is limited to 100GB. I get 120 Mbps down on this with no degradation.

I live in a semi-rural area and work from home in tech. I am within range of LTE towers, but only T-Mo will serve my area and the connection remains spotty even with a $1000 signal booster.

It is frustrating to see initiatives like this that do not address the actual problems that make work difficult. My throughput is about 25 down / 3 up when it works, and this feels fine to me.

What I do need is a ping that stays under 100ms reliably, even when downloading or streaming. I can usually get 60ms or so, but it jumps up to 1000ms for short periods of time regularly for no reason. This interferes with any sort of voip calling severely.

Just as importantly, data caps should be at least 500GB, and clearly unlimited would be better yet. Plans that offer under 100GB of data are used up very quickly if doing anything more than the bare minimum.

I live in a semi-rural area and with no cable/fiber/dsl options available.

In my experience, most home internet offerings from the big mobile carriers will throttle you fairly quickly if your usage goes to a few hundred GB (easy to do with streaming, os updates, etc). They may not have a limit, but once you're throttled it is basically unusable.

Same here, we just deployed a test instance running the upgraded code. No issues in our existing dashboards so far, and our initial testers are liking the speed improvements a lot.

These sort of rates were real in the past, but regulatory changes have decreased them dramatically. In general, much less than $0.01/mi at wholesale rates.

One common exploit if only one user account is hacked is to set up a forward to a specific high cost number that receives a lot of traffic. There are carriers who aggregate these routes and even blend them in with legitimate routes and then resell them to other carriers at a low cost.

Make sure you understand the basics of the new domain extremely well. You don't need to know everything in depth, but every piece you do know needs to fit together in your mind.

Ask questions until you think you understand, then have someone confirm your understanding. Those with experience in the domain will be able to recognize the right questions being asked.

In my experience, most seniors in a company are willing to help you get up to speed if they see that you're actually trying to understand the domain as opposed to just learning enough to get by.

Even though it seems like everyone else has a good understanding of things, this is usually not the case. Often people have bits and pieces of domain knowledge, but not a thorough understanding. These are not the ones who can really help you.

Find someone who has a good understanding that you seem to get along with. Be proactive and ask them if you could pick their brain over a long off-site lunch and then ask a lot of questions.

I could very well be wrong, but it is not my impression that Vietnamese are very prevalent in tech.

Short codes are managed per country, but within the US just about every true mobile operator should have the ability to work with the same US short code. If they don't support a given code, it is because they choose not to. Part of the approval process for getting a short code is having all of the major wireless carriers sign off on your application.

If Google Fi is using SMS-enabled wireline numbers as opposed to mobile numbers then there could be additional complications.

In general, it's a bad idea to wear gloves when working with spinning tools. If the glove snags the wrong way, it can pull your whole hand into the tool.

Today after fighting with Kibana all morning, I decided to tweak our scripts to build Grafana dashboards against our existing ElasticSearch data store. Very fast to get up and running and the the features and speed are amazing.

Very glad I saw this announcement on HN.

The second half of this is particularly important.

Apple keeps iOS desirable to an enormous number of end users who are willing to spend money on apps.

They benefit from this by selling a lot of iPhones, but the developers benefit as well by having a market to target.

Sichuanese Cuisine is very good.

La Bu La in Bellevue is also good.

Dough Zone is worth trying if you like DTF, but not as good imo.

There are certain things such as race and gender which are protected classes. It is illegal to discriminate against someone based on these attributes in various ways including employment. [1]

Beyond this, most employment in the US is "at-will", meaning that you can be fired for any reason or no reason. [2]

Some things not explicitly listed as a protected class might still pose problems if its determined that the way in which is it enforced is discriminatory. [3]

[1] https://en.wikipedia.org/wiki/Protected_class [2] https://en.wikipedia.org/wiki/At-will_employment [3] http://navbat.com/can-you-fire-someone-for-being-too-ugly/

A storage server and network to put those drives into which would give similar functionality to EBS would have significant costs and require some degree of management.

I use Slack in my own company, but often use Skype with companies that I do contract work for.

Searching your conversation history in Skype is terrible. Slack really does this well.

I think you may want to consider focusing more on concrete goals, and what funding will provide to backers.

For example, see https://www.kickstarter.com/projects/tomchristie/django-rest... which is widely used Python library. In that campaign, it is easy to see how much time the author would be able to continue to commit to the project at various funding levels, and specific features they will implement.

Even if the commitment at a certain level is just being able to provide on-going bug fixes, this shows the value to the company rather than backing being presented as a thank-you for previous work.

It was the same with my family when growing up in Hawaii.

Based on the responses in this thread, it seems to be more prevalent in areas with Cantonese populations.

If you're looking to make espresso drinks, going too cheap will be an exercise in frustration. Cheaper machines have limitations you need to work around and make it harder to get consistent results. Most people just getting started will simply give up. If your budget is less than $500, get a Nespresso. It makes a better drink than the other pod systems and beats most non-specialty shops (it can't touch a good shop or something you can make with a good machine and practice).

If you want to go further than this, the following combinations provide a very good value:

Gaggia Classic + Breville Smart Grinder Pro (~$500 total)

The Gaggia Classic is considered entry level to make good espresso by many people. I started with this and it can make a good drink, but you cannot make back to back drinks and foaming milk well is more difficult than on pricier machines.

Breville Dual Boiler + Barazta Vario (~$2000 total)

After using the above setup for a while, I upgraded to this combination. It is considered one of the best values if this is your price range. Frothing milk well is much easier than on the Gaggia Classic, and its larger boiler and electronic controller provide better temperature stability.

If you want something halfway between a semi-automatic and a fully automatic, the Breville Oracle has received very positive reviews in the coffee community, even by people who came in wanting to hate the level of automation it can bring.

Don't skimp on the grinder, get very fresh beans from a specialty roaster, and then plan a week or two learning curve. If you're interested, http://www.home-barista.com/forums/ has a lot of information.

I'm curious which products you would recommend for bug tracking. If they have testcase management, even better.

I run a managed hosting company that hosts a fair number of Atlassian instances. We have our complaints about Atlassian and our customers often experience sticker shock when upgrading past the 10-user licenses, but we've had trouble finding other issue trackers with similar functionality, flexibility and market acceptance.

The same goes for Confluence as a wiki. While not perfect, most other products seem unable to do things such as access controls easily.

If there are other mature products out there that people are using we'd love to take a look. We do support Bugzilla and MediaWiki as well, but this is usually a different market segment from what Atlassian serves.

For people whose main complaint is watery coffee, but are not opposed to pod systems in general, try Nespresso. I find them a lot better than the coffee I have had from Keurig and Starbucks machines.

The coffee is pretty good -- better than most coffee shops, but not as good as a great one. Apparently they are actually used by a lot of restaurants when you order a coffee.

The original quote was "but that does _not_ mean I think its fine to watch porn" (emphasis added).

Perl has a CSV driver for DBI: http://search.cpan.org/~hmbrand/DBD-CSV-0.41/lib/DBD/CSV.pm

This is probably not what either of you meant, but until 2005, it was illegal to import sichuan peppercorns. This resulted in a lot of dishes missing a fairly important taste, even in otherwise authentic Sichuan restaurants.

http://en.wikipedia.org/wiki/Sichuan_pepper#US_import_ban

I've always liked http://www.cise.ufl.edu/~manuel/obfuscate/piglatin as well.

If I came across the code in the original post, I would be confused as to what the Or operator applied to. With a regexp, the parenthesis make this clear.

I would also assume that Exactly(1).Of(".") was meant to match a literal ".". In a PCRE, you can surround a section with \Q...\E to force literal interpretation, but I believe in .NET you would need to call Regexp.Escape.

The overall concept is not a terrible idea, but you should probably become a little more familiar with regexps before trying to write a library that creates them. While some things in the sample seem a natural product of being code generated (e.g. "@{1,1}" instead of simply "@"), the use of "(?:" in many places is simply not needed.

AFAIK, one database per application would not protect other databases from a SQL injection exploit.

The "ATTACH DATABASE" command (http://www.sqlite.org/lang_attach.html) can open any other database that the current user has permissions to.

You could, as you mentioned, set up a new user for each database. At a certain point, the permissions systems in a traditional RDBMS may be easier to manage.

To those wondering if this is worth it, the method of using a trie-style regexp to optimize this type of word matching has been used in the Perl community for a while now and it does work well.

Starting with v5.10, if Perl encounters a regexp that is just a list of strings, it will even use trie-based matching automatically.

Prior to that, people have been using modules such as Regexp::Trie to build optimized regexps and noted increases in performance similar to the benchmark shown in the post.

Looks very nice, and I had been looking for something like this for a while.

Part of the value proposition to me would be that it is third-party but still controlled by the site owner. By being third-party any verification of external logins you do would be more trusted than the average testimonials page of a very small company. By leaving the site owner in charge, they can know it doesn't look tacky, try to steal traffic, or contain negative reviews.

One feature I've always wished someone would implement would be a way to assure a customer they can easily have their testimonial removed if they end up unhappy with the service later.