What Lessons Do Startup Tech Stack Choices Teach Us? A Real‑World Case Study

Background

In June 2022 the author joined a very small logistics startup whose founder lacked technical and managerial expertise, leading to rapid but poorly planned growth that eventually resulted in the company’s dissolution and unpaid wages for the final months.

Initial Technology Selection

With a team consisting of a fresh graduate front‑end developer and a UI designer, the author chose a stack that leveraged existing JavaScript skills:

Use uni-app for cross‑platform mobile app development, enabling future mini‑program support and fast delivery of a minimum viable product.

Use egg.js + MySQL for the back‑end, offering quick development, sufficient performance for the niche domain, and an easy migration path to midway.js later.

Use antd-vue for the admin console to keep the front‑end technology consistent with uni-app and reduce conversion costs.

The combined stack ( egg.js + MySQL + uni-app + antd-vue) allowed the team to build two mobile apps and an admin backend from 0 to 1 quickly.

Why egg.js Was Chosen for the Back‑End

The founder prioritized cost over technical perfection. egg.js met the requirements because it is simple, fast to develop, familiar to the author, and has a low learning curve for new JavaScript developers, unlike heavier Java, PHP, or Go solutions.

Mid‑Project Turbulence

Development proceeded smoothly at first, but the product failed to launch quickly, and the founder repeatedly demanded changes based on unrelated expert opinions, redesigns, and a push to hire native or Java developers without clear justification. New requirements emerged, including system upgrades, a mini‑program version, a new supporting system, instant messaging, and various small features.

Later Technical Adjustments

Changed the app packaging approach.

Introduced midway.js for new business modules, leveraging the team’s existing egg.js expertise and preparing for future standardisation.

Managed internal npm packages and built a shared component library.

Standardised code style and development processes.

Hiring and Team Management

Recruitment

Hiring for a tiny company is difficult, especially with limited salary budgets. The chosen stack mitigated this by allowing developers proficient in JavaScript to work on both front‑end and back‑end tasks, reducing the need for specialised hires.

Team Management Practices

Adopt a business‑oriented, realistic approach in the early stage.

Prefer full‑stack development to avoid coordination bottlenecks.

Define coding conventions based on the team’s habits to improve consistency.

Enforce a disciplined development workflow to prevent chaotic management.

Follow a standard pipeline: product evaluation → task allocation → technical assessment → development → testing → code review → deployment → post‑release issue tracking.

Measure performance through task deadlines, documentation quality, bug count, and careful database modifications.

Encourage knowledge sharing and continuous learning.

Maintain timely communication about progress, challenges, and personal feedback.

Final Takeaways and Pitfall‑Avoidance Advice

Ensure the founder is reliable and decisive; otherwise, the venture is unlikely to succeed.

A trustworthy founder can still create value even if the current project fails.

Focus on generating revenue; without cash flow, survival is doubtful in today’s financing climate.

Prioritise core business problems over tooling or code style; technical decisions can be deferred.

Provide regular progress updates to align with the founder’s high‑level perspective.

Extract learning from every experience; each step adds meaning to the professional journey.