Categories
About us Featured Podcast Interviews

Two Months into My First Software Developer Job

Olena Drugalya recently went from being a stay-at-home mom to landing her first software developer job, joining Novatec Consulting as a junior software engineer. Two months into the role, she chats with us about her beginnings, first learnings, and what other people starting their web developer career should expect from the first weeks at the job.

🔊 Subscribe to the podcast


Congrats on first software developer job? What projects have you been working on so far?

I’m actually not working on any client-facing projects right now because I’m still in the learning phase. Novatec has a Talent Hub, and every new employee in the software engineering department starts there. We spend a lot of time learning, as the project we will be involved in later require a lot of additional skills and knowledge of languages and frameworks. So, they want to be sure that we know all these things in advance.

What’s the talent hub like?

There are a lot of new developers in the hub: juniors, trainees, students… And we work together on pretty much the same program. We learn back-end, Java, Kotlin and some frameworks, but we also learn front-end tools and frameworks. Then, in the end, we are given a project to do by ourselves, and we present it and show everything that we have learned so far.

Some need two months to complete the program, others need more time. It really depends on the person, but it usually takes no more than six months. We need to deeply understand the concepts and processes, so we can use as much time as we need to learn. They don’t rush us. I really love Novatec’s idea of the talent hub.

Pretty cool, isn’t it? Sounds like a great way to get started.

Yes. I was so happy when they took me in. This was something I was looking for because I don’t have that much experience and they give us the possibility to learn and cooperate with other developers and see what the process of development is really like.

We participate in all the company meetings, as well as in sprints and refinements. So, from the first day, we can see what the other developers are doing and how they manage the development process. We are not taking part in it yet, but we are already aware of what the project looks like from the inside and how people are working on it, and this is a very valuable experience.

What are you finding to be the most challenging part of this learning process?

The most challenging for me probably has been working on a project inside a team. Before this, I was doing everything by myself. So, if I had a project to get done, it was just me doing all the thinking, projecting via framing and coding. Now it’s just a bit different situation.

You have other developers in your team, and the planning of the project takes more time than the coding part itself. That’s because it needs to be divided into small parts, and everyone in your team needs to understand what their task is and what they’re going to do.

And I bet you learned many things as a result.

Yes. I learned how to develop the user story, how to create a ticket, how to cooperate with other developers using GitLab and all these things which I would have never learned by, for example, being a freelancer.

You mentioned you’re learning back-end, and your previous training was in front-end tech. How is going full-stack like?

I was lucky because was able to handle the back-end pretty well because I had some experience with C#. So, Java was not that difficult for me, but still, it took me probably a month to dive deeper into it, to go beyond the basics and learn new stuff. Then it became easier when I started with Kotlin and the various back-end frameworks. The most challenging part was Java itself.

Connect by Mindquest Newsletter

How was the experience of going through the onboarding process? Was there something in particular that positively surprised you?

I was really surprised with it all, as that the onboarding process was really well organised. Everything was on time and there were so many people presented their teams and projects. They were telling us with enthusiasm and happiness, explaining how they were handling things and that they were happy to see us at the company. That was very inspiring and surprising in a positive way.

What advice would you give to others just starting with their web developer career?

For the junior developers who are just starting their web developer career, I think the most valuable advice I could give is: don’t be afraid to ask questions. Everything you want to know, everything you are not sure about, just ask. There are a lot of people who will help you, who will guide you and mentor you.  

In a good software engineering team, they all want you to succeed. That’s the beauty of cooperation. Everyone helps each other out when they are working on a joint project.

Join our community and find your next job or expert in IT

What about work-life balance? Starting a new job can be stressful. How are you doing with it all? Are you working from home, or at the office?

Work-life balance is pretty much on schedule and going well. We’re still working from home remotely, but we can go into the office if we feel like we want to socialize with other colleagues. So, from time to time, we meet at the office. I do like work from home, as that way I don’t have to spend that much time in traffic to go to the office and back.

You were blogging quite a lot before starting your first job as a software developer. How is blogging given how busy you must be? Are your new experiences prompting you to write about new topics?

Yes, it’s difficult now with the content. I know there are a lot of people on Twitter who juggle their work with content creating, family and everything, but it was difficult for me these first two months. It being a new job, and my first software developer job, I wanted to get to know everything, to learn as much as possible. And that didn’t leave too much time for content creation.

So, my blog is still where it was before, but still coming up with ideas. At Novatec we also have the possibility to write blogs, so I will probably think about that as well. I would like to pick up blogging again soon and write about all the new back-end tech I am learning to use, about Java and Kotlin – there are so many topics waiting to be written about.


Check out more of our interviews from our podcast episodes.


For more guidance in your web developer career, make sure to follow Olena on Twitter and LinkedIn and don’t forget to check out her blog and Hashnode activity.

Need more tips on how to find a job in IT? Check out our IT job hunting guide.

Categories
About us Featured Growing your career: permanent & freelance IT Consultants Podcast Interviews

A Career in Data Science: Unlocking The Power of Data with AI

We chat with Ton Badal, machine learning engineer at London-based DataOps start-up Synthesized; about pursuing a career in data science and the challenges of working with data.


🔊 Subscribe to the podcast

Check out more of our interviews from our podcast episodes.


How did you get started in tech, what made you go for data science career and machine learning in particular?

Since school, I have had an engineering mentality, I’ve always had this problem-solving way of thinking. I’ve always enjoyed math and solving problems. In university, I studied telecommunications engineering and specialised in audiovisual systems, so the processing of audio, images, video and other audiovisual systems from a technical perspective.

There I started doing research in machine learning, AI and data science. I started discovering this super interesting world. After that, I was sure that I wanted to do a data science career. So I went for a master’s in AI. And that’s how I discovered this very, very interesting and challenging world.

What did you find to be the most challenging part of this process of learning data science as career and becoming a machine learning engineer?

When I started university, it was not a clear path yet. Eighteen or fifteen years ago, you couldn’t see the path of a data scientist from start to end. Data science sits between computer science and math. And, throughout my career, I’ve been closer to computer science than to math. But the challenge is that you have to know as much as possible from both worlds. But at the same time combine them as well as possible. So I think it’s been quite challenging to be able to unify both worlds.

What’s the best career advice you have ever been given?

This is not really a piece of advice that someone has given me, but rather something that I’ve seen people do. I’ve realised that, when I was starting to look for jobs and was looking for a career, I was kind of looking for anything. I felt like I was the only one selling myself. But at some point, you realise that it’s important that the company also sells itself to you. The company also has to be interested in the person who’s applying. It’s not just top-down, but also bottom-up. There has to be this mutual understanding. When I started looking for jobs, I didn’t care that much about that. But after a while, I realised that it’s really important to feel confident and be in a good environment. It’s crucial for your career development and for example a data science career.

So, I would recommend to everyone to not just get the first job and be very selective about what they want and what they seek to accomplish. Also, the people who interview you: you have to look at them and ask as many questions as you can about the company. It’s not only about selling yourself, but also about understanding the company and making sure that the step you’re going to take is the best one for you because that’s going to influence the rest of your career.

CV Writing Tips for IT Professionals

What’s your advice for those who want to learn data science?

If you want to learn something, the best way to learn it is to get hands-on, to find a project that you’re interested in. There are a lot of open source projects that require some help. For example, at Synthesized, we’re now going to open source a fairness package. If you’re interested in this field, you can collaborate on many, many different projects. The best way to learn computer science and data science is to get a project, get a data set. Sign up for a Kaggle Competition, for example, and try to solve it and get as close as you can to the top of the ranking.

Need tips on how to find a job in IT? Check out our IT job hunting guide.

What are the biggest issues with working with data these days?

First of all, there is the problem of ending up with a poor signal-to-noise ratio. The amount of data that you can find nowadays is huge. But, many times, this data contains a lot of noise. And, if you are not careful, you are just going to end up with just a lot of noise that renders it useless. 

The second big issue is compliance, so GDPR, HIPAA, etc. If you have data that is not privacy-compliant or that is discriminating against some groups, that’s going to be not only useless, but it’s also going to be illegal to use. So you need to work closely with compliance teams. You need to spend time with the legal team to make sure that you make proper use of your data. 

Finally, there’s the problem of data sets becoming data silos. More and more, to access data, you need a data engineer, a data scientist or a machine learning engineer — someone who can do the magic with the data. It’s getting more and more complex to access the data because doing so requires the knowledge of a data engineer or a test engineer. 

How is Synthesized helping to solve these problems?

Synthesized has a core engine that is able to solve these problems by enabling users to easily access their data products in many different ways. So, for example, let’s take one of the problems that I was mentioning before: working with compliance and privacy. Our engine is able to generate data that is representative of the original data but is free from privacy issues and from even biases. 

Connect by Mindquest Newsletter

Another of the problems is related to infrastructure, to data silos. Current approaches are data warehouses and data lakes. There are some problems with these approaches, for example, the signal-to-noise ratio in the case of data lakes. There’s a lot of data in there, but it’s very difficult to use. But, the infrastructure problem is also there because the data is very centralised and you need a data engineering team to get to it. So what we’re working on is a new infrastructure called data mesh that aims to decentralise data access. It tries to decentralise all these data products so that each team can access the data independently. Both for internal and for external collaboration.

Can you tell us a bit more about your role at the company?

I’m very lucky to have been a very early employee of the company. I joined at a very early stage, and this meant that, although my official title is machine learning engineer, I’ve been able to touch a bit of everything. 

However, my main role as a machine learning engineer is making sure that the core technology is as good as possible. But that also involves a lot of what a pre-sales person would do. So, going to the clients, asking them for requirements, and making sure that the product works well for them and is as tailored as possible to their requirements. But about also improving the product. 

And there is also some marketing work involved, like developer relationships. We need to push into that direction because we’re a small company with very new technology and we need to make sure that we sell bottom-up, not top-to-bottom. We approach customers as machine learning engineers, as the nerds who sell to other developers, not as the marketing guys who are trying to sell something to them. Otherwise,+j the message doesn’t get through that well.

What’s next for data? Where do you see data science in, let’s say, five years from now?

I think that, right now, we’re in a very crucial moment for data. We are having all these privacy issues, fairness problems, and the users are more and more aware of this. So, we have to make sure that we have the best practices in place, that we make the best that we can with our data but still respect users. It’s going to be a very challenging time. 

At Synthesize, we mainly work with structured data, but I think it’s worth mentioning unstructured data. What’s happening with OpenAI, GPT-3 or other generative models — what’s being done is amazing. It’s a very exciting time. I’m very, very excited to see what the next new thing is going to be.

You’ve been based in London for a while. What do you like the most about the London tech scene?

What I like the most about it is that there are a lot of people working on the same topic, and you can very easily meet people doing really interesting things. And that’s one of the most powerful things when you are doing research or trying to improve your product. Just talking to people, understanding their problems and just having a conversation about something that probably you don’t understand and you don’t even know about. 

Discussing new tech trends with people at other companies, that can really help. You discover new things and go out of your usual boundaries. London is great for that because there are a lot of meetups. Well, there were before corona. But yeah, you can talk to and meet a lot of people. There’s this big ecosystem where a lot of things are happening and there’s so much to learn. I’m really happy to be living here.


Join our community and find your next job or expert in IT


You can follow Ton on LinkedIn and on Twitter.

Looking for a job in IT? Check out our IT job hunting guide.

Categories
About us Featured IT Consultants Podcast Interviews Tips for your daily life as a freelancer

How To Code Well: Taking Breaks and Other Pieces of Timeless Career Advice

Peter Fisher; freelance web developer and host of the popular “How To Code Well” podcast; discusses why he started teaching coding and some of the best career advice he has given.

🔊 Subscribe to the podcast


How to code well

How did you get into web development?

I never actually wanted to be a programmer. I actually started off from an arts background. So I did a lot of graphics design and a lot of 3D animation. We did a lot of flash animation and action script coding, so the coding came alongside the multimedia stuff.

When I was at school, I was building small little websites for myself and friends just to post images on. And I found it interesting that one could build something with really small feedback loops. All you had to do was write some HTML code and refresh the page and you had something.

And then when I got my first job in a web development agency, I discovered very quickly that I wasn’t actually a graphics designer as more of a coder. So, I was able to transfer my passion for design to a passion for designing and architecture.

You are the host and teacher of How To Code Well. A podcast and learning hub around web development and pursuing a web developer career. How did this adventure start?

I never started How To Cope Well with the intention of building a business from it or being a creator. It was a purely accidental thing that I got into. I always started blogging when I started learning because that was my way of keeping note. But I was writing to myself rather than to others.

After I finished university, I was in this ocean of developers who’ve just come out of university, and they were all looking for the same jobs. I was speaking to a lot of recruitment agents, and one of them, off the cuff, said “I wish there was a way I could show our clients how well you can code.” This was like 2006-2007, so YouTube was just coming out. And I thought: “You know, that’s something people is starting to use more, so I will video myself doing some code.” It was a very selfish decision. It was never intended to teach anyone how to code, it was just to show how I coded, so I could have called it How Well I Code rather than How To Code Well.

But then you decided to focus on helping others. What changed?

At first, I did about four videos and posted the links up onto my CV, but I very much doubted that anybody would actually see those videos from a job perspective. So, I forgot about it for a few years and didn’t bother logging back into YouTube.

Then one of my family members wanted to post or share a video for other family members. And I just thought “Oh yeah, I’ve got this YouTube account.” So, I logged in and, after several years of it being dormant, I noticed that there was a ton of comments and questions and feedback which were all very positive. I thought this was something I could run with, and it went from the very selfish decision of promoting myself to helping people out. People on YouTube were asking if I knew how to do other things, how to use other programming languages, where the next part of the course was. The funny thing is that I never thought it was a course when I did it. The driving force of How To Code Well is its community.

What was the most challenging part of starting to produce educational content on a regular basis?

I was a junior dev working a full-time job with freelance work on the side, and I was now teaching people to code, so time was and is a thing that is against me.

I’ve got a very strict rule of not doing it during working hours, so it’s evenings and weekends, and over several years I’ve managed to keep that going. But there’s a lot of sacrifices one has to make. For instance, if I live code on YouTube on Tuesdays after work, my working day is prolonged, and my downtime is shorter. If I live code on Twitch on Sundays, my Sunday afternoons are out of the water. And there’s a lot of preparation that you have to do before you do that. You need to think about what it is that you’re going to code and talk about.

What about impostor syndrome. Do you experience it yourself? How do you address it?

Impostor syndrome is something that is definitely real, and with the podcast that came through accident as well. I started doing long-form content where I was touching upon subjects that I didn’t know much about. It got to a point where I was getting to the limits of my knowledge, and I just decided to bring people on the show to learn from them. It’s always a learning journey, always knowing where my limitations are.

With every course I build, I think that I’ve done the wrong thing, if I’ve said the wrong technical thing. You know, if I’ve pronounced an acronym wrong. You’re constantly doubting yourself. It does get easier because you get used to that feeling and you can have a little word with yourself and say “It’s fine. It’s okay, you can publish it.”

You’ll never truly know how the audience is going to react until you publish it. So, every doubt that you’ve got in your mind is just your doubts. It’s not the doubts of others. I think that’s how I get through it.

Speaking to people on the podcast who know about the subject matter, I do come away feeling like I know nothing. I know what they’ve said because I’ve understood what they said, but it just makes me aware of how little I know of web development, which is another reason why web development is so good, because there is so much to know and so much to learn, it’s endless. You’ll never learn everything.

Join our community and find your next job in IT

In your experience, what makes a good web developer versus a great one?

From a technical standpoint, a good web developer knows the syntax and the processes. But a great developer understands the technical consequences of those processes and decisions, and they can lean upon past experiences.

Connect by Mindquest Newsletter

Also, a great developer is highly professional. They know when to say no and they have justifications of why they’re going to say no. They have testing, they know how long things are going to take, they have some experience behind what they’re doing. They’ve seen it from inception to deployment, and they’ve gone through the whole bug fixing cycle. But really, I think what boils it down is experience. You can’t just learn to be a great developer, you must embrace it and experience it.

Based on what you have seen through your courses, what are most developers struggling with these days?

Not understanding core programming concepts is something that I see a lot, so knowing the framework but not understanding the core principles of the programming language behind that. Learning the concepts of programming is a transferable skill. I’m not just talking about learning JavaScript or learning PHP or Python. It’s learning the operators, the logical flows, learning what a function is versus what a class is. All of those things you can take with you to the next programming language.

What I see a lot is people diving into frameworks and then getting stuck when they move to another position or another job, or when that framework changes. They are comfortable in that world, but they’re not comfortable in the world outside of that framework.

What’s the best web developer career advice you have given?

First of all

Take breaks. Take more breaks than you think you need to. Your brain works offline, so even if you’re not physically at your machine, you’re thinking about the work. I think about the work when I wake up and when I go to bed. I never switch off in terms of thinking about the bugs that I need to fix or the logical flows, but because I’m not staring at a screen, I’m not getting stressed about it. I’m processing this information in my brain in the background. And, when you come back to the code, it’s easier to identify the issue that you are in.

The second one

The second one is to keep asking questions. Web development is super hard and it’s going to get harder. You think you know it now, but, in two years’ time, you’ll know two years’ worth of it, and then you’ll discover another two years that you don’t know. There’s more stuff in web development that I don’t know than there is that I do know, and I’ve been in it for a long, long time. Don’t beat yourself up and if you don’t understand what you’re trying to achieve, then ask someone. And, if you don’t understand what that person is saying, ask someone else, because perhaps that person hasn’t talked about the answer in a way that you can absorb. Maybe you are more of a visual learner. Maybe they can show you on a whiteboard or take you through the process. Throwing acronyms at someone isn’t a very useful thing, is it?

Lastly

Lastly, technology comes and goes. At university, I studied visual basic and action script. Well, action script is for Flash. Flash is never used. And visual basic, I just wouldn’t even know. I did well in that course, but I’ve never used it. What I’m trying to say is that technology comes and goes, and whatever you learn now probably won’t be the thing that you will be learning in 10 years’ time or doing in 10 years’ time. So, what you need to do is accept that and embrace change, but don’t embrace change every five minutes.

And the only thing would add is to just enjoy it. Don’t get too stressed with it all. It’s a very challenging thing, and I find that, the more I get stressed, the more I dislike it. So, once you find that you’re actually getting stressed and frustrated with something, take a breather, take a couple of hours. The code will still be there tomorrow, so take an evening off.


Check out more of our interviews from our podcast episodes.


How To Code Well is a video podcast which is live on YouTube every Thursday at 20:00 BST. The audio version is released every Friday and is a week behind the live show. You can find it on iTunes, Spotify and most other podcast platforms.

You can follow How To Code Well through its website, on YouTube (Live every Tuesday @ 17:30 BST and Thursday @ 20:00 BST for the podcast) and on Twitch (live every Sunday @ 14:30 BST).

Categories
About us Featured Podcast Interviews

How to Grow as a Front-End Developer: Soft Skills and Keeping Things Simple

How does one grow as a front-end developer? We chat with Vasilika Klimova, senior front-end developer at Avaloq and founder of the SkillUp School in Luxembourg, about why soft skills and not over-engineering are key to advancing as a front-end dev and in your web developer carer.


🔊 Subscribe to the podcast


How to grow as a front-end developer

Why did you decide to go into web development? What’s your web developer career story?

Actually, web development wasn’t my first choice at all. I have been playing video games since I was three years old, and, at first, my idea was to become a game developer. I studied C and C++ at university. You can get into this industry through OpenGL and all this stuff but, in Tver, my city of origin in Russia, we didn’t have any jobs for students in this area. So, I found some web development vacancies and decided to try it, and by the fourth year of university I got my first job as a web developer as a Webmaster. So, I started from scratch.  

After working there for several years, I finished my university degree and moved Moscow. Then I had to decide if I wanted to go for back-end or front-end, as before I was full-stack. I was doing server code, business logic, all requests to the servers and database stuff, but also user interface. I did all of it. In Moscow there are bigger companies, and these usually have different web development teams, teams for front-end and teams for back-end. So, at this point I needed to decide: do I go as a back-end PHP developer, or as a JavaScript front-end developer? And I went for front-end because I’m a visual person. I need to see what I’m doing, and, when you work with a server, you usually look at the terminal and you see just code and not a lot of interfaces.

And what came next? You now live in Luxembourg. Why the change? What are you up to these days?

I’m actually in Luxembourg because of my previous job. I was a Front-End Team Lead at Artec 3D, a company that has offices in Moscow, Luxembourg, China and California, doing user interfaces and 3D-related tasks. After five years, I decided to switch and was approached by Avaloq’s HR department. They do banking software; it’s quite common to work in the banking industry in Luxembourg.

Avaloq is a much bigger company, and banking quite a regulated industry. Did you notice any differences as a front-end dev?

So, I went from a 200-people company to a 2,500 thousand one with 30 offices around the world. And some processes are not as fast.

Before, when I needed to ask someone within the company for something, I just went directly to them and asked them. But Avaloq has around 800 people at its main office in Switzerland. If you need some information, there are a lot of different teams, and you really need to investigate. For example, sometimes you are working on a project, and you need to find the people who wrote the code in the first place. And often, the only way to know who did this code is to look at who committed it. Coders and managers change, and the only way to find the author of the code is through the commit.

Join our community and find your next job in IT

And besides your job, you also work on some web projects, do consulting and give private lessons for adults and children. You are also the founder of SkillUp School, a school that teaches technical skills and how to advance your front-end web developer career. Tell us a bit more.

Yes. I started being a teacher and mentor for front-end development in 2015. I taught at schools in Russia, both online and offline. And after I had settled in Luxembourg and finally had some time in my hands, I decided to create SkillUp School, as I hadn’t seen that many schools like this in the country.

What we give to our students is this absolutely modern way of looking at front-end technologies, because as professional front-end developers, we are using them every day. We started in 2019. We don’t have too many students, and our main idea is to be very flexible for our students. People who want to change their career usually already have a job and not that much time to invest in their development. We only have two or three teams per year, so not big groups, and we are very flexible. It helps us take an individual approach to each student, and I often become even friends with them. After the course, I keep helping them grow and with any questions they have.

In your experience, what makes a good vs. a great web developer?

I think I started to think more about this when I became a team leader. Good developers can think from a technical standpoint, but a great developer, in addition to the technical aspect, knows how to take more of a business perspective. The main idea behind our job is to deliver something that makes our clients happy. You need to think about the business requirements, why you have these requirements, if there may be a more efficient way to create a feature that meets them and not overengineer. You need to ask yourself “Why?” several times.

Connect by Mindquest Newsletter

I know some genius developers, but sometimes they end up over-engineering because they want to make something ideal, something perfect. But the business doesn’t need that. You need something now, for this and for that purpose. And you always need to keep timing in mind. If development takes more time, then you can run into problems. It’s more of the developer’s time, which results in more money. Don’t over-engineer. Relax and just keep it simple.

As a senior developer, how can more junior specialists grow as front-end developers?

To work on their soft skills, on how to learn, how to behave, work in teams, etc. If one day you’d like to become a team leader, it’s important to work on your team skills, on how to negotiate with web designers. Often developers have issues with designers because we materialise their design and they are not happy with what we created. You really need to have a grasp of some psychology basics for this.

What do you enjoy doing in your free time?

I like scuba diving. I already have more than 100 dives on my back and am a rescue diver, so I could rescue someone from the water, I hope. It’s so calming and beautiful under the surface. But I don’t have enough money to do it too many times a year. Usually maximum twice per year, unfortunately. Covid-19 has made it particularly hard too.

I also like playing board games and having a nice time with friends. I still play computer and video games sometimes. Not to compete, but it’s just something that helps me relax. I am partial to games with and interesting and breath-taking plot.

Your favourite video game?

Mass Effect, the first and third ones.


Check out more of our interviews from our podcast episodes.


For more tips on how to advance your web developer career, make sure to check Vasilika’s website and follow her on Twitter, GitHub, and LinkedIn.

Categories
About us Featured Podcast Interviews

‘If it’s Useful for You, Then It’s Useful for Someone Else’: DevRel and Creating Content for Web Devs

What’s the secret to creating content for web devs? We continue our chat with Stefan Judis, developer relations lead at Contentful, blogger and front-end expert. Here is why and how he shares what he knows and learns with the community.


🔊 Subscribe to the podcast


Creating content for web devs

After building a career as a front-end developer, you’re now leading developer relationsfor Contentful. What does exactly the job involve? 

Developer relations is still a fairly new field. What we see over the last decade is that a lot of technology companies. And especially the developers using these technologies have a lot of decision power. We at Contentful are one of these software providers, a headless CMS (Content Management System) that you can put anywhere. And our developer relations team doesn’t work directly on the product. We have completely separated engineering teams that are building the APIs and the product itself.

And the DevRel team is there to spread the word about Contentful but also going into the communities and helping developers with whatever they’re struggling with. And this can be Contentful related, but very often it’s also just web development related. So, what we’re doing is that we are blogging, we are building code examples, etc. And whenever we are talking to users or customers or friends; we are basically the bridge between the product and the developer communities out there.

When someone has a problem with something, our team are usually the first people that they go back to. And we’re then feeding all these things back into the process and building this trust within the developer community. So, yeah, we are blogging, speaking, writing, and hanging out on our community Slack. To connect with the people, have a little bit of fun and build cool stuff. That’s what I do for a living.

But you also enjoy creating content for web devs in your free time, right? 

Yes. Since this year, so since 2021 and the pandemic and being stuck home, I’m writing a weekly newsletter. If people are interested in random web development stuff to read on a Monday morning over their coffee… It’s usually something around 10 resources, some GitHub repositories, some music, etc. And I’m writing that every Sunday. So if you’re up for some random good stuff I thought was good over the week, people can subscribe here. 

So where do you draw the line between your personal blogging and the one you do as part of your developer relations job?

Well, when you work in DevRel, the line is very, very blurry. Where does work start and where does it end? So I usually do a lot of things on the side. Right. So I do a lot of blogging on my own blog and occasionally I do something for the Contentful blog. Lately, I am leading the DevRel team, which means that I’m not hands-on with the content that much anymore. But I’m still around and the line is very, very blurry.

When you work in these semipublic roles, it’s usually like “Oh yeah, Stefan is the Contentful guy”. And when someone writes me DM on Twitter on a Saturday because they’re struggling with something, well, I’m the last person to say “Yeah, no, it’s the weekend, not going to help you right now”. So it’s very hard to tell where it starts and ends. But I’m just really into web development and I like to share all the things that I learn and that are exciting. And that’s just what I do.

Join our community and find your next job or expert in IT

What advice do you have for other IT pros who want to create content and share tips to help out others? How did you start creating content for web devs?

It’s hard for me to give advice, but I can say what I do. I made it a habit of writing something down or creating a video or some sort of content around things that I discover. I’m also reading a lot. I’m subscribed to a gazillion newsletters. So when on a Sunday morning, I read something and have this thought “Huh, I didn’t know that”, I put it somewhere. It could be on my own website, or it could be on Twitter. But just making this habit of constantly documenting what you’re learning helps with this whole idea that you don’t know anything about web development, because this fear is just so big.

Connect by Mindquest Newsletter

I have been doing this for three or four years. And what that comes down to is that I now have, I don’t know, 200, 300, 400 learnings on my own website. And these are primarily for me. So this is how it started. Because I wanted to come back a month later or six months later and look at it and say “Man. You got a lot smarter over the last six months”. But, after some time, more and more people discovered what I wrote. Because, if it’s useful for me, usually I’m not alone.

And that’s one piece of advice that I would give to people that want to start creating content or blogging. If it’s useful for you, you are usually not alone. And there is nothing like “Oh, beginner content is not useful” or “It has to be this 2,000-word, in-depth article with a lot of scientific, engineering knowledge”. That’s absolutely not the case. We have so many people joining the industry. And whenever you learn something or when someone learns something, I think it’s a very good habit to just write it down.

And then you have the greatest feeling in the world. When some people write me an email or send me a tweet tell me “Hey, Stefan, I just learned this thing. You learned that three months ago and now there’s two of us.” And that’s just beautiful because you can kind of connect the two things, helping people but also documenting your journey.

And you have even built some tools to help you and others in the learning journey, Tiny Helpers and Random MDN. Can you tell us a bit about them?

Tiny Helpers is a very simple website that I created around Christmas one and a half years ago. There are so many self-built or quick build tools that you usually cannot Google. For example, there are a lot of people that build tools for accessibility or tools for defining font sizes, but when you Google them, you will never, ever find them because they are not SEO optimised. There are not a lot of words in them. If you find them and don’t bookmark them, you will always lose them. So, I just built this little resource collection that is Tiny Helpers, and I put it online because that’s what I do.

I thought, “Well, if it’s useful for you, then it’s probably useful for someone else.” And the whole thing is open for contributions. I think I have had over 100 contributions. And there are quite a few people that just come in and say “Oh, that’s useful. I should add that to Tiny Helpers because that’s where I go to find little online tools.” And, when I’m looking for a very specific tool that I’ve seen online, I’m going there as well and it’s the same thing. If it’s useful for me, it’s usually useful for someone else.

The other project that you mentioned, Random MDN is a quick and easy Twitter bot that I built to support my learning journey. So MDN is the developer resource for Mozilla, and it is huge. There is so much knowledge in there and I just had this random thought: “Hey, it would be kind of cool if there was something that tweeted out random MDN pages. It tweets six times a day. It just grabs the sitemap from MDN, picks a random page and tweets it out. And I learn new things just because of it. Sometimes I see a tweet and I am like “Huh, I didn’t know that.” And very often this me to blogging about it, just because my own bot taught me something about web development.


Check out more of our interviews from our podcast episodes.


Follow Stefan through his blog, Twitter, GitHub, and LinkedIn.

Also discover our article: A Data Centre Migration Is About Technology and People

Categories
About us Featured Podcast Interviews

From Hacking NASA to Protecting Your Online Accounts: A Chat with Rickey Gevers

Ethical hacking can be the solution to some of our most serious cybersecurity issues. We interview Rickey Gevers, cybersecurity expert and founder of Scattered Secrets, a password breach notification and prevention service that is helping businesses and individuals protect their online accounts.  

Here is how this Dutch security pro got into hacking, was arrested by the authorities, and went on to show how that his talents could also be a force for good.  


🔊 Subscribe to the podcast


How did you get into hacking? 

My dad was really the one who introduced me to tech. I’m not a typical technical person. I like to play outside and those kinds of things. So, not necessarily being behind a computer. But my dad bought a computer when I was young, so I started playing with it at a young age too. I liked the Internet a lot because you could search for anything you wanted. I am a very curious person, so I was looking things up all the time.

But an Internet connection was very expensive back then, and at one point my parents had to pay a lot of money because of me. So, they used a Windows password. But I managed to break into the Windows user account and started using the Internet again. They got mad again, and then my dad used a BIOS password, which was a proper measure to keep me out for a month or so. 

 Then I managed to take out the whole modem, put it in my own computer, install all of the drivers and use the phone connection from the moment they left the house.  And I put my computer in such a position that if they came home, I could see them entering and remove the cable, remove the modem, and put them back in my dad’s computer just in time before they entered the house. That’s how I sort of started hacking, in a pretty natural way. I wasn’t really busy with hacking or anything. I just wanted to get the things done. 

Then, at the age of 13, you created Waarneming.nl, a leading community-driven platform where users collect and share data for nature conservation, research or education. How did you go from there to the major leagues of hacking?

Usually, when I talk about the things that I have achieved, I see Waarneming.nl as the brightest thing that I’ve done. I didn’t make any money from it, but it contributes a lot to society. And at one point the website got hacked, which I will never forget. One guy just took it offline and put some defacement posters on it. I put the website back online but, after half an hour, the guy defaced the website again. It a lot of fun for him but, of course, it was not for me.  

I decided I didn’t want this to happen anymore in the future. And the only way to stop it was to understand how hackers work. So, I started to learn to hack and, pretty quickly, I hacked my first computer. I kept on challenging myself. Back in the day, nobody got arrested for it. I didn’t break any computers ; didn’t delete any files or whatever you can imagine ; I just hacked the computer and that’s all I did. So I started aiming for higher targets. I went from one computer to a computer network. I went to universities because they had fast Internet connections. And I moved up the ladder and eventually was able to basically hack any network, move laterally within the network and become the main admin. And that’s sort of where my story ended. 

Join our community and find your next job or expert in IT

Then you got caught. 

For some reason, the University of Michigan did a forensic investigation, found me and arrested me. As I said, this was back in the day, so not a lot of hackers got arrested. I had also hacked NASA, to just give you an example. And I remember one guy got arrested for hacking NASA, but at that time, it was very normal to hack computers at NASA. 

What exactly happened with the whole University of Michigan incident?

Well, the University of Michigan was sort of my playground, because the Internet connection there was very slow. So, if I wanted to try some new tools that I had found, I usually tried to do it on a network there, which is probably one of the reasons they caught me. But they did a proper forensic investigation and they determined that I was in the network, that I had full control of the network, but that I didn’t do anything else. So that’s why the FBI basically did not chase me.  

Connect by Mindquest Newsletter

Then the high-tech crime unit here in the Netherlands was established and they contacted the FBI and asked them if they had anything they could do for them. So that’s when the FBI said, well, we have a file here. We know its name, we know where he lives, so maybe you can pick up the case. And that’s basically what they did. I got arrested by the high-tech crime unit as one of the first hackers they arrested, I believe. They thought I was a really big hacker, which I wasn’t, of course. I did hack a lot of computers, but I never did anything with it. So, I was basically a huge disappointment. 

Then, after some years under trial, and a suspended sentence, you went back to hacking, but with a different approach. You went on to create Scattered Secrets. What was your thinking?

At first, when I went on trial, I wondered “should I continue this?” But after two years, I was like “well, I’m only good at one thing, so let’s just fight back and show everybody that I’m on the good side and that I don’t have anything to do with criminals or whatever.” And I started hacking again.  

I did a lot of penetration testing, and at one point I noticed that you can easily hack any company and you usually do it with the same trick. That’s when I started building Scattered Secrets, because I believe you can hack any company by simply looking at the passwords that have been leaked. So that’s what we’re trying to fight against right now. We’re basically doing the low hanging fruit for most hackers. It’s not that interesting. It’s not that advanced. But, in our opinion, it’s the most dangerous and easiest way to hack any company right now.  

So, you basically monitor for passwords that have been hacked and leaked. Where do hackers get these passwords?

The funny thing is that most passwords are leaked through only a few databases. We have a few enormous leaks. One of them is MyHeritage. The other one is MySpace. And the third one is LinkedIn. That’s where most passwords come from. It’s often the small databases people are in, but once every two years, you have an enormous breach.  

Given these ongoing data leaks and recent headline-grabbing global breaches, how do you think we are doing in terms of cybersecurity? 

Often, if you talk to security experts, they say we’re not getting better. But in my opinion, there won’t be a single day without hacks. That’s simply because you have the human factor, and the human factor is always vulnerable. We can build secure systems, but there’s still a human using them, so it will always be vulnerable. So, we have to deal with the fact that there will always be hacks. 

At the same time, when it comes to multinationals – back in the day, in 2014 or prior to that, we had these flat networks, and you could easily become the administrator. It was pretty easy to hack large companies. I think most multinationals now have a certain base level. And, sure, in the news we see the ones that don’t have that base level. But we’re getting more and more mature. I think that’s the most valuable lesson.   

To you, what’s the most challenging aspect of cybersecurity? 

As a security researcher, I think the most challenging part is that you have to keep up with your knowledge, you have to continue learning and working. If you stop doing certain things, your knowledge starts to lag behind. It’s a constant battle to keep your knowledge at a certain level.  

And what are your go-to cybersecurity education resources to stay at that level?

Without a doubt, the SANS Institute. In my opinion, they’re the only real experts. It’s very expensive, between six and eight thousand euros, but it’s absolutely worth the money. I try to do a course every year, but it’s not always easy to find the time.


Check out more of our interviews from our podcast episodes.

You can follow Rickey on Twitter and LinkedIn.

Categories
About us Featured Podcast Interviews

Changing Lives Through Tech Education: Interview with BeCode’s Karen Boers

Tech education is a force for social transformation. We interview Karen Boers, co-founder & CEO of BeCode, a Belgian coding school bridging social divides through tech education. A social entrepreneur at heart, Karen has kick-started various successful digital transformation projects over the years – including the European Startup Network, the EU’s first network of national startup associations. 


🔊 Subscribe to the podcast


How did your professional career begin? How did you enter the tech space?

Well, after some time in HR, I joined what at that point was a brand-new research institution focusing on software innovation. I joined as a management assistant, so absolutely nothing to do with the tech part of the company. But it was a burgeoning institution, and we grew quite rapidly. I evolved into marketing and communications and took on HR as well for a research staff of one thousand people across multiple universities in our country.  

We worked closely with industry partners to understand their needs and design software solutions for real-life problems. Not just economic problems, but also societal problems like children that have been ill for a long time and have been isolated from the learning environment. It was the pre-Internet era. So, we started working on solutions for children to have a virtual playground and play and chat with their friends. It was really cool. That’s what got me interested in technology. Not the technology itself, but how it can offer answers to societal problems and bring human-centred solutions into the world.  

Then you went on to create several business and career development projects, as well as Europe’s first unified startup network. And at what point did you decide to dive into education and create BeCode?

I saw there was a huge war for talent raging all over the tech world. Not just for startups, but also in bigger companies. During one of our international missions to Kenya, we visited a coding school that was taking people off the streets, providing them housing, and giving them the training to become programmers. They would then introduce them to European startups looking for new talents, offering them as remote employees. And I thought “cool idea, but maybe there are similar solutions to be found closer to home.” 

If we cannot find the right talents to join these companies, then we’re going to be in trouble. And not only from an economic point of view. We also have a huge societal problem with lots of people that are being isolated, cornered, and that face a lack of prospects. And, if we don’t address that problem, then we have an even bigger issue coming up.  

Being the mother and stepmother of five teenagers, that was kind of in my face. I thought “if I don’t help resolve these issues, my children are going to be in huge trouble five to 10 years from now.” So, for me, the sense of urgency was pretty high. That’s how BeCode emerged from my multiple professional experiences.  

I had my love for education, my industry experience, my experience in marketing, and my first steps as an entrepreneur. It all came together into a bigger project where we basically go hunt for untapped talent. We go look for people who are low-educated, in long-term unemployment, of immigrant background, etc. People who, for whatever reason, are struggling in today’s job market today, but definitely not for lack of talent or motivation. 


Join our community and find your next job in IT

How do you reach these at-risk people and help them realise and unleash the potential of a career in tech?

We go search for them. We try to inspire them into considering ICT as a career. Often, the problem is not that they’re not talented, but rather that they don’t know that they’re talented. They’re not aware of the potential they have. So, there’s a lot of awareness and evangelisation to be done with these audiences, to get them excited about tech and consider such a career choice.  

Then we help them through really hands-on training programs. Not through too much theory, not through listening to the big expert who will tell you what to do, but basically through trial and error. We give you a small exercise, a project, then something more complex, etc. You have a small group of peers and lots of resources that you can draw on. Basically, nobody reads a manual before they start solving a puzzle either, right? They just pick up the pieces. They try bits and pieces. And if it works, it works. And if it doesn’t, you search for another solution. That’s what they do.  

What skills are you putting the focus on through your tech education programs?

The funny thing is that our tech education does not actually focus on the tech skills themselves. I mean, it’s a means, but not an end. What we focus on mostly is teaching them how to learn in a technical environment, because whatever competency or programming language teach them today, tomorrow the context and the technologies will have changed. So, they will have learned basically nothing, or at least not how to continue developing themselves as professionals.  

That’s why we focus a lot on learning how to learn: understanding where the resources are; how you can apply them to a use case; what to do when you get stuck; how to build a network of peers where you can go and ask for advice; how you look at examples and copy-paste, but not exactly copy-paste, and debug, etc. So, it’s much more about the soft skills and the learning process around technology. 

Connect by Mindquest Newsletter

In the end, they come out with a basic set of technical skills, but mostly with the ability to continue learning once they leave this environment. Especially because in seven months you can’t learn everything. So, whatever they come across, they will have to keep learning for probably the rest of their careers.  

And that’s what we hear from the companies that hire our graduates. It’s a combination of, “OK. It’s nice to have people with a different perspective around the table, but it’s also nice to see that eagerness to learn and that ability to learn and be a problem solver rather than a bringer of problems.” Also, the ability to resolve problems as a team and work towards goals together. 

What’s usually your main piece of advice for those starting out with their tech education?

Always dare to fail. If you don’t try, if you don’t experiment, you’re not going to learn. When you learn how to walk as a kid or even how to ride a bike, which is already a bit more complex, you don’t go sit down and read the manuals first. You fall flat on your face at least a couple of times. But you get back up on your feet. You look at your parents to ask “what exactly did I do wrong?” And maybe they give you a little nudge left or right, and you try again. You do better. And that’s how we learn.  

It’s our natural way of learning. We have to accept that, if we want to learn as adults, we also have to fall flat on our face a few times and hurt ourselves a little bit. We’ll look at other people for small tips and pieces of advice, then take those and try again. And that’s OK. It’s not shameful to try something and not succeed at the beginning, or even not to succeed at all. But if we don’t dare to venture out there and try, then we will get nowhere.  

What are some of the most incredible stories of personal transformation you have seen at BeCode over the years?

That’s a tough choice. We have seen over 1,500 stories pass in front of our eyes, and many of them are absolute tearjerkers. I think the one that touched me the most was that of a female refugee. She spent two years trying to come to Europe and had asked for asylum. It was a really rough journey where she saw a lot of hardship and people suffering around her. I don’t think she even dares to tell the people that she met here in Belgium.  

She then spent another two years here going through the motions of becoming a refugee: doing the paperwork, learning the local language, etc. And then she came across BeCode. She was so eager to learn.

While she was with us, she was also trying to get her children, who she had had to leave behind, over to the country. And she succeeded not only in finishing the programming course and securing herself a job, but also in getting her children here. You could see it in her eyes that she was absolutely convinced that she was going to make this happen. No was not an option. And she persevered. She had a rough time during the training at certain points, but she always saw it through and found a way out, and she was always open to helping other people. When you see people like that graduate, secure a job, see them reunited with their children; those stories, they stick with you for life. 

But I love helping the local people as well. It can be equally rewarding to see somebody who’s been a truck driver for twenty, twenty-five years and started struggling with their back and is not able to drive the truck anymore. That was basically their whole life. They spent their whole life in their truck and then, all of a sudden, they’re completely stuck. If you can somehow make them see that there might be an alternative career for them through tech education, an alternative future; that can be a life-changer. 

What new tech education projects is the BeCode team working on these days?

We have seen that, for some, becoming a professional programmer is a good career choice. But for some, it’s a bridge too far, and that’s okay. Right now, we are developing a number of shorter training programs, so that they can just taste and try and then decide whether it’s something for them.  

But we are also working on programs to teach people basic digital skills, how they can survive in a collaborative workspace so that we all had to become acquainted due to the global pandemic. Things like how to download your work schedule from the Internet as a factory worker, how to apply for your holidays through an app instead of by writing on paper. 

If you look at recent studies, the digital divide is mostly on those digital skills. Yes, there’s clearly a shortage of programmers. But the biggest problem is on fairly basic digital skills that really hamper people from being proficient as professionals and in their personal lives. And that’s a disaster.  

If you look just at Belgium – and we’re quite a developed country, aren’t we? – 40 per cent of all Belgians lack the digital skills to be proficient in what they do today. And, if you look at low-educated people or people in low-paid jobs, that number rises to seventy-five per cent. So there’s a lot of work still to be done and not just on the programming side. That’s our conclusion and our path forward, to include these people as well and not leave them side-lined. 


Check out more of our interviews from our podcast episodes.


Follow Karen on LinkedIn and Twitter.

You can connect with BeCode through their website, LinkedIn, Facebook and YouTube.

Categories
Press review Tech Magazine

A Ransomware Attack, Self-Taught Robots and Online Abuse: The Week in Tech News

In the world of IT, real news can easily get mixed with eye-catching headlines and promotional buzz. From a critical ransomware attack to tackling online abuse: filter out the noise with our selection of the top 3 tech news stories of the week.


Full podcast episode:

🔊 Subscribe to the podcast


Join our community and find your next job or expert in IT

Ransomware attack: the new oil disrupting the old one

One of the most echoed statements about data is that it is the new oil. Regardless of whether you agree or not with this comparison ; you will surely find it ironic to see how much the decryption of data, this “new” oil, can end up affecting the old one. 

Last Friday, Colonial Pipeline, one of the largest oi pipeline operators in the United States, experienced a ransomware cyberattack that pushed it to shut down its IT systems. Linked to the DarkSide hacking group, the breach happened on the business side of the company’s IT infrastructure but affected its nationwide operations. 

Although it is thought the motivations behind the attack were economic and not of sabotage, the incident reignites fears of the dangers hackers pose to a country’s critical infrastructure. Oil prices have gone up due to the supply disruption, with people all over the US piling up fuel reserves. The issue might not be fixed until the end of the week.

ZDNet

Self-taught robots

The idea of programming AI systems to teach themselves has been gaining major traction in recent years. Flexible software that is able to learn through experience makes a lot of sense. But our current capabilities in this regard might not be as far-reaching as we think.

A group of Amsterdam-based researchers built a simple robot and tried to make it learn how to move through trial and error. Made of independent units chained together into a train-like structure ; the robot used a series of inflating pumps to propel itself at a top speed of two millimetres per second. 

Unfortunately, while the autonomous learning system managed to effectively move, maintain a stable pace and follow a circular track, the robot encountered a few real-world problems that threw all its calculations off. A good reminder of how easily a variable not accounted for can disrupt machine learning algorithms.

Ars Technica

Tackling tech-enabled abuse

The tech boom caused by the pandemic has brought along some troubling side effects. An increase in online abuse is one of them. With the number of tech abuse cases requiring specialised assistance having grown by 97% over the last year.

All around the world, domestic abusers use both legitimate online tools and so-called stalkware to harass, control and monitor their partners. Suffice it to say, this kind of behaviour usually predates or accompanies other forms of abuse, from physical to psychological. 

That’s why the Barclays-backed non-profit Refuge has launched a site to help abuse victims protect themselves from tech-enabled domestic abuse. RefugeTechSafety.org has been built with the help of survivors and provides educational and actionable resources in multiple languages. 

Computer Weekly


Check out more of our interviews from our podcast episodes.


Categories
About us Featured Podcast Interviews

What Makes a Successful Web Dev: Stefan Judis, Front-End Dev Expert

What makes a successful web dev? We interview Berlin-based front-end expert Stefan Judis. Stefan works for the content management platform Contentful leading developer relations. Whether it is by tweeting, writing, or streaming, he loves sharing his web development expertise with the broader community. He also helps maintain Tiny helpers and Random MDN.



🔊 Subscribe to the podcast

Let’s start from the beginning. How did you get started in technology?

I started working in a completely different field after school. I was working as a sound engineer, and I worked in German television. So, what I did for a couple of years was mixing stuff mainly for sports TV shows. But then I figured out that I didn’t want to do that my whole life, that that wasn’t going to fly going forward. So, I thought, well, you’ve been always good with computers.

Then I started studying here in Berlin, where I learned to program stuff. So, it all began with a little bit of C++ and Java and these kinds of things that you learn at university. Berlin is a very start-up-heavy city, so I landed an internship working with Magento and PHP – not real front-end stuff like we do these days; that was not really a thing yet back then. But yeah, I took my first internship and from then I just jump from company to company and learned that I love the web and love writing and creating content around web technologies.

What made you fall in love with web development?

I’ve always liked the visual aspect of it. When I started, I was really into the Magento stack and I thought it was kind of cool, but I always liked the whole visual animation part of doing web development. And when I started, it was still the early days. Then, you know, slide up, slide down, fade in, fade out, all of these tiny functions. But II found these incredibly appealing. And then slowly but surely, front-end development became a real thing. Then more complexity got into that, and I was completely hooked by all this new technology that was coming out. Then I found out that building for the web is fun. And since then, I tried to build the best stuff possible.

Join our community and find your next job in IT

What was the hardest part of your transition into tech?

Well, especially in web development, learning is difficult. I have been doing web dev for 10 years, and when I started, I was incredibly impressed with what people were doing there. So, I remember I was sitting next to a colleague, and they opened their terminal, and they were doing some fancy stuff in this black window and I was like, “holy moly this is a completely different world.”

I think it was rather challenging to figure out what exactly I had to know. What should I know how to do? But also building a career around that. I think it’s also important to figure out what you actually like.

So, even though now I say that I specialise in front-end technologies, that took me quite a while. Then, I would say that it took me two or three years to figure it out and get a clearer picture of what is actually out there. And it’s only getting worse, especially in the front-end sphere, because there’s just so much technology out there. A lot of people keep asking me: “Hey Stefan, what should I learn?” And I’m like, “well, good luck figuring that one out.” So, I think that is definitely a challenge that we have at the individual level, but also at the industry level, because there’s just so much stuff happening these days.

Given how many open fronts there are these days, what would you recommend to those who don’t know what to focus on?

For people who are just entering the industry: do whatever is fun and useful, really, because there’s so much stuff to learn and it feels very, very overwhelming. Build your website, get it off the ground and do whatever is fun and useful. But what I usually recommend to people is: don’t forget to be curious about the technology when doing so.

Connect by Mindquest - Newsletter

What we see right now is that there are a lot of people just learning a framework when they enter the industry. And, while that is great to get a product off the ground, I think it’s very important to understand what is actually going on. I’m a big fan of the pillars of the web, HTML, CSS and JavaScript, and I think it’s still important to have a very good fundamental knowledge of these technologies. And these are huge areas by themselves. You cannot be an expert in all three areas, especially when you have frameworks on top and that and maybe something on top of the frameworks. But I think curiosity and having this drive to say: “Ok, I’m using that. But how does it actually work?” — I think that’s very important to become a good web developer.

In your experience, what separates a good web dev from a great one? Is it soft skills, or is it more about hard skills? What make a successful web dev?

I think there are two areas. Soft skills are usually a very underrated thing when we speak about software developers. Being a team player in general, I think this is definitely a crucial part of a solid career. Being humble, being helpful, all the kinds of things that make you a good team player. That’s something, for example, that probably should have been taught at university when I studied. Good or great teams or developers really depend on soft skills. And I would love to have the industry focus a little bit more around that.

And speaking from the technology side of things, I think a great web developer is someone who always puts the user first. What happens in web development right now is that we have a lot of technology fatigue. We’re using the latest and greatest just because it is the latest and greatest or just because everybody is doing it. So, what I see very often are overengineered sites and products where something simpler would have done the job.

There’s nothing wrong with building something with the latest and greatest when you’re playing around and you’re building your own blog. But when you’re building a commercial product, I think it’s very important to take a step back and think: “Hey, did that make the whole thing slower, or is it now more inaccessible or is it less robust just because we wanted to use the latest and greatest technology?” I think great developers keep the bigger picture in mind and think about the user to build the best possible product. Because at the end of the day, that’s what we’re paid for. We’re not paid for playing with tech. We are paid for building something great.

What would you say are the top three soft skills a successful web dev should have?

I would say it’s the usual things, from being helpful to being humble. Putting yourself into the shoes of your colleagues and customers, I think that is a very underrated skill. Very often it always feels like everything is on fire and everybody wants something. But very often, and I’m guilty of that myself, it’s necessary to take a deep breath and think about where the other person is coming from. I think this is very valuable when it comes to building a career or working together in teams.

One piece of advice that I received a few years ago and that I now keep close to my heart is that when you’re working it can get quite stressful, always under pressure. And very often, what happened to me is that I had this kind of “anti-” mode. I was like, “everything is too much.” And I just ranted a lot to other people. And I once ranted in a situation where the person was in front of me. They went like: “Stefan, I feel you, I empathise with you, but what’s the solution?” And I didn’t have one. I just wanted to rant.

Since then, when I really had the feeling that something had to change or something was really going on with my nerves. Try to think about the solution first and then propose that to colleagues, your bosses, your mates or whoever is around you, because very often ranting doesn’t solve the problem. And it’s very easy to rant instead of changing something. And that’s something that I learned and that I have kept with me for a couple of years now. And it’s definitely helpful.


Check out more of our interviews from our podcast episodes.


Follow Stefan through his blog, Twitter, GitHub, and LinkedIn.

Categories
About us Featured Podcast Interviews

From Stay-at-Home Mom to Full-Time Web Developer: An Interview with Olena Drugalya

The first part of our interview with Olena Drugalya, a Berlin-based, self-taught front-end developer who just recently managed to go from being a stay-at-home mom to a full-time dev. Born in Ukraine and having lived and worked across Europe, Olena discusses her transition into tech, the barriers she encountered along the way and how other women can overcome them.

Learn of Olena’s progress with her account after two months into her first developer job.

🔊 Subscribe to the podcast

Interview with Olena Drugalya: Congrats on your new job! You made it. How did you go from stay-at-home mom to full-time developer?

Thank you! My transition into tech was a long and winding road of failure, hard work and, eventually, success. So, let’s start from the beginning.

I graduated in linguistics and law, but I never worked as a lawyer. Fresh out of university, I found a job at a trading company as a translator, as there was a huge demand for speakers of foreign languages at that time in Ukraine. I worked in the company for 10 years and was promoted a couple of times, ultimately becoming an executive manager.

What happened then?

Then I met my husband and we got married. We moved to another town, and I worked remotely for some time, but it didn’t go too well because my daughter was born, and I didn’t take maternity leave. Not long after that, I was already burned out from the job, from having a baby, from the move. So, I quit my job.

But, after some time, my daughter had grown older, and I started to think about what I would like to do next in my life, my career possibilities, etc.

My husband is a software developer, so he suggested that maybe I could find a development job in our city. There was a coding academy that offered a course on software development on the weekends, so that worked for me as my husband could watch my daughter during the weekends. I learned there for two years and graduated as a .NET developer. After that I graduated, I participated in several projects. I even built an online game and actually got some money for it. So, I was like, OK, I can do it.

And then…

Then I decided to try to get a job at a company, not just freelancing. But at that time, in Ukraine, it was very difficult for a woman to enter the tech world if she didn’t have a computer science degree. So, I had a couple of interviews, and that was a failure. A total disaster.

So, after a range of failed interviews that got me discouraged, I decided that tech was not for me. I always thought that, for being a developer, you needed a special mindset, and that I just didn’t have it. And everyone around me seemed to think the same, except, of course, for my husband. But I was too unmotivated and frustrated. So, I stopped. I decided it was not for me, that I would try something else.

Women in tech

We moved to Denmark, where I got a job as an office manager. I was quite happy with the job, since we had just moved in, and I could learn Danish and do something useful instead just sitting at home. But while working there, I realised that, in western Europe, the situation with women in tech is totally different. In fact, tech companies encourage and offer women enormous possibilities in the tech industry. That made me think about tech again, and I decided to give it another shot. This time I started with web development and that’s what I’m doing right now. We moved to Berlin, and I recently got a job as a junior software developer at IT services provider Novatec. And I love it.

Join our community and find your next job in IT

You mentioned how hard the interview process was at times. What would you say to people who are going through failed interview after failed interview? How can they keep their spirits up?

Above all, that you just must keep going no matter what. If you really want this job, if you really want to work in tech or in any other industry, you just need to learn from your failures and just move on and try again. Failing at an interview doesn’t mean that you are not good in what you are doing. Sometimes there is just a better candidate, or the company has a different profile in mind. It often just means it’s not the right time or the right company for you because they are looking for something else.

Do you think your background in humanities has helped you in tech?

Absolutely. Knowing a lot of languages, for example, has helped me a lot. Speaking English is a big plus in this industry, and I can speak German too. There are a lot of wonderful developers out there who are missing out on great opportunities because they don’t know languages. All technology now is made in English. Plus, if you know how to learn a language, you know how to quickly learn new structures and words. You can directly apply that to learning a programming language. You learn the grammar, the syntax. The same goes for fluency. In order to get fluent, you just need to write code often. You just need to treat programming just like any other language.

How do you combine your job, learning and raising kids, especially during lockdown?

You need to have a daily routine. Otherwise, you will always feel like you don’t have enough time. I was lucky to have the help of my husband. When my son was little, I usually studied for two hours after he went to bed.

That was, of course, tiresome, because usually you don’t feel fresh anymore in the evenings. But I had no other choice. But the first lockdown actually helped me a lot with goals, as my husband started to work from home, and we shared the time with the kids. From morning until noon, he was with the kids, and I was with the kids from noon until the evening. I had my two or three hours to myself every day, and that was fantastic. Then I jumped right away into the 100 days of code challenge. I made a habit of coding every day for at least one hour. And I have been doing it every single day since. So, yes, the daily routine is very important.

You are very active in the dev community, sharing development tips and your journey into tech. Why do you enjoy blogging, how has it helped you?

I started my blog when I started my studies as a web developer. First, I wanted people just to know my story about being a stay-at-home mom and learning web development. I was hopeful it could encourage other women like me who were afraid of transitioning into tech. But as I proceeded with the study, I started to write posts about topics I was learning at the time.

I thought that many blog posts or YouTube videos out there were not really that beginner-friendly, often being written in a rather complicated language. So, I decided to try to write down these difficult concepts just in a simple language, just for myself. If you manage to understand something by writing about it, you actually learn it more deeply. Then I saw others were struggling with the same problems and decided to share these materials with the broader community.  

I encourage everyone to start writing the blog. It’s one of the best ways to learn by yourself because you need to research something and then you have to explain what it is and what it does, and how you can use it. It’s also a great way of holding yourself accountable and make sure you keep progressing towards your goals.


Check out more of our interviews from our podcast episodes.


Make sure to follow Olena’s blog and Hashnode activity.

You can also follow her on Twitter and LinkedIn.