I am very comfortable with algorithmic and system design questions. However, what I am struggling with is articulating past experiences. Throughout my last 5 years at my previous employer, I didn't jot down in my personal notes any accomplishments or technical designs. And my memory is so rusty now that I have a hard time reciting them. I understand this is squarely my fault. Wondering if you have any advice on approaching my next job? (senior / manager role)
write them down before you start interviewing. flesh them out over time as you remember more details. focus on the most valuable experiences, ie the ones that had the most challenges (organizational > technical for senior/management roles) or were the best learning experiences.
taking the time to do this ahead of your job search will help you surface those memories when you need to talk about them, much like the leetcode grinding people talk about.
Does CloudFlare have an on-demand image optimization like Vercel? I love that I can specify <Image src="original_image.jpeg width="500px" /> and Vercel just took care of it for me. I am looking for something cheaper and works on native mobile apps as well.
that is a lot cheaper than Vercel in term of store image but egress seems expensive since they charge per cache image served as well. Do you know if Cloudinary is a better option?
I am on the first leg of your journey. Quit my extremely high paying FAANG job to co-found a startup as a CTO. We raised a crazy amount of money for seed. I am just so burnt out (and genuinely feel I am not qualified for the job). I want to swallow my pride and call it quit despite the company is doing ok with a lot of cash left in the bank.
But two things keep me going (in an unhealthy way): 1. My ego and embarrassment 2. credibility with the investor network we built up. It's not sustainable for my mental health but I frankly don't know what my next steps are yet.
All I can say is best of luck to you. I would love to hear how you bounce back from the VC-funded burn to bootsrap another one.
Neon is a great suggestion. I'm just writing to add a bit more color.
Neon is a bit different from PlanetScale. With PlanetScale, they're running Vitess under the covers. Vitess is a proxy that sits between you and the MySQL database. It means they can do fancy things like rewrite the queries on the way to the database or route them differently. For example, a "SELECT" query could be sent to a replica instate of the primary. Likewise, if you've sharded/partitioned your data by customer_id, Vitess could see the query says "WHERE customer_id = 5" and send it to the correct server. This proxy also means that Vitess can seamlessly manage some things for you like failing over to a new database or bringing online a new replica.
Neon is a decoupling of storage from the database processing. While Vitess still has MySQL storing the data, Neon changes the storage so that it can separate data processing and data storage. This is somewhat like Amazon's Aurora.
If you're interested in other PostgreSQL compatible options, CockroachDB is PostgreSQL compatible, but is more of a fully distributed database from the ground up rather than new layers like Neon or PlanetScale.
I've used VueJS/NuxtJS/Tailwind for the frontend and a NodeJS/ExpressJS/Postgres backend.
I've developed everything custom and didn't rely on a headless commerce solution.
it's amazing you built a complex marketplace/commerce site all from scratch. big kudos! if you ever do a paid course on your development, I am more than happy to pay!
Awhh, thank you! I don't have plans for a course, but feel free to hit me up on Twitter if you need any help or advice, haha.
Best way to learn imo is to just start with an idea and tackle one task at a time. Before you know it, you'll have a fully functional and impressive creation on your hands
Pusher provides a way to simulate a stateful WebSocket connection using a stateless server architecture. Jamsocket provides a stateful server architecture where WebSockets have first-class support.
wow this looks amazing. Do you mind shedding some light on how you built this? especially how you organize taxonomy and product metadata for each category
I am working on an e-commerce platform that would benefits a lot from your experience here
I won't get too deep into our architecture, but needless to say letting users dynamically edit/add/remove fields in their databases is not easy. We use Postgres + Prisma as our ORM, and I'm fairly happy with its DX re: handling this level of complexity
Does anyone have practical engineering blogs on big SwiftUI / Swift app architectures? I am trying to wrap my head around all things MVVM, Clean architecture, Coordinator, and Navigator. Individually, I understand the concepts but in practice I have a hard time splitting things into individual components
