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?”
90 karma · joined February 5, 2021
Twitter: @kurt2001
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!
It is true I can get an instance most of the time, but not if I need >16GiB GPU memory.
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).
Honestly I don’t have answers but here’s a few ways I’ve found cool people:
- via “slow-grow” communities like lobste.rs
- if someone writes a good comment or tweet or whatever, check out if they have a blog
- Sometimes I subscribe to a bunch of things that seem promising, and then follow a “three strikes and they’re out” policy to extend the reach
- start reading papers from conferences. It’s a heavier format than blogs, but it’s reviewed and novel, at least if you pick good conferences.
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.
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.
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.
I remember writing a very small single user OS for a course in uni over maybe 6 months. When it booted for the first time it felt amazing. That was like an “I have made fire!” moment.
Now I’m supposed to feel like I’ve achieved something because I can center a div on a webpage.
What is cool is helping non-programmers with automating some of their tasks, like rearranging a spreadsheet or scraping some data. I mean they think it’s some amazing feat but it’s actually very simple. Lots of low hanging fruit still, esp for every day users. Again mostly due to the horrible accidental complexities and buggy mess software has become, so I feel mostly apologetic about it. “Yeah sorry copy-pasting this data should really just work but I’ve written this script which applies a few workarounds”.
1. So many caveats and excuses before raising some valid criticisms! People in the cryptocurrency space sure seem easily offended.
2. Most of the article deals with how cryptocurrencies have no real applications. I would add that in the areas where applications do exist, they’re way better solvable by non-crypto solutions.
Just my experience, don’t underestimate how much working a job limits you and your creativity.
Unfortunately this will get me further from the line rather than closer (unless I somehow strike gold) but I figure the only thing I can’t make again is time.
Unsuccessfully trying to convince friends to stay away from crypto did give me loads of empathy for people like climate scientists - you spend your whole life trying to measure the average surface temperature accurately, and some random dude goes "but what about the summer of 76". It's just too easy to quickly dismiss relatively complicated arguments or explanations.
We - hipster programmers - were incredulous at first but actually seems like a great business model.
It takes your local code and environment (we support pip, poetry and conda) and runs python code on AWS or Azure (though Azure might have some rough edges still). You can specify what kind of machine you want based on cpu/memory etc, no need to deal with weird instance names. You can get cheap spot instances etc.
Discussing marketing to figure out how to best get the project off the ground and find users.
Writing some posts for getcode.substack.com
Reading Godel,Escher,Bach finally!
What they're doing does feel icky, and they could have mitigated a few concerns by a) making the inventory of the full training set public and b) at least attempt to attribute if there is a direct copy (which by their own admission happens about 0.1% of the time). These seem very simple steps they could take, and takes away the "shady behavior" argument.
tag, estimate, assign, add to epic, put on next sprint
We were unaware of ploomber until now, but have been building meadowrun https://news.ycombinator.com/item?id=31694827 and share many goals with you. So obviously I think this is solving a real problem.
All the best with the cloud launch!
We've looked at the code for PyWren and in our opinion it's not practically usable as-is, even if you wanted to target only Lambda. Also we initially focussed more on the deployment aspect (i.e. getting environment + code on the target machines reproducibly), and EC2 because we figured to make this general enough people would need an escape hatch anyway if Lambdas didn't cut it for some reason.
[1] https://github.com/Vaishaal/numpywren
[2] "From Laptop to Lambda: Outsourcing Everyday Jobs to Thousands of Transient Functional Containers" https://www.usenix.org/conference/atc19/presentation/fouladi
We're two programmers who have worked in core/platform engineering roles for most of our working lives. During that time, one of the main problems we've solved time and time again is to let people run their ad-hoc jobs and scripts on remote compute without hassle.
To solve this once and for everyone, we made Meadowrun, an open source tool that automates the tedious details of running Python code on cloud VMs. It runs in your AWS or Azure account, nothing else required.
No need to mess around with containers, SSH into remote machines, copy code across, set up images or look up instance types that sound like Starbucks orders ("t3.venti.oatmilk.latte") and what they cost.
All with the same experience as you'd have running on your laptop - just change the code or dependencies locally and run - meadowrun takes care of the rest.
We welcome any and all feedback!
Maybe it can also search by signature like https://hoogle.haskell.org/ - would be a killer feature for me, but niche :)
I'd very much welcome contributions on documentation, and esp. on approaches of how to keep the C#/F# documentation consistent and still accessible for both types of users. Even if it's just ideas/comments - how would you like the documentation presented? What are examples of excellent C# documentation? We need to balance that with available resources - we don't have a team of ghostwriters to write docs and examples for every language, as you can imagine. I know it's a cliche by this time, but if every user would take a couple minutes to write a paragraph or example where e.g. the C# docs are lacking, it might be in a much better state. From our side, if something is stopping you from contributing in this way, we'd like to hear about it. Addressing that is important.
Separately, I'm surprised you experienced that generators are significantly more tedious to write in C# vs F# - could you open an issue with a few examples of this? This would inform v3.0 where we will stop trying to use tricks to make the F# API accessible, but instead add a bespoke C#/VB.NET API in the FsCheck.Fluent namespace, and separating F#'y bits in FsCheck.FSharp.