

Whatever you are continuously learning about tech or non tech things, like any other walks in life, this path, being a developer, will only work for you if you mean it. So I say, do not just finish, live and develop things!Īction Plan - Manifest ownership. Even if it's a group work, if you treat it as your own and keep striving, there will come a time when you will be the one to set your own standards, that meeting target "deadlines" is just a factor, not the single goal. If you are serious on becoming a dev, you have to invest in all the things you need to establish yourself as one. Honestly, I kinda feel disappointed a bit when things don't work whatever the reason might be, but yeah, you just need to dust if off, replan and try again to focus on how to become better. To Improve - Sense of urgency mah friends. I trust you guys to treat every dev day a humbling experience. I tried my best to make them always realize this every session we take, and I kinda feel guilty of succeeding in making them feel stressed or pressured or burnout even if they are still in Avion now, but NO. But this is how it is even if you are on the job itself.

Went Well - Continuous learning at its best! This sure is a given, because no matter how much we try to catch up on the latest technologies, we will always feel a bit late in the game.

that's why we did a retrospective meeting too before taking our traditional class picture as we end their FE journey.Īfter hearing their own insights, I'm sure they know what to do, but as a parting gift, here's mine: Front-End Slack App Presentations and Sprint Retrospective for Batch 26 happened in Avion School last night!Ĭurrently, creating their very own chat app using the slack api is the final project of the students for FE before diving more on BE! After major presentations, I kinda want to keep simulating the real world.
