sauldcosta

You and your students can get access to a few online coding tools designed to help with this via the GitHub Student Developer Pack and the GitHub Teacher Toolbox (https://education.github.com), all for free.

Our online coding tool (and entire course library) is included in the Pack. https://next.tech/github-students and https://next.tech/github-teachers if you'd like to take a look.

Interesting. Were these small companies, or large ones as well?

We were literally just about to deploy an updated pricing model when our test suite started failing when using Stripe's API.

Yep, definitely is. Have been getting 503s for the last 15 minutes.

Right you are, heh. Not sure why it jumped back to that date. False alarm.

Some people on Twitter are reporting that it's due to a DDoS. http://www.digitalattackmap.com/#anim=1&color=0&country=ALL&... seems to indicate Iran is the source?

Without question. I've never seen an affected regions list that immense.

We use downdetector.com because status pages tend to take up to an hour or so to update, if they ever do.

If your analytics show almost no usage and you're not required to by any SLAs or similar, I'd say go for it. We did recently and it's definitely reduced the mental overhead in our development process.

Our official SLA now is to support the current version and one prior for Google Chrome, Firefox, Safari, and Edge. We also don't support any version that is no longer receiving functionality updates.

The most important thing though is communication. If your site isn't going to work well or at all on certain browsers, alert your users to this with a popup. There are lots of libraries for doing user agent detection that makes this trivial.

Appreciate the thoughtful reply and summary of experiences with GCP vs AWS.

Disagree. If managed correctly a large customer can help grow your startup in some great ways:

- cash to invest into growth, especially if you can derive a higher profit margin than average from the customer

- increased stability ("battle tested") in the eyes of other large companies

- pushes you to build a scalable and secure product earlier on

In my experience with Codevolve (where we prefer to work with multi billion dollar companies) I've found there is a balance between how much they need you vs how much they are willing to bend to your startup mold. If they want you enough, they'll concede certain points to you. Some important things to stick to your guns on are:

- included support (you want to provide as little as possible, and get paid for it as much as possible)

- non competes (you don't want them to get one, or at least not for very long)

- pricing (leave yourself room to grow the account, especially if you have a product that can be used across multiple departments, and you're just starting with one)

The best way I've found to do this so far has been to go "bottom-up": find a champion in the company who will actually use your product. They're much more likely to work with you than an exec.

This is really useful. We're building a lot of courses for Codevolve.com right now and definitely will be using this as a reference for where to focus.

At 24, kids are a long way off for me. But when they do come to pass, my hope is that I can give them a childhood like the one I had: full of rocks, sticks, mud, and band-aids. Thank you for the reminder of how important that is to strive for.

We just launched a new feature at Codevolve that tracks your coding skills for you as you learn. Would love to hear what you think!