Earlier quoted context omitted.
> It's deploying, testing, environment issues, metrics, databases, dns, etc. Basically it is a lot more complex than "learn to code". I would even go further and say that such things are well over 50% of a working programmer's time. Learning the toolset for modern programming is as hard or harder than learning how to program well. It's a different kind of hard, though -- the ability to slog through tedium and frustra…
Slogging through tedium and frustration has been a cornerstone of programming since the olden times
GitHub Student Developer Pack
161–170 of 226 posts
Re: GitHub Student Developer Pack
#162Re: GitHub Student Developer Pack
#163Re: GitHub Student Developer Pack
#164Hey does this apply to college students?
Re: GitHub Student Developer Pack
#165Re: GitHub Student Developer Pack
#166Earlier quoted context omitted.
Hm, that's nice of them, although this page states you aren't allowed to do that: "Keep in mind that we only allow one promo code per account, so if you’ve redeemed one in the past you may not add another. To see your promo code history please visit your billing page." https://www.digitalocean.com/help/pricing-and-billing/
We're making an exception to our existing policy for those who wish to participate in this program.
Re: GitHub Student Developer Pack
#167So if you have an existing DigitalOcean account, it makes it seem like you can't apply the promo code to it. But I shot off a ticket to DigitalOcean's support, and they applied the $100 promo to my account within 5 minutes. So definitely send them a message if you have an existing account that you would like to have the credit applied to. Awesome pack, and great service from DigitalOcean as well. Also of interest is…
Re: GitHub Student Developer Pack
#168I wish they had these things for drop-outs like me.
Re: GitHub Student Developer Pack
#169Earlier quoted context omitted.
I like starting a school-related project as a private Github repo, then as time or permission allows for to open it up as a public repo. I've open-sourced a few things this way, whereas the couple Bitbucket repos have been left to languish since I don't have a limit on private repos or the ecosystem to share it with.
You can always push your private BitBucket repos to public Github ones -- just add another remote and push there.