snikch

Yep ^ This is what I often do too. Simple, but effective.

Your #1 isn't correct. Collaborators don't count as a seat if they don't have access to a private repo.

> These users do not fill a seat: Outside collaborators with access to only public repositories

https://github.com/blog/2164-introducing-unlimited-private-r...

Typo on Original Assignee? "Correlated Megnetics Research, Llc."

I feel the same problems with scaffolding / boilerplate, but I'm not sure I want to bring in Ruby / Cucumber to run my acceptance testing. These are just as easily written in Go too.

Liking all the rest :ok_hand:.

My favourite bit of this article was where they pad the struct to move each field onto separate cpu cache lines and see a 15% speed increase.

Quick note on 3.b - Go 1.5 didn't introduce cross compilation, that's been around for much longer.

I think you meant to comment on https://news.ycombinator.com/item?id=10069521

If it enables a start up to grow without having to worry about scale, I don't think so. You could say the same of a lot of the technologies in a cloud provider. At the end of the day, if you want to take advantage of the speed to market and cost reductions these technologies enable, you're going to have to take a punt.

IMO this sums up one of the biggest benefits with Go, and unfortunately goes against your own point. There's no need to know about a variety of community built tools, or what's the "best solution" in language X - the std lib gives you what you need. You can stand up a service quickly because it's simple, and there's no "in knowledge" required.

I'm not 100% sure on this, could you only delete albums for users who had given access to your app, or was it any user at all?

This is a really hard question. It's also the reason my product never took off. I've got ~50 loyal customers who love the platform and send millions of emails a week but I never found a co founder to come along for the journey.

I looked locally and abroad for a founder, and had investors ready to continue to back me. I'm a good engineer and gave sales a go but realised I'm just not cut out for it. I put up ads and got plenty of interest (early product hunt advertiser) but never found the person making investors were willing to put their cash on the line for.

It's a tough find. Especially if you don't have a sexy as fuck product. I wish you luck!

Tl;dr without a go to market or sales co founder, chances are you're fucked.

Edit: Abysmal spelling.

You use a rack middleware to handle static files, which is how Rails handles it by default. So, unless I'm completely mistaken (which I may well be), this should work just fine?

Current is most definitely != latest. Current means any model that is still in production and being sold, although admittedly for some manufacturers those two things don't usually align, Apple has a tendency to remove models immediately from the line up when they cease production.

While elastic search queries ARE verbose (we've clocked up a query 23 levels deep in our app), the first example stated here is unnecessarily verbose. He's using a `bool should` query, with only one value in it. A `bool should` is basically an `or` statement, so he could replace the whole thing with the single query he has inside it.

This definitely feels like a rant that picks up on a few issues with ES, and then smothers it with a variety of things which are different, but not really "issues". I've found the ES documentation to be a bit fragmented, but good once you know where things are. It's not the most newbie friendly system, but once you're up and running it's incredibly powerful.

I find your response to be really arrogant. Postman is an easily installed Chrome extension that can be supplied to everyone on your team, regardless of skill level. Requiring a cli isn't as easy as a one click install - there's dependencies (Python etc.) that are required which, while easy for many, aren't as simple for a lot of web developers - especially those who focus on front end development and may just need an easy tool for inspecting API requests they need to make.

There's still a wide market for GUI based programs, and Postman is an excellent extension that I've used for years (even though I'm a CLI guy myself). It's always there, easy to use, and powerful to boot.

Edit 1: Grammar / Spelling

I had a look at doing this myself recently to do iPhone -> Laptop transfers. Does this work for mobile -> desktop? I didn't think that WebRTC was available on mobile safari and therefore wouldn't work.

I have an interesting question. Currently my AUD$ balance is displaying as $0. However in December and Febrary I had asked to withdraw $1,000 and ~$400 to my Australian bank account. Those transfers were taken from my balance, but merely sat as 'confirmed' rather than 'processed'. What happened to my money?

Both are.

https://twitter.com/pjhyett/status/89064336454201346

If you're getting an error "The crypto field is required", I got that when trying to enter a dollar value but no BTC value. Enter 0 for BTC.

3. is the most important there. The other questions could be speculatively answered. But there's no way to explain a 20M imbalance without some sort of criminal negligence, which would make any sort of rebrand / relaunch absolutely impossible.

I believe that would be the point of <meta http-equiv="X-Frame-Options" content="deny">

What do you do for directives that are shared across your whole app?

While I love Angular, I feel the author is wrong on a few things. It doesn't provide a way to structure your codebase, that's still up to you… directives.js isn't going to scale at all. That's also one of the things I love about angular. The code is modularised, but that isn't enforced on the filesystem. You can choose to lump things into files in a folder for directives, or you can put all your routes, directives, filters etc for each feature in a feature folder. You have plenty of control.

Also, I feel like their example is better served as a filter, rather than a directive.

We needed this for our site. You can add as many 'domains' as you like, each with their own plan. Instead of creating a new customer + subscription we hacked together a way that each customer gets a unique 'plan', which can be multiple subscriptions. Multiple subscriptions per customer would have saved us a lot of time.

The other option was asking the user for CC details each time and creating a new customer at Stripe - but that felt like friction.

Sigh, I cringe even remembering this one.

We were storing payment details sent from a PHP system into a Ruby system, I was responsible for the sending and receiving endpoints. Everything was heavily tested on the Ruby end but the PHP end was a legacy system with no testing framework. Since the details were encrypted on the Ruby end, I didn't do a full test from end to end AND unencrypt the stored results.

Turns out for two months we were storing the string '[Array]' as peoples payment details.

Takeaway: If you're doing an end to end test, make sure you go all the way to the end.

And the write-up from the author: http://www.sitepoint.com/css3-pong-insane-things-to-do-with-...

I think the operating profit for Oct[1] should have a negative in front of it.

[1] https://mediacru.sh/transparency/2013-11-01-Financial-summar...

dotenv allows you to store env values in the .env file. envconfig handles normalizing the various ENV values from providers into a single configuration. Every provider has a different env value, such as POSTMARK_SMTP_SERVER, or SENDGRID_SMTP_SERVER. envconfig knows about these and provides a single service agnostic interface to that information.

.env and envconfig work very well together.

With Amazon's cloud storage for books, not just ones purchased through them, the storage should really be considered ephemeral. I don't think that having enough space to store a large library of books should be considered a showstopper, when you can download books you've sent to your kindle via email at any time.

I do agree with the mechanical buttons. I love my PW, but miss the buttons.

Interestingly, they recently adding a Content Security Policy, which I would have thought would have prevented this bookmarklet.

https://mega.co.nz/#blog_19