Google phone interview long time ago. Can’t remember what I said or did wrong, but realised I wouldn’t get a call back when the guy asked: ”do you know what a set is?”
My 2c is to try the funky ideas to get a foothold/differentiator
I think your implicit intuition that indie gamers are keen to explore more titles than they currently (reasonably) can, is valid. I suspect they’re also keen to be involved in early development. And devs are interested in early feedback. So you could introduce something to facilitate that. Or introduce a Patreon/kickstarter type model where you can choose to fund development of games from your subscription.
Network effects are valuable to build in/explore - make it super easy to stream the games on Twitch, Share clips on YT etc. Might help with the chicken and egg!
Having some kind of "early access/alpha" is an idea we had, but something more like patron is a really good idea. Thanks for the suggestions on network effects! We're doing our first YT partnership on Monday, so I'm excited to see how it goes!
Is this region dependent? In us-east I can’t get them to approve a quota for GPU instance families (G,P) for anything more than 4 CPUs. At one point they rejected my request citing “unprecedented demand”. Of course this is small time, just my personal account.
It is true I can get an instance most of the time, but not if I need >16GiB GPU memory.
We've been having the same problem getting GPU instances on us-east. Multiple week-long delays to escalate and talk to yet the next person up who can make a decision. It's a mess.
Take risks, say yes to all opportunities, try to fail often.
I don't mean risks in the sense of things that put you physically or mentally in harm's way, but trying ideas, learning new things, new activities etc.
Some reasons: the explore/exploit tradeoff is massively in favour of exploring when you're young, you have almost nothing to lose, very few responsibilities and so much time (relatively speaking to later in life).
A beautiful book, written in the "The Little..." series' question and answer format. A challenging topic but just about as accessible as I can think anyone can make it. Warmly recommended if you want to know what dependent types are all about.
I have an MSc in CS so biased, but I think on balance it's worth it, if only because you'll be confronted with subjects outside your comfort zone. Even if you don't "like" them they'll broaden your perspective, and who knows you may learn about something you wouldn't have heard of before, and really interests you.
Definitely depends on the curriculum though - my advice would be to look for timeless subjects, so "Algorithms and Data Structures" over "Game Programming with Unity", with a lot of variety.
This is all from the perspective of you being interested in learning new stuff regardless of monetary gain. If you're thinking of this more transactionally, i.e. "will I be able to get more money/better paying job" then I think it depends a lot on where you live. In some areas formal education is valued more than in others. Also a good part of it will probably not be immediately applicable to the day job - at least not obviously so - but it should give you a decent perspective on the field as a whole.
With your very limited runway I'd get another offer with another employer first. That immediately strengthens your negotiation position with your current employer, even if you have zero intention of taking the offer.
Basically start doing some interviews now. You'll probably have to brush up for those as well, and practice.
> I feel stuck and bored
> Working 9-5/Mon-Fri is really draining
These two statements are contradictory imo. Figure out whether you want to stay in your comfort zone, or take a step in another direction.
"We have a time every morning when the team gets together and reviews all of the code and designs that were developed the previous day."
That seems much better than the mandatory code reviews that are pervasive nowadays. Most of my annoyance with those is the mandatory part - I think it increases the threshold to make small improvements sufficiently that they either don't happen, or happen together with unrelated changes, which is then a reason for the resident purist to scold you. I also think doing them asynchronously, as a form of email, rather than in-person or video introduces friction unnecessarily.
