Saw this tutorial on organizing into Follow-Up, Awaiting Response and To Read Labels. https://www.youtube.com/watch?v=oLdHnWLbn4A
How do you guys keep everything sorted and what's your typically workflow?
I am considering creating a feed, it couldn't be that hard, could it?
What are your experiences?
Golang: Sets the standard for efficient backend development.
GCP: Guides the team in scalable cloud deployments.
Kubernetes: Crucial for leading complex system management.
Docker: Ensures consistent application deployment quality.
Kafka: Leads in building real-time, event-driven systems.
REST and gRPC: Offers diverse and efficient API solutions.
Event-driven Architecture: Directs the development of scalable, responsive applications.
Frontend Knowledge: Bridges backend and frontend efforts for team synergy.
Event driven Microservices
I don't sit with Golang, Kubernetes, Docker, Kafka, gRPC in my own hobby projects. However, it would be fun to get to know this tech stack in an upcoming project. Do you guys have any suggestions of projects that I could to that utilize this tech stack?
I want to be able to send and receive emails from my custom domains but not pay 5-49$ a month in doing so.
What options do I got?
Saw these alternatives but I don't know what you guys recommend.
- https://www.cloudron.io/index.html
- https://cyberpanel.net/
- https://www.hmailserver.com/
- https://wildduck.email/
- Sendmail and dovecot on a (Rasberry PI) RPi
- https://www.makeuseof.com/make-your-own-raspberry-pi-email-server/
To clarify, I don' t mind the UI looking like it's a website from 1998. I just want to be able to read and send.
Fellow developer here and I am curious how many developers struggling with flaky tests in terms of keeping the CI/CD pipeline green and not fail intermittently.
- What kind of struggles are you facing today? - How are you tackling those issues? - What tools would you like to see to help combat this?
I am not sure how companies handle flaky tests, some people at companies might just shrug their shoulders and retry the pipeline until they pass (that's what I've experienced out in the field), others assign them and investigate? What do you guys do at your company?
I am keen on developing a tool that would help developers track and debug flaky tests by using tracing while running tests which I don't think any tools do in that extent today. Also utilizing LLM's to pinpoint root cause of failure would be interesting in that context to help fixing flaky tests.
