Benefits of a growth mindset in developer training

A growth mindset can make or break the success of training a developer, and that’s why we made this concept a pivotal element of our teaching method. Check out the benefits of a growth mindset and learn how it works in action at Codecool.

Codecoolers become skilled and motivated junior developers during our Full-Stack Development course. They’re capable of taking on new knowledge quickly at the workplace and have all the hard and soft skills that make them the best on the market.

But how do they get there in only ten months? A huge component is the growth mindset – this ‘skill’ drives their progress behind the scenes and helps them progress and grow in a way they never thought possible. Let’s see how!

What is the growth mindset concept?

The growth mindset describes a way of thinking about challenges and mistakes.

When you have a growth mindset, you know that encountering a setback doesn’t mean you’re bound to keep having them. It’s just the natural way of progress, and you know that your abilities aren’t set in stone.

We’ve known this since Carol Dweck’s 2014 TED talk.

Just because some people can do something with little to no training, it doesn’t mean that others can’t do it (and sometimes do it even better) with training.

Carol Dweck Tweet

The importance of a growth mindset in education

Having a fixed or growth mindset can make or break the success of the training one takes part in.

Why?

Because cultivating a growth mindset during training leads students to understand that their potential depends on their work. It’s not due to talent they should’ve been born with or any other outside factor. Once believing this, students begin to thrive and progress in a way they never thought they could.

Carol Dweck researched this theory for 30 years. According to her research, children tend to have an inherent growth mindset about their potential. On the other hand, adults are already conditioned to a fixed mindset regarding their own and others’ capabilities in many topics, which limits their ability to progress.

What is a fixed mindset?

We all have a fixed mindset about certain things, our own capabilities above all.

We tend to think that our skills are rooted in talent and shaped by circumstances. That our understanding or skills cannot really be improved. And this can limit progress in many areas of life.

Writing code is a perfect example of that. People tend to think they won’t be able to code because they’re not good with math or they’re not the naturally ‘techy’ type. They don’t see how with the proper mindset and the right methodology they could improve their understanding.

The relevance of a growth mindset for organizations

The ever-growing IT talent gap slows down digitalization and many businesses. So there’s a global need to train new tech professionals and to re-skill employees. But many organizations still have a massive wall between tech and non-tech people. And at the same time, there seems to be no concrete plan to make it possible for people to climb it.

We at Codecool believe tech training is best done by cultivating a growth mindset and celebrating initial mistakes. People sometimes make mistakes when they make an effort and dare to step out of their comfort zone. But that’s when they gain valuable experience and progress, so it shouldn’t be a thing to fear.

We’re building on a growth mindset to make the talent gap a thing of the past and enable digitalization. But what does growth mindset look like in action at Codecool?

Let’s dive in.

Growth mindset in action at Codecool

Our business model builds on a growth mindset and it proved to be a winning bet. We break down walls between tech and non-tech talents and help people, even without any relevant background become the best junior tech professionals on the market.

1. We focus on the beginning

During the application process, instead of looking at degrees, tech experience or achievements, we explore our applicants’ goals, drives and peculiar aspects of their personal profiles. We check their logical thinking and English skills, but no further hard skills. Our case studies prove that having certain soft skills provide a better indication of our student’s future success.

2. They get the big picture right away  

Instead of keeping knowledge to ourselves, we let our students in on the bigger picture behind our approach. During the first few days we present them the growth mindset theory, share our implementation plan and point out their place in the bigger scheme. They understand that becoming a tech talent is their own path, they are the driving force behind this decision. If they put in the work, they’ll succeed.

3. We put our signature on their success

Our method is effective, and our belief in our student’s success is rock-solid. So solid that we’re contractually bound to get them hired if they take our job guarantee. If we can’t do that in six months after they graduate from our 10-month Full-Stack Development course, their tuition fee is on us. So far, 98% of our graduated students have found a job with our help, and 100% work in new tech jobs after our course.

4. They work in agile teams in a workplace simulation

Codecoolers work a lot individually, as well as in agile projects groups during the course. They gain experience with the agile way of working and learn a lot from each other. This way, they organically develop a ton of new skills. Not to mention, they become great team players with solid soft skills.

5. We encourage a failure culture

We encourage our students to make attempts and fail. This way they learn to take alternative approaches to problems, develop an analytical attitude, understand that failure is inevitable, get used to collecting themselves mentally afterward and fail less later, in workplace situations with higher stakes.

6. They get challenging but achievable goals 

The tasks our students get are carefully developed to match the actual level of their skills and confidence during the course. Mentors and peers are there to help, and resources are provided. But we make sure not to give out final answers, and instead encourage them to find their own unique solutions to challenges.

7. They take test results as a snapshot, not a judgement

Frequent evaluation of progress helps our students see where they are in a process and what they still need to work on. We try to make sure test and exam results are not taken as a verdict. Instead, we help them understand where they stand in the process and strive to keep up their motivation.

The result of a growth mindset in training

What’s the result of all the above-listed elements?

Well, Codecoolers …

… become great team players. They are good communicators and can share their responsibilities and successes with their colleagues. They take ownership of challenges and support the development of others.

… can get things done. They are capable of solving challenges quickly and efficiently and are okay with trying different options until they succeed.

… quick learners. They understand the direct impact hard work has on their own development, can take on new knowledge quickly, and like raising the bar for themselves.

Looking for talented tech professionals?

If you’re looking for your next developer, consider partnering with Codecool. We have an active network of quality tech pros and flexible recruitment processes, offering you quick access to top talents.

Growing your teams? We can help you find your next junior who could be in your team in just a couple of days after you contact us. 

Don’t want to let your best colleagues go? We offer up-skilling or re-skilling services too. We’re happy to tailor our flexible training programs to your exact needs, and turn them into your most valuable and skilled digital resources.

In case you have any questions, reach out to us! You can also visit one of our Demo Days on any Friday, online or in person, to check out the skills and capabilities of our students if you’re interested.

Hope to talk to you soon.

The Codecool Way: 4 Core Values we Follow to Disrupt Tech Education

Company values are important: they can define a company and its brand, help communicate corporate identity and keep everyone aligned with the agreed strategic directions. If done well, they have a direct impact on core activities, shaping the way everyday work is being done at the company.

We at Codecool have been trying to follow 4 simple values for years in our everyday work:

  1. Courage – to explore new things and push limits.
  2. Transparency – sharing information and expressing ourselves, not just when comfortable.
  3. Quality – in whatever we do.
  4. Fun – to also enjoy what you do, so that you become even better at it.

But words are just words. They may sound cool, and we may check out an invisible to do list with them as any serious organisation that should have a list of core values does. But if there is no action behind them, they mean nothing.

So the tricky part about values is not even defining them  – especially that you better define them based on what you really believe in and what you actually do. It’s much more challenging to be always true to our values. How to apply them in different situations, with everyone and at all times. Even when it would be faster, cheaper or simpler to just not bother.

We follow our values in internal processes and ceremonies, among ourselves “in the background”, the way we talk to each other and do our daily work. We follow them when we meet external parties, like our business partners, and they experience them first hand, too, when they welcome graduate Codecoolers in their organisations.  And that’s because we also follow these values when we work together with our students, in the way we facilitate their learning and help them restart their lives in brand new tech careers.

But how exactly do we apply our core values in our training and make them work for everyone impacted?

Let’s dive in.

1. Courage: We step out of our comfort zones

Having courage to explore new things and break conventions is very attractive, but failing can be scary. So pursuing new challenges comes with a price: if we want to stay true to ourselves, we can’t always go the safe way.

You can’t have innovation or deep learning without trying new things. And trying new things naturally comes with failing a few times first. On the upside: the earlier you fail, the earlier you can fix what went wrong, and with the smallest cost possible. 

So we encourage learning by doing and learning from mistakes. We appreciate each failure together. We always give feedback and do a positive reinforcement on failures, as they are a valuable part of the process. For example: “It’s great, that you tried this option and found out that it doesn’t work. What have you learned from this?” 

To achieve innovation and learning via natural failure, we focus on processes rather than outcomes. We aim to create a supportive, fail-safe environment, where real growth can happen, so we also focus our feedback on behaviour, not on personality traits.

For a start, our mentors (we call our trainers ‘mentors’) cultivate a growth mindset. This means that we make sure our students understand and fully believe that with a growth mindset, their skills and abilities can be developed through dedication and hard work. Not by talent, luck, good grades from high school, or an IQ test’s result from last year. It depends on how much they believe they are capable of learning to code. This view creates a love of learning and a resilience that is essential for great accomplishments. To achieve this, we rephrase “fixed mindset” statements. For example, instead of saying “I’m not good in solving math problems” we suggest: “You might not have found your way in solving this math problem, yet. But have you tried … ?”

Learning new things can be intimidating, too. Once in a growth mindset, we finally dare ourselves to move out of our comfort zones to change and to grow. When defining challenges for our students, we concentrate on the “learning zone“, or the Zone of Proximal Development. The learning zone is between the comfort zone and the panic zone – neither of which is a place for learning. In the comfort zone there is nothing new, but in the panic zone there’s way too much. In the learning zone, however, you have the right amount of challenges to tackle. The Zone of Proximal Development inside the learning zone is where the learner gradually moves from learning the first steps with support (of a mentor or peers) towards learning further steps without help (or without ‘scaffolding’).

During the learning process, we make sure to always go step-by-step (sometimes in baby steps). We start routinely questioning ourselves, our beliefs and ways. We turn old stones, reinvent the wheel, understand how and why things work or don’t work, and then most of the time come up with ‘lousy’ new ideas – or at times, with truly ingenious ones. And in the meantime: we analyse, we open our minds, understand how to tackle problems, grow our confidence and learn. We grow – and have a lot of fun in the process.

Besides all this, we do follow-ups and retrospectives regularly. Our mentors also take the courage to face any feedback from our learners, and admit if anything went sideways – then, they focus on these areas of improvement, and turn the feedback into learning opportunities.

 

2. Transparency: We share and express

Transparency for us means more than just being honest. It means telling the truth at all times and sharing as much information as possible for everyone’s benefit – also with the learners during the learning process.

To support transparent communication, we first establish psychological safety, an atmosphere that facilitates mutual trust and growth.  In a team with high psychological safety, teammates feel safe to take risks around their team members. They feel confident that no one on the team will embarrass or punish anyone for admitting a mistake, asking a question or offering a new idea.

To achieve this we:

  • strive to recognise our own tensions and notice tension in others, that distracts us from being present or feeling comfortable, 
  • communicate tensions in a way that doesn’t hurt others,
  • give a context or a greater perspective about a decision or a behaviour to further enhance involvement and trust,
  • organise ceremonies (sharing/syncing) outside our daily work for bringing up questions or information transparently about things experienced in various situations.

We basically set a good example by communicating transparently, also to encourage others to start communicating transparently, too.

We can use this principle in the following situations:

  1. We give upfront information about the trainings, workshops, etc. We don’t hide any useful information from learners. We tell everyone what will happen, when, how.
  2. We clarify rules, roles and expectations. Then we have a ground to say “no” to learners, if they ask something beyond our agreement.
  3. We consciously avoid having secrets or taboos. What, how and why the mentor/trainer does what she does? It has to be clear for everybody. For example “Why are we doing this exercise?” We give context to the learners – with careful timing of the information, so it helps their learning.
  4. We do regular mappings. We map out our day, the next hour, exercise and even the whole course for everyone in advance. Learners always have to understand the process and where they are in it.
  5. We express our feelings. When our mentor has any tension, they also express it freely. The mentor is not perfect, either, they are a human being with feelings, emotions. For example when learners don’t pay attention, the mentor expresses their feelings about the situation and then asks them to pay more attention.

3. Quality: We put extra work in providing real value

We pursue quality and craftsmanship in everything we do or expect from our students or partners.

For a start, we significantly increase quality of learning outcomes by maximising learning time efficiency through guidance, support and motivation provided by our pro mentors. As opposed to self-paced learning, instructor-led course students are much more likely to finish their studies, and to end up with usable, practical knowledge and skills they can actually implement later in a work environment. They also have much more fun.

One way Codecool mentors engage students and partners for even better result is empowerment. As a start, we define quality together and how exactly we’ll get there.

We follow the principles of subsidiarity – which may sound complicated, but it only means that we tackle problems on the lowest level where information is available to solve them. Meaning that if there is a solution available for the students already for a certain problem, based on their previous project experience, then their mentor will encourage them to find the solution themselves and will not hand it over to them.

Solution focus is a technique we borrowed from Solution-Focused Brief Therapy. It requires future-based thinking and resource consciousness and builds on the notion that “the solution doesn’t care about the problem”. Instead of analysing the problem, we analyse the preferred outcome together with available resources, and derive the possible ways to get there from “top down”, rolling it out backwards from the desired state of final outcome.

The agile methodology is a no-brainer go-to toolset to use in software development context, and we use it extensively, too. We actually go as far as to build our learning schedules around agile ceremonies, and have our students demo their projects in front of real-life “clients”, represented by our hiring partner companies every Friday, from week 1 in their learning journey.

We also believe in efficient, goal-focused meetings and learning sessions. We respect each other’s time, arrive on time and keep timeframes at all times – but that’s only one side of the story. 

We start every meeting with a check-in round where we discuss how everyone feels, so that we can “arrive”, that is put outside problems behind by acknowledging them and sync the mood of the team. This may sound like an overkill or waste of time, but skipping it is just not worth the 10 minutes it saves. People tend to focus and participate more actively and efficiently after this short routine, and the time saved indirectly is a lot more than how long the whole thing takes.

We also do a check-out in the end, to share how we feel then and if there’s anything more to share, to make sure we maxed out our time spent in the meeting together.

Apart from these generic meeting routines, we also do short attendance meetings each and every morning with our students.  At this meeting everyone (including mentors) answers one simple, casual random question generated by a bot (like what’s the one TV show that always makes you laugh, or who is you favourite superhero and why). We don’t react to replies, we just share and listen. The purpose is to kick-off the day on a positive tone and consciously bring in the human element into our work and learning every day, which is also a key tool for building a teal organisation with high standards for quality.

And last, but not least, we build on the 4 principles of doing by non-doing, which in our case is basically a coaching attitude pursued by mentors. The principles are the following:

  1. We don’t know the one single truth: The mentor/trainer doesn’t know the truth, only shares knowledge by her experience. Everyone can challenge the mentor’s or others’ thoughts, ask open questions and start a constructive debate.
  2. We don’t judge: We give specific feedback on behaviours, and we don’t apply labels to people.
  3. We don’t take over responsibility from others, especially from learners: The one who is working hard is actually learning by doing. If the mentor/trainer works hard, it means they learn a lot themselves, but not necessarily the learners. For example that’s why the mentor cannot touch the keyboard of a learner as a rule. We also say: learners should spend most of their time practicing, communicating, elaborating on a task. The main responsibility of the mentor/trainer is to facilitate learning, but the ownership is with the student – they own their own learning, for the best possible result. 
  4. We don’t give solutions: We don’t tell the tricks and give final answers. The learning process is more important than the final answer. Our approach is coaching – we help the learners with questions, guidance, motivation.

Some people intuitively interpret ‘non-doing’ as something passive, laid back or lazy. But if no action is needed, then doing anything may already be ‘overdoing’. In fact, sometimes action can do more harm than good.

If we are growing a plant and we have created the right conditions for growth with healthy soil, sun and water, there comes a time when the very best way to ensure the growth of the plant is simply to leave it alone. More water, more sun, more fertiliser won’t help, in fact, too much of any of these may stifle the growth of the plant. We remain attentive, connected to the plant’s needs but for the time being, doing nothing is just what is needed. 

We do our best not to kill our plants, but let them grow and reach their highest quality.


4. Fun: We make sure everyone enjoys the ride

Choosing Codecool is a life-altering choice for both our day-time course students and our colleagues – so we always put fun high on the list of priorities. If you enjoy something, you’ll become better at it. It’s that simple.

We do believe that learning and work can and should be a fun, light-hearted, and possibly a flow experience, too. We don’t take ourselves very seriously either. We make sure to be able to laugh at ourselves as much as possible.

Our students learn technologies and new skills via life-like, but still playful and fun project assignments, instead of boring, heavy textbooks and frontal lectures.  

A fun learning experience will bring a better end result because of the positive association:

  1. We experience how we all (including the mentor) are just human beings. We all make mistakes, and we laugh at ourselves, together.
  2. We focus on the journey, the experiment of learning something new. This adventure, the discovery can be very enjoyable, genuine fun.
  3. We share interesting small details, fun facts, all related to the topic.
  4. We do more interactive, practice-oriented sessions, and fewer frontal sessions and presentations. Learners will remember the “experience” most: when they were moving, talking, practicing, laughing, etc.


That’s basically it – and of course a lot more. But listing all the ‘secret’ ingredients of our learning method and routines is just not possible in one article. 

We know that every company is different, and your values at your company must be different, too – not better, nor worse, just different. Hope you found this insight to the Codecool values and our ways of working with them inspiring, and that we made you think about yours. 

What core values do you have at your company? What do you do to follow them every day?

Stop and think about them sometime, and find more creative ways to be true to them. It will be well worth your time.

Coding a Better Future – Codecoolers Win Silver at Morgan Stanley’s Hackathon

A team of Codecoolers developed an innovative learning support app, that might change the lives of children with a chronic desease.

Morgan Stanley and the Amigos for Children Foundation asked young developers to help non-profits building innovative learning tools for children and teenagers with chronic diseases, in the scope of a three-month virtual competition.

We’re super proud that the Codecooler team – Zsofia Szonja Kassai, Barnabas Urmossy, Balint Molnar and Kristof Murai – came 2nd place in the Hungarian competition, in an all-university team lineup.

We asked them about their experience at the hackaton and their studies at Codecool.

What motivated you to sign up for the Code to Give hackathon in the first place? Was this your first hackathon?

Zsofi: Yes, this was our first! We were curious about the challenge, we wanted to try ourselves and learn from a longer project. The idea that we might help a nonprofit was very attractive, too.

Barnabas: I wanted to know what it would be like to work together with a client on a project which is much longer than the usual 1-2 projects we are used to. Plus, I knew that we’re a really good team, and wanted to see us as a team develop, besides individual development.

Balint: For me, it was a no-brainer. I’ve never participated in anything similar, and I loved the concept that we can help kids learn languages, sponsored by a huge multinational company.

Kristof: I was also driven by curiosity in the first place. I had no idea what to expect. I wanted to see what we can do being in the 2nd part of our one-year full-stack development training. The idea that we can help kids in need was obviously a huge plus.

You named your team LazyLlamas. Where did this crazy name come from? 🙂

Barnabas: We realised that we shared an interest about llamas at our very first meeting. Then we just sat back like we had nothing else to do until we sign up. We added the “lazy” when we realised that we have just 15 minutes left until the deadline and we still haven’t registered the team in the competition, which was so us, actually.

But it felt good when people mentioned a few times, later, during the competition that based on the way we work we must have meant “lazy” as irony.

What kind of learning support tool have you developed? Can we see it?

Zsofi: Our app has 2 parts, one for students and one for teachers. The part for students is a learning enhancing tool with 6 types of tasks. The part for teacher, or the “Amigos” makes it easy to create tasks, monitor students’ progress and give feedback.

Barnabas: The basic idea was to create an app with templates that help creation of new tasks. And we also wanted to support the communication between the students and the Amigos, so that they can align on tasks and evaluation. On top of this, we wanted to create a gamified system for collecting points to enhance students’ motivation.

Balint: The biggest benefit of the app, just like Barna mentioned, are the templates. We created templates for memory game, word – image coupling, interpretation of written and spoken text, substitution and organisation into categories. We made all of them available on all the languages the Amigos work with.

Kristof: We’re very happy to demo the app to anyone who finds it interesting.

What was it like to participate? How did it feel to get in the finals?

Zsofi: For me it was an amazing experience! We spent the whole time sleeping much less, collecting creative ideas all the time, working together really smoothly as a team. Our original goal was to learn, but we’re so happy we got this far in our first hackaton. And it was super exciting to present our idea to the jury in the finals.

Barnabas: On top of what we have expected, the whole thing required a lot of organisation, project management, copywriting and presentation rehearsals. I really enjoyed being able to practise all this in a real-life development environment. And the experience helped me decide that I want to be a front-end developer after Codecool. Plus, getting into the final showed that we were capable of performing well in such a complex project, even before finishing course.

Balint: The competition was a blast and I was especially happy that I could refresh my web skills, plus learn CSS at the same time. I was really curious how we’ll perform among the university teams, but after the meetings of round2 it was obvious that we’d make it to the finals.

Kristof: I just loved everything about the competition. It was great to see what it takes to organise and put together an app from scratch. We started out super motivated and the ideas just kept coming to us. Then, after we successfully presented our ideas, our motivation got another  boost, and then we just had to fight time to actually deliver on our idea. Getting into the finals felt like a dream come true, and assured us that we did a good job.

What was the biggest challenge in the competition?

Zsofi: Racing with time. We had so many ideas, but it was almost impossible to deliver on them in such short time.

Barnabas: In the last days I found it really difficult to let go of some of our ideas and my maximalism, just like Zsofi. We had to decide what to implement in the prototype and what to put on the next steps slide in the final presentation.

Balint: For me it was CSS! 😀 And as the project kept growing, refactoring. It was really challenging to create and put each task type together, but the end result turned out very organised, thanks to Zsofi.

Kristof: For me, too, the biggest challenge was time, because we just kept getting newer ideas about how to make each task type even better and fancier. We had to draw the line somewhere eventually.

What skills could you use in the competition that you got at Codecool?

Zsofi: Like everything. 🙂

Barnabas: There were 1 or 2 technical solutions that were so specific that we haven’t seen anything similar during the course. But since we also learnt at Codecool how to find new solutions on the internet, we managed to find and apply those, too.

Balint: We had a huge advantage in the finals because we pracised so much already at the Friday demoes in front of clients at Codecool. As for hard skills, for me the hackaton was like “and add-on” to the web modul of the full-stack course. Our app turned out a Flask based, JavaScript-heavy website, with a complex database structure.

Kristof: I got all my coding and developing skills from Codecool, so I used what I learnt there. And when I got stuck, I could always turn to a Codecool mentor for help.

Where are you now in your Codecool studies? What are you learning about now?

Zsofi: We’re at the end of the OOP (Object-Oriented Programming) module, which is the 3rd or the 4 modules of the one-year full-stack development course. We signed up for the hackathon at the beginning of this module.

Barnabas: Yeah, the competition lasted the whole time of the module. Let me take the opportunity to send our thanks to our teammates who put extra effort into our shared Codecool projects, so we could focus on this challenge. 🙂

Balint: It was refreshing to work on something totally different while also coding in Java (but obviously the last weeks of OOP were also about web based stuff, databases and such). I’m actually just about to start my last module, I’ll specialise in Test Automation.

What are your plans for after Codecool?

Barnabas: I will start looking at web app front-end developer jobs with real confidence after this competition.

Balint: Precision planning is far from me, I have always been going with the flow. I’m curios about the Test Automation specialisation at the moment.

Kristof: I liked the web modul best so far and especially after this result I’m looking forward to become a web developer, too.

What will you do with with your prize? You’ve got some EMAG vouchers.

Zsofi: I haven’t decided yet. I want to make good use of it.

Balint: I killed my laptop a few months ago, so I got a new one from my prize.

Kristof: I have always wanted a smart watch, but I’ve never came around investing in it. Now I have.

What is the biggest learning for you from the competition? Is there anything your would do differently in retrospect? Would you ever enter a hackathon again?

Zsofi: The biggest learning for me, how much I actually learnt during the ride. I’m satisfied with our performance and would definitely go for another hackathon, too, sometime.

Barnabas: In the beginning I haven’t even realised how big of a task we took on. It even started to get a little scary after a while. But seeing that we can do all this, I started to come up with new ideas and challenges in the last days. I would definitely do something like this again.

Balint: i would do a lot of things differently, for example I would stick to naming conventions form the very beginning, and make SCRUM standups regular. But we all did our best, and I would definitely do this again.

Kristof: Since this was my first hackathon, I would do many things differently. But it was an amazing experience and I would definitely be up for the challenge again.

Inspired by this success story? Want to work with juniors like these amazing Codecoolers?

Our fresh graduates are waiting. Reach out and let’s discuss how we can help you.

We can’t wait to talk to you!

Telekom offers discount subscription for Codecool students

Codecool students in Hungary may use Telekom’s postpaid 15GB mobile Internet package together with the “Mobil XS“ tariff plan free of charge in the first two months and for a fee reduced by 30% for further 10 months. As a result of the cooperation between the programing school and the telecommunication service provider, more and more people can acquire marketable developing skills.

Telekom Hungary and Codecool Programming School have concluded a cooperation agreement. Under this agreement, all active or newly enrolled students of Codecool are now entitled to receive significant discount off the monthly fee of Telekom’s 15GB mobile internet package (offered together with Mobil XS tariff plan) for two years. The offer applies not only to the new 15GB mobile internet package, but also to the 10GB one contracted earlier, until the end of September. Telekom provides this construction for its clients participating in the trainings of Codecool in Hungary for a residential monthly fee reduced by 100% in the first two months and by 30% for further 10 months.

“Owing to the introduction of our short-term IT trainings, accessibility to our courses has improved significantly for the past few months, since our trainings have become available not only for people living in the capital or in Miskolc, but anywhere in the county or even outside of it. The agreement concluded with Telekom Hungary is also part of our endeavors to widen the accessibility of our courses. In addition to the benefits of the discount mobile internet package, we provide job guarantee and the possibility of post-financing for our full-stack programming course students, while the participants of our short-term trainings can pay their tuition fee in instalments, as well,” says Codecool co-founder and CEO József Boda.
The entitlement to the discount can be validated by presenting a document certifying participation in our course, issued by Codecool, in any Telekom shop. Within the framework of this special offer, one student may use only one discount package.

“Telekom Hungary is committed to the improvement of Hungarian digital economy and society. Digitalisation changes the usual routines and processes in every economic sector and in most fields of our everyday life; this change is inevitable, and, at the same time, it has become one of the most important competitive factors,” says Chief Commercial Officer of Telekom Hungary Melinda Szabó, referring to the agreement. “Our company has contributed to the major successes of the past few years not only through the intensive development of our network, but we also keep supporting digital education and the training of IT professionals through various programs and initiatives. Codecool’s digital IT training perfectly matches Magyar Telekom’s strategic programs, that is the reason why we support the students of Codecool by providing discount mobile internet service for them.”

Codecool expects that most of its students will take the opportunity to use this discount package, as having a reliable and fast internet connection is indispensable for the completion of the trainings. Mobile accessibility to the internet increases flexibility even more.