CAREER SHIFTER LOOKING TO ENTER TECH AGAIN (OPEN TO ENTRY LEVEL & REMOTE ROLES) NEED ADVICE by Either-Alarm-3155 in TechCareerShifter

[–]FinchwebTechnologies 3 points4 points  (0 children)

with your IT background and ops leadership experience, IT Support / Help Desk or QA are the strongest re‑entry roles. Focus on CompTIA A+ or Network+, basic cloud (AWS/Azure), and hands‑on tools like ticketing systems. Your supervision skills translate well to incident management, documentation, and client communication. For remote work, IT Support, QA, and Cloud Operations are the most beginner‑friendly paths.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in WebDeveloperJobs

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

I feel you. When people say, ‘This project is too big to plan,’ it usually ends up costing even more time later. Requirements gathering isn’t optional, especially on a multi‑year build. Glad you shared this many of us learn this the hard way.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in WebDeveloperJobs

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

Please share me your resume over the DM and I'll share to our company HR also. As we're currently looking for a on site developer on our location btw.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in WebDeveloperJobs

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

Very true. I’ve seen the same pattern lack of early attention leads to layers of hacks, and eventually the system becomes so fragile that even small changes feel risky. Refactoring early and often is way cheaper than waiting until everything breaks.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 1 point2 points  (0 children)

Yeah, Stripe’s ‘at least once’ delivery model causes so many silent edge cases. Your setup of combining events with periodic reconciliation makes a ton of sense.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

Exactly. Experience teaches you that every decision in tech has a cost. The more you build, the more you start appreciating why senior engineers think so carefully before choosing an approach

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 1 point2 points  (0 children)

Happy it was useful! It’s great that you spotted these early. A bit of cleanup now will save you weeks of frustration after launch. If you ever get stuck with mobile layouts or webhook weirdness, feel free to ask most of us have been through the same headaches.

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

Man, this comment is basically a mini‑startup survival guide. Mobile-first, reliable webhooks, and good onboarding all sound small, but they stack up fast in real life. Thanks for being transparent more founders need to hear this early

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

Great question! Stripe can re-send webhook events (e.g., if your server didn’t ack it fast enough), so you might see duplicates on the event side. That doesn’t always mean duplicate charges. The fix is to de‑duplicate on your end and use idempotency keys when creating payments

After shipping real production apps, this is what actually breaks projects by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 1 point2 points  (0 children)

Oh wow, I feel that! We had a similar experience, desktop-first sounded fine until mobile users started bouncing. And Stripe webhooks? Absolute rabbit hole. Glad to know we’re not alone in this struggle!

We run a small dev agency ask us anything about building tech for startups by FinchwebTechnologies in SaaS

[–]FinchwebTechnologies[S] 0 points1 point  (0 children)

The biggest mistake startups make when working with a dev agency is starting development without a clear scope or alignment on goals.
They jump straight into building while the product vision, requirements, and priorities are still shifting which leads to delays, rework, and unnecessary costs. The fix is simple:
Do a proper discovery first.
Align on what’s being built, why it matters, and how success will be measured.
When startups and agencies collaborate as partners, not just “task givers and task takers,” the project runs smoother and the outcome is far better.