This has been on my list for quite some time: an open-source, fully serverless webhook-as-a-service that can be deployed into your own AWS account using AWS CDK. (repository in thread ๐)
One aspect Iโm excited about is that it already uses the newly released AWS Durable Functions, which provide a simpler abstraction over Step Functions. They simplify implementing reliable webhook delivery patterns such as retries, backoff, and failure handling.
The funniest thing I heard this year in my conference travels is that Prisma is actually a VC-backed company thatโs now scrambling for revenue while Drizzle is just some 10x engineer having fun lmfao
the aws space needs new creators in it - it's a total wasteland
if you are an aspiring creator considering focusing on it - the bar is so low and there's a chance for someone good to dominate
Product teams forget the culture in the midst of frameworks and processes. Whenever someone asks me about creating quality, I always start talking about hiring first since people most impactful contributors and participants of any kind of culture.
@jeff_weinstein:
"I think it is contagious to want to build great things and you can dilute yourself if you're around people are motived by something other than building a product people love"
I also loved Jeff's point about instead of talking about quality, talk about "building something surprisingly great".
Tailwind is such a joy to use. If you learn one utility class, you know all utility classes. If you implement something on one project, it works on all projects. And it never breaks. It works exactly as it worked since v0.3 and keeps getting better and faster.
The CloudWatch book is out! ๐
If you want to learn CloudWatch with a real-world project and a hands-on video course, check it out ๐
You get 25% off with the code ๐๐๐๐๐ ๐ธ
Book: $59
Code & Book: $134
Video & Code & Book: $194
Bonus: If you buy it within the first week, you get the AWS Fundamentals book ๐๐จ๐ซ ๐๐ซ๐๐ ๐
๐ https://t.co/HwFTnwDXg4
Product Engineer Checklist TLDR ๐
What is a Product Engineer?
Definition: Product engineers are not just coders but builders who care deeply about the entire product, from design to customer satisfaction.
Counter to Hyperspecialization: Unlike specialized roles (e.g., frontend, backend), product engineers have a holistic view, bridging gaps between different technical domains.
AI: AI tools enhance the role by making specialized tasks more accessible, allowing engineers to focus on product strategy and user experience.
Product Engineer Manifesto
Core Values: Builders first, software engineers second. Emphasis on combining product thinking with technical execution.
Principles: Asking why, continuous delivery, market & customer understanding, teamwork, dogfooding the product yourself, and strategic thinking.
Checklist
1. Understand
User: Identify who the user is, their needs, pains, and how to delight them.
Customer: Distinguish between users and paying customers, understand what makes the product valuable to customers.
Market: Analyze the market landscape, competition, and industry standards.
Ask Why: Continuously question to uncover root causes and motivations.
Leverage Existing Knowledge: Build on existing insights, avoid starting from scratch.
2. Craft
Pride in Work: Maintain high standards, avoid technical debt, and ensure quality.
Product Feel: Develop a taste for what makes a product great; focus on smooth, intuitive experiences.
Efficiency: Deliver quickly and iteratively, prioritize visible progress.
Teamwork: Effective communication and leveraging team strengths are crucial.
3. Growth
Measure Success: Use analytics and feedback to evaluate the impact of your work.
Maximize Impact: Focus on significant bottlenecks, align efforts with company goals, and seek feedback.
Stay Ahead: Stay updated on trends, benchmark against competitors, and encourage innovation.
4. Product Vision
North Star: Align with the broader product vision and strategy.
Design Impact: Ensure new work fits well within the existing design, aiming for simplicity and consistency.
Ambition Level: Define whether the goal is incremental improvement or revolutionary change, and prioritize accordingly.
This checklist serves as a practical guide for software engineers who wish to level up their career to build great products and break the stereotypes of engineers being thought of as only narrow technologists.
hey @DRo_604,
Will the SFN Http Invoke Task support different transfer-encodings in the future? I feel like using "chunked" does not make a lot of sense, esp. because the payload size is known in advance. Would appreciate your thoughts on this? ๐
aws help needed: is it possible to give the step function http task a s3 ref and get the content as the request body? I really want to use it but sfn do have the 256kb limit, hence I'm not sure how to bypass that currently :(
Implemented Speculation Rules pre-rendering on our app ๐ช
Love the dev tools view to actually see the defined rules and whats pre-rendered and so on โค๏ธ
Shoutout to @tunetheweb for the resourceful writeup and video here: https://t.co/1m4vz0R7BO
#web