GitHub Pages and a custom subdomain.
Build the first public landing page, configure GitHub Pages, connect swe.tickerbell.biz, understand DNS, and verify that the site is truly online.
Learn. Build. Publish.
A real journey into software engineering.
The software engineering journal
From the first webpage to a protected backend. Follow the decisions, challenges, and practical lessons behind becoming an independent software engineer.
The lesson library
09 published lessons
Read online · Sign in for PDFs
Build the first public landing page, configure GitHub Pages, connect swe.tickerbell.biz, understand DNS, and verify that the site is truly online.
Add the tracker, connect every journal CTA, test the form, confirm the email, inspect the Brevo contact list, and document the frustrating parts honestly.
Separate the public learning repository, production frontend, and private backend; define secure boundaries for GitHub Pages, Google Cloud Run, Auth0, Brevo, and secrets.
Define the website type, purpose, audience, sitemap, content sequence, customer journey, requirements, success measures, and phased scope for swe.tickerbell.biz.
See the complete 30-step process for developing software from a problem to a maintained production system, and understand why project-based learning follows a different sequence.
Choose a learning-driven architecture with Firebase Hosting, Auth0, Cloud Run, Firestore, private Cloud Storage, and GitHub-based deployment—while keeping every security boundary explicit.
Move the existing static frontend from GitHub Pages to Cloudflare Pages, connect swe.tickerbell.biz, diagnose the failed npm build, and verify the new deployment path.
Connect hosted login, define Learner, Team and Admin permissions, fix navigation, and apply consistent branding. Understand why private pages still need backend protection.
Deploy a protected FastAPI service from GitHub to Cloud Run, handle cloud permissions through Cloud Shell, and test the learner’s request. Database persistence is the next milestone.
Why we chose this journey
AI has changed how software is created. People no longer need to know everything before they begin, but they still need to understand how systems work, how to guide AI, and how to evaluate what it produces.
We started this journey to explore how a founder can use AI as a learning and development partner while gradually becoming an independent and responsible software builder.
Your path to software engineering
Move from the foundations to reliable, measurable, automated software. Learn one concept, build something small, test it, document what went wrong, and improve it through real projects.
Learn HTML, CSS, and basic JavaScript—the building blocks of the web.
Track every change, collaborate safely, and publish small public projects.
Learn Python fundamentals, logic, data structures, and problem-solving.
Build responsive, accessible interfaces with JavaScript and React.
Lesson 9: a protected FastAPI service on Cloud Run. Follow a request from the dashboard to the backend.
Next: save learner progress in Firestore and verify persistence. SQL and PostgreSQL remain later learning topics.
Lesson 8: Auth0 login, roles and navigation. Lesson 9 adds the protected backend API.
Write unit, integration, and end-to-end tests so changes can be trusted.
Deploy the backend from GitHub to Google Cloud Run. The frontend stays on Cloudflare Pages.
Test, build and deploy from GitHub Actions using short-lived Google Cloud credentials.
Measure visits, user journeys, conversions, and performance to improve the application with evidence.
Connect the frontend, backend, database, security, tests, deployment, and analytics.
Develop documentation, system design, code review, teamwork, and communication.
Keep learning · Keep building · Keep shipping
Keep learning with us
Follow the learning journal as we build, test, and publish the next milestone.
Contact · Budapest
Collaborations, partnerships, or a question about the journey.
Népfürdő u. 22B · 1138 Budapest, Hungary
Monday–Friday, 9:00–17:00 CET / CEST