Great but only so long as you want to use their nameservers. I had a domain with them that I wanted to use with AWS Route 53 nameservers which I was unable to - then I had to wait the standard ~60 days before I could transfer it out which caused a headache in the meantime.
oh that’s a major bummer they won’t let you customize NS records for domains you buy on their platform. not a huge deal for most of mine but some of them…
You can set NS records for subdomains though... I have done this for a couple of domains where i have internal.<domainname> and that points at Route53. I also use Route53 for my Reverse IP lookups, since Cloudflare does not seem to support this (unless i missed something).
On an related note, what does Route53 give you that you cant do on Cloudflare?
Ahh ok. That's not so bad. It's really only for one 'learning' domain or such where I set it elsewhere. But it's by far the minority of the time that I didn't just use Google's built in one (or used GCP's) for the API which Cloudflare has
Cloudflare is straightforward to use but watch out, they don’t let you use custom nameservers, which is very unusual for a domain registrar. As great as Cloudflare’s nameservers are, this was a dealbreaker for me and I eventually moved all my domains off of there.
"[Almost]" doesn't appear in the title of the article as currently linked. I would also agree that there is no need for an "almost" anymore - voice cloning can be pretty spot on e.g. this fake Joe Rogan interview with Sam Altman[1].
I have noticed this as well sometimes, though never thought it might be intentional, I'd doubt it is. You can always hint to ChatGPT which language to use for the codeblock anyway though.
I'm involved in building a backend right now for which I chose to use AWS ECS with Fargate containers for deployment, over some managed Kubernetes service like AWS EKS which would have been my first choice. Using ECS has been dirt cheap (<$5pcm) whereas AWS EKS is ~$75pcm per cluster, before you even start running any containers. I'm not completely sure it was the right decision as it's involved having to spend time getting familiar with ECS, but it seems to work well enough and cheaply for something which isn't making money yet. I probably could have provisioned a Kubernetes cluster myself using something like kops but didn't want to deal with the headache.
Another one is using Heroku (~$7pcm) over Vercel (~$20pcm) for deploying a simple website/CMS for a business (and therefore not eligible for Vercel's free hobby tier). I initially wanted to use Vercel but Heroku is actually fantastic if you're developing solo and don't need all the bells and whistles Vercel provides.
I would mention something to that effect in the modal because it wasn't clear to me why it was asking for card details at that point for "$0.00/mo" (though I guessed the reason). Maybe something like "To prevent abuse, we require card details, but you won't be charged", but worded better.
"no matter what based on your usage/you are locked into the free tier" would have helped for sure
i still would've bounced because i just wanted to goof off with it quickly while it captured my attention and requiring a payment method is just... terrible friction to capture users being able to quickly test one of the key features you advertise, but i guess if fraud concerns are that bad, that's the tradeoff you have to accept?
No, I lean in the opposite direction - I would be more inclined towards employment opportunities which have a reasonable coding challenge as part of the hiring process. In my experience, there is a strong correlation between how technically challenging the hiring process is and how good a place is to work as an engineer. A reasonable coding challenge is a signal that there are competent engineers within the organization (in order to be able to come up with and mark such challenges), and that the organization values engineering capability to some degree.
Of course, there are exceptions to this. I'm also explicitly excluding here employers who outsource the technical challenge to a third party like leetcode.
That's ridiculous! Obviously not every software engineer knows algorithms and data structures, but if you do pass a leet code question you have at least some minimum of skill.
It's shocking how many interviews I've done where the candidate can barely code anything unfortunately, so it is absolutely worthwhile.
Having done many coding interviews I can assure you there is more to it than memorizing a problem and solution. I don't see how asking someone who is applying for a software engineer job to do a miniature software engineering task is controversial!
It has not, although it has greatly changed how I program and learn. We are currently entering a period where "centaurs"[1] - humans using AI - will be the most effective agents for many tasks, including programming. With that in mind, I'm enthusiastic to embrace AI as a daily tool, knowing it will let me do things faster and better - but I don't expect this period to last forever and so it has put a sense of urgency in me to execute rather than just ideate, which I did not have before the dawn of things like ChatGPT.
Not sure why that article went with centaurs; I think cyborg is a more accurate term. Just asked ChatGPT for a term for half human / half AI and it suggested cyborg as well.
GitHub Copilot for coding, and ChatGPT for sundry tasks, mostly summarizing and explaining written text. I pay for both of these tools now. ChatGPT seems great in particular for summarizing YouTube videos (I copy and paste a YouTube video transcript) and email newsletters. I also use it alongside reading longform articles to expand on or clarify parts of the article I don't fully understand or want to know more about. You can also ask it follow up questions when using it in this way (e.g. for examples of the concept or thing you don't understand).
I would second this. Having interactive examples alongside the documentation (in multiple languages nonetheless) was something that stood out to me the first time I had to read the Stripe docs some years ago.
