Forem: Valerica Plesu

Android real-time pose detection app using TensorFlow Lite.

Valerica Plesu — Thu, 09 Apr 2020 19:13:17 +0000

I hope everyone is doing fine in the current situation.
The quarantine was not something that I have ever imagined before.
In Romania, we are on lockdown for almost one month now and we’ll continue one more.
There are lots of articles about productivity work from home tips but let’s face it, it's hard, it’s stressful, it’s new. When was the last time you spent an entire month inside your home?

I’m sure that each of us is doing their best, no need to overreact about this and I bet that no one is more productive now just because they are wfh, no, this is isolation, not the normal situation.
We are all on the same boat, all over the world.
Thank God we have The Internet and everyone is still connected.

When I feel down and I’m done with Netflix, HBO Go or other resources I try to redirect myself to self-improvement.
I was thinking to try fitness since nowadays I do lack it, but I know myself and I know that I can get injured really easily.
So why not combine Technology and Fitness?

Goal

To keep me busy and to learn a bit more about technology. Developing an Android app using TensorFlow Lite.

What is TensorFlow Lite

TensorFlow Lite is a production-ready, cross-platform framework for deploying ML on mobile devices and embedded systems.

It enables on-device machine learning inference with low latency and a small binary size.

TensorFlow Lite consists of two main components:

The TensorFlow Lite interpreter, which runs specially optimized models on many different hardware types, including mobile phones, embedded Linux devices, and microcontrollers.
The TensorFlow Lite converter, which converts TensorFlow models into an efficient form for use by the interpreter, and can introduce optimizations to improve binary size and performance.

TensorFlow Lite is designed to make it easy to perform machine learning on devices, "at the edge" of the network, instead of sending data back and forth from a server.

But what is it useful for?

There are different models ready to be integrated into your app from the website.

Functionalities

The app I develop will monitor my posture and remind me to stand up after a certain period of time and do some yoga exercises.

The problem

How do I determine if the movement is a yoga one?

Development workflow

Pick a model

The first model I've used is the single-pose detection model. Pose estimation is the process of utilizing computer vision techniques to estimate various elements of human posture within an image or segment of a video.

PoseNet provides a general-purpose pose estimation model. This model may be used for simple applications containing a single human body for the purpose of joint detection. As an example, the model can estimate the position of a person’s elbow and/or knee in an image. The pose estimation model does not identify who is in an image; only the positions of key body parts.

What makes this model fascinating is its ability to track joint movements in real-time with a relatively high level of accuracy and flow.

TensorFlow Lite is sharing an Android sample application that utilizes the device’s camera to detect and display key body parts of a single person in real-time. Check out the source code!

The second model I've used is an Image classification model.
Image classification is a common use of machine learning to identify what an image represents. For example, we might want to know what type of animal appears in a photograph.

The task of predicting what an image represents is called image classification.
An image classification model is trained to recognize various classes of images.

Train and Convert the model

So back to my problem, my model should determine yoga movements so I need to train it and at the end to convert the model to the TensorFlow Lite format since I need it to run on Android.

Data Collection

I’ll be training a classification model, hence my dataset will contain different kinds of images that the model has to identify (yoga movements).

I found that Python provides us with a handy third-party package called google_images_download, which has easy-to-use syntax and can automate the search over the internet of yoga images.

Before I train my model, it’s essential that I get rid of these images from the dataset that are garbage.

Train the model

I'm using AutoML Vision to train and convert the model. A quick start you can find it here.

My dataset looks like:

Doing this training in a traditional way would have taken way more time and effort on my end and would have involved installing and setting up dozens of third party packages. I think it is a good idea to use existing tools like AutoML.

After completing this process I have exported the trained model files: a TF Lite file, a label file and a metadata file.

Test the model

I uploaded a test picture to see if it is classified right

Deploy & use & have fun!

I added my model to my existing app, so now I can run it on the android phone.

I know that everyone is thinking about how to protect themselves and their families, food, and shelter but in the end, programming is how we get paid and we have to remember the privilege that we have by being able to work from home.
Let's take this quarantine to show our passion, to connect with the people we love and to shift the mindset to something better.
Don't get angry, don't let emotions drive you in and focus on what you can control.

Thanks for reading!

Developing for the future, My smart fridge

Valerica Plesu — Mon, 02 Mar 2020 16:41:29 +0000

In a constantly changing world where powerful AI-based applications are day by day more accurate and efficient than any technology, it’s hard to keep track of such a big transformation.
As developers, we need to learn how to leverage the technology in such a way to solve problems from the real world and even if we are not implementing some of the world’s most cutting edge technologies we can integrate them into our daily workflows.

My eagerness to try out the latest technology and the love for coffee made me search for a solution of a problem I had, how do I check if I have milk in the fridge? (yes, I make my own cappuccino).
Of course, many exciting systems came into my mind, like a bunch of pressure sensors placed into the fridge or a cam so I can read real-time what items do I own. But this comes with the obvious risk of not implementing it since it introduces the hardware part so the complexity grows.

So back to my need I started to implement an app for the Google Assistant, an app to help me keep track of the items I have into the fridge.

But what are actions?

Actions on Google lets you extend the functionality of the Google Assistant with Actions. Actions let users get things done through a conversational interface that can range from a quick command to turn on some lights or a longer conversation, such as playing a trivia game.
There are many conversation design principles but the main idea is to create such a natural conversation with the Assistant in a way that the user forgets that he is not speaking with a human.

Goal

My goal is to have a fast and easy way to check if I have milk. But why not extend this to any item that can be placed into the fridge and have sort of a “voice list” to quickly access it through voice using Google Assistant.

I started writing sample dialogs.
Sample dialogs are the key to creating great Actions on Google; they’ll give you a quick, low-fidelity sense of the “sound-and-feel” of the interaction you’re designing.
They convey the flow that the user will actually experience, in my case a way to check if there is any milk into the fridge.

During the conversation sketch, I was thinking of a possibility for the users to add any item (milk, eggs, etc) into the fridge, remove one or check what the fridge contains using only speech.

Going deeper into any possible conversation that I can have with the application, I ended in some flows that are hard to follow on a device without any screen capability (like the google home mini).

Available devices:

For example, if I’m going to check all the items I have into the fridge and let’s say that I stored like, 20 or 30 items, to keep track of them by voice is hard. I need to adapt my spoken conversation into a multimodal conversation and check if there is a display available and build a list with all the items.
In this way, I scale my application across multiple devices (spoken alone or spoken with display).
So for devices with an available display, I built a list:

Development part

Building your own natural language processing service can be challenging, so using Dialogflow is the best choice.
First I created a developer project for Actions on Google Console.
Second I created a Dialogflow agent where I started to define all my Actions (add, remove or check fridge items). To create the conversation, here is the place to define intents, to create conversation's grammar or the things users can actually say to the Action.

Intents I've created:

The backend part I wrote it in Kotlin. I use Firebase Firestore to save all users items and query for them when “check food” intent is matched.
I deployed the application into the Google Cloud Platform. This way I do not worry about managing the infrastructure and how to scale it.

Final Thoughts

No matter what programming language you know, no matter what day by day projects you are working on, all the time look forward to solving a need. The technological range is quite big as well as the efficiency and reliability of the technology vary but this should not keep you from doing it. Maybe you will not revolutionize the future but definitely you are having fun trying it.

You can check the app while talking with your Google Assistant, <Ok, Google, Ask Smarty Fridge to check my food.>

Let’s shape the future together.
Thank you for reading this. If you have any questions, comments or funny jokes comment below.

What a difference a year makes in software development? Get in shape for 2020! 🥳

Valerica Plesu — Sun, 29 Dec 2019 10:29:25 +0000

While tech moves so fast you just need to be disciplined, a continuous learner and to be self-educated. It's really ok to look for something else, to have different hobbies, to do the things in your way. Just weigh the pros and cons when you have to.

Here is my list of things I did better this year:

1. Chase a career, not a job - Yes, I’m working on shifts, I do it on the job, I go home and I do it again. I go to conferences, I do networking, I learn new things. All of this is to improve me at my job and myself as a person.

2. Personal projects - Yes, I do learn a lot through side projects. Also, I do chill out on the couch. Both of them are working just fine. Taking the opportunity and investing my time in certain technologies that I cannot use them at work helped me to learn more about Google Actions, building various projects on a Raspberry Pi or trying Augmented Reality applications.

3. Coding is the fun part - Yes, I do LOVE coding. Also, coding isn’t easy. I sit alone for hours and trying to mentally inhabit pieces of software. And there is nothing nice about figuring out why an error message appears.

4. People are unpredictable - Yes, while I’m coding I feel it as a refugee from the unpredictability of humans. This means that I recharge my batteries with being by myself, alone or with my family. This is not good or bad, in the end, coders are humans too.

5. The illusion of easy money - No, actually I have to work really hard and being efficient. Unfortunately, there is no one to just give me a salary like that. There are lots of people saying that working in the technological field it’s easy but actually, it’s hard work.

6. I am better then I think I am - Yes, my intrinsic motivation is huge. I’m hungry, I’m curious, I’m chasing experiences, learning programming languages, frameworks, and new technologies day by day.

7. I’m not as good as I think I am - hilarious, reading point 6. Yes, I do need to focus more on unit testing my code, or TDD or better architecture. It’s my job to make sure that I deliver a better product day by day and to tell my manager about the importance of these.

8. Trust people - the fear of trust is big but eventually, I realized that I’m not alone. My path of thought was on the wrong track the whole time, and the switch to get off was right there, trusting the people around me. I’m not gonna lie, going to talk at conferences made me a nervous wreck but I’m happy that I got the courage to do it.

9. Learning and development opportunities - Yes, I do invest time and money in order to become better. The company I work for has a budget for this also. Attending various conferences, books, and Udemy subscription. If you are willing to grow, the company should support you and if you are not getting along with the culture of the company, find another.

10. People don’t leave organizations. They leave managers - Myth or truth? Yes, I do trust my manager. I find him supportive and I learned in the right environment that it’s ok to ask for help. Being able to figure out that I’m not able to perform a certain task in a specific time interval by myself and choosing between burning-out or ask for help this means to grow.

11. Teach others what you know - Yes, I try to do this every time. I do Android classes for students, I attend local meetups or conferences where I share my knowledge about Android and Kotlin. The best feeling to hear someone says that they learned a certain topic from you.

12. My smile, still, stays on - my friends working at the same company are leaving the company. Yes, it is very sad and I feel that I cannot handle it but I promise myself that I will take the time to gear up the best response.

13. Don’t hide your mistakes - Yes, I do mistakes. But I’m able to figure out what went wrong and why. And more importantly how to fix it. This happens in a healthy environment.

14. Process, Process, Process - Yes, I do fight with Jira, meetings, tickets and so on. In a positive way, I’m not a strong opinioned person about it since I’m aware that those are improving the collaboration and work within the team.

15. Stay committed - Out there, so many tools, architecture patterns and a huge amount of information. Yes, I don’t know everything but I make sure though I know at least one thing really well and trying different paradigms to have at least a clue, knowing that this stuff exists.

16. Stay motivated - Yes, I’m not all the time motivated. There are times I have to work on a project that doesn’t spark a lot of joy. What I do is to search for challenges that I can conquer so my ego thrives from the dark. In this way boredom cannot kill my joy and productivity.

17. Write - Yes, I try to be a better communicator, to express my thoughts easier. This helps me to communicate technical requirements and specifications to others in an easier way. Being able to write code that can be understood by both a computer and by human beings is a skill developed over time.

18. Ability to influence and persuade - Coding, point 3, would be pointless without this ability. Yes, I do influence people. I structure my arguments to make a point through the idea I want to share. As developers, we work with other teams and maybe our goals are not completely aligned so choosing between the authority or the capability to influence it’s a growing.

Thank you for reading this. Really thrilled to start my next adventures and to meet tons of incredible people next year. What an incredible 2019!
🎉Happy New Year🎉

🎄 How to decorate a Christmas tree like a programmer 🎄

Valerica Plesu — Sat, 14 Dec 2019 18:26:06 +0000

Xmas is around the corner! 🎁🎅

I know that not everyone celebrates Christmas, but for those that do or for those that just love Christmas I did an Android application to make this Christmas devtastic!

Why not start and build something using your skills? There are lots and lots of programming languages so why to stick to a single one?

Stack

ArCore for Android. I started with the Sceneform sample found here.
Going through the sample you will learn how to display an arSceneView and how do you detect a plane in order to place different virtual objects.

The next step is to add a bunch of models from poly. Notice that those are published under a CC-BY license. You're free to use them as long as you credit the author.

Compatibility

Android devices with Android version > 7.0

The Outcome

How do you decorate your Christmas tree?

Go ahead and post your Christmas tree! 🎄🎄🎄

Ok Google, How Do I Build My Action for the Assistant Using a Kotlin backend?

Valerica Plesu — Sun, 17 Nov 2019 15:31:42 +0000

Learning is a big part of a coder life, and from my point of view, it’s important to look at programming as a hobby.
Besides the main technology you are learning, there are many other technologies and lots of soft skills. One important is curiosity.
In this article I would like to share with you my experience with how to develop an action for the Google Assistant, using Kotlin. I will focus mainly on the struggles I had using Koltin as a backend and App Engine as a container for it.
All this started with my curiosity about how an action work and taking the extra mile to build an action and share it with the GDG community.

But why the need for this?

Working in the technology area it’s a complex job. Out there, so many tools, architecture patterns and a huge amount of information. Nobody can know everything and you need to choose what you invest your time. My Java background and for the last two years, Kotlin pushed me to try the Google Actions Kotlin library and not to learn and invest my time into node js, no offense here :) Google Actions development is based on node js and almost every tutorial out there is based on it so for me was like challenge accepted!

Small talk

Because Actions are powered by AI, they interact as humans do. No user manual or learning curve required. Google reports that 41% of people who own a voice-activated speaker say it feels like talking to a friend or another person.

Actions on Google is the platform where developers can build Actions for Google Assistant. Actions are conversational interactions that allow users to talk with Google Assistant. Your Action’s users will be able to ask, “Ok Google, talk to . . .” your action name and your Action will respond!

Users don’t have to install anything to use your Action; however, all Actions must be submitted and approved by Google before they can be discovered.

Start design

At a first sight, the set-up process seems a bit hard but Google has broken down the process into an easier process to follow Conversation Design, which comes with extremely in-depth guides to understanding each step of the process. Details here.
If you are at the very beginning stage with Google Actions, I recommend these res1 res2 res3

The Action I build using DialogFlow
Bucharest DevFest is an action intended to help Bucharest GDG organizers to share information about their next DevFest event. DevFests are community-led developer events hosted by Google Developer Groups around the globe. GDGs are focused on community building and learning about Google’s technologies.

With this in mind, I started to develop the action which would be able to share information about what is this event about, where and when would take place and which are the topics.

Here's a sketch of what a conversation with this app looks like:

Project setup and tools
Because I wanted to write the code my way (using Kotlin) I chose Google Cloud's serverless platform App Engine to take care of managing the underlying infrastructure.

I started with their git project template and did all the steps mentioned there.
The first step (already created a new project in google action console, and linked it to a DialogFlow project) is to import the Agent in your DialogFlow project:

After cloning the above repo, you can use IntelliJ to open it and start writing your own code.

The first remark to say is that if you try to run the code locally the used logger (org.slf4) will crash so none of your debugging logs will be there. (this happens because somehow their boilerplate code is some commit behind the library repo.

To fix it you need to add this dependency into the build.gradle file:

compile 'org.slf4j:slf4j-simple:1.6.1'

After this, you can start your local server from within IntelliJ, open the Gradle tray and run the appEngineRun task. In the Run tray you should have an out like this one:
Now your local server is running.

Next, you need to make this accessible from the internet, so your google assistant can access it. To do this I used ngrok to expose my localhost

The third step is to go back in the Dialogflow console, from the left navigation menu under Fulfillment > Enable Webhook, set the value of URL to https://<...>.ngrok.io and Save.

Now is the moment when you are able to test your action using your local webserver.

Now comes the fun part, the coding.

You add your Intents into the DialogFlow console and then you are handling the request in the MyActionsApp class which extends DialogflowApp() like this:

All the string resources are going into this directory

This goes well if you want to distribute your action in different countries.

Another struggle I had was with the default project for the gcloud CLI. Because I had an old project already setup with the Google Cloud, somehow that was my default project.
To fix this I added two new build type to project gradle file

Just set correctly your projectId. (you can check the id in the DialogFlow console).

Another interesting and easy step to be done is to integrate your code with the Firebase Firestore in order to get your action content dynamically. But this is another discussion.

So what do you think? would Google Action be your next fun project?

Thank you for reading this. If you have any questions, comments or funny jokes comment below.

#InternationalProgrammersDay

Valerica Plesu — Wed, 11 Sep 2019 19:50:22 +0000

For all techies out there, Happy 256th day of 2019, this Friday 13.

Let's celebrate it as we all know best, by coding.

Dare to code a new app, a code snippet or whatever you want using a programming language/tool/API you don't know.

I'm learning how to develop apps for Google Assistant and I'm thrilled about it. Here is what I've built: Programmers Facts

daretocode,

And big thank you to all the coders out there changing lives for the better

How was your last on-boarding experience as a new employee?

Valerica Plesu — Thu, 08 Aug 2019 17:34:57 +0000

Hey techies!🚀 I'm cooking a new workshop for Google Actions (actions sdk, dialogflow) and in preparation want to get your thoughts on something.

📍We've all gone through the on-boarding experience as new employees with a company.

I want to know what kind of information you received that was useful and what kind of information you wish you would have received but didn't.

📍Ex: finding info about other teams, where the cafeteria is, where the restroom is, where is the HR team, what kind of benefits you have, etc

Comment below and help me shape this workshop.

Thanks🙏
Your insights will be greatly appreciated!

Soft skills: Coders by Clive Thompson – book review

Valerica Plesu — Sat, 27 Jul 2019 13:59:44 +0000

“Code shapes coders, and coders shape the code that changes how we think, every day of our lives. If you want to create a more humanistic digital world, read this book to get started” - Sherry Turkle, professor at MIT.

On my way to becoming a well-rounded software developer, I found myself reading Coders (The Making of a New Tribe and Remaking of the World) by Clive Thompson.

Why?

The reason for picking up this book was that like everybody else I do read a decent amount of books about technical subjects but what about the remaining part of life as a developer? I do want to equip myself with soft skills that complement technical skills, so this is the main reason for choosing this book.

Content of the book:

The book is written by Clive Thompson who from my point of view has done a very good job by putting down in words who coders are, what they do and what’s the culture of code.
The book is divided into 11 chapters, it’s quick to read and guides readers through the undercovered history of programming and a better understanding of programmers.

As the author states, in a world made of software, programmers are thus among the most quietly influential people on the planet, they are the architects.
We want to understand how today’s world works but first we need to understand who are the people building it, what makes them tick, what’s their personality.

I found out that the first record use of “Hello World!” was in 1972 by Brian Kernighan, a young computer scientist. The idea came watching a cartoon of a chick coming out of an egg, saying “Hello, World!”. Nowadays, every single guide to a programming language has the “Hello, World!” how to do a tutorial.

The author blows my mind multiple times when describing how coders are. An interesting explanation is that “The default state of everything that you’re working on is fucking broken. The type of people who end up being programmers is self-selected by the people who can endure that agony. That’s a special kind of crazy. You’ve got to be a little nut to do it.”

“The programmer personality is someone who has the ability to drive a tremendous sense of joy from an incredible small moment of success”. I do this day by day, and at the moment I quash a bug I’m like Sherlock Holmes in his moments of cerebral triumph.

Trying to dive into understanding what coding is, the author often says that coding isn’t easy, you have to sit alone for hours and trying to mentally inhabit the twisty nuances of a piece of software.
There are no niceties. If there is an error into the code, it just spits out an error message and the coder needs to figure out what he did wrong.
When you meet a coder, you meet someone whose core daily job is of unending failure and grinding frustration. This is going into his mind and personality. Coders tend to be good at thinking logically, systematically.

A nice analogy is that the programmers are “near Sisyphean” - day by day are resigned failure, watching the boulder roll back down the hill… until one day it tips over the crest. And what do they behold on the other side? Another hill.
One central plank of coder psychology it’s a boundless, nigh masochistic ability to endure brutal, grinding frustration. That’s because most of the time they are finding bugs.

I felt particularly attracted by “coding it’s a refuge from the unpredictability of humans, from their gray-scale emotions and needs”. When I do code I’m sure that the computer would execute what I tell him to do, nothing can surprise me. Of course, the computer is a complete asshole, it will not help me and will fail completely and spectacularly for any tiniest error, but still, humans are the ones unpredictable.

Programmers are poets of bits. The author is giving us what’s the culture of a coder. Code is a form of artistic expression, they are giving it freely to everyone who wonders “Hey, how’d you do that?” this way people are going to learn it. All of this went to be known today as “free and open-source software”.

Going page by page, chapter by chapter, the author successfully surprised me by unpacking the coder in different ways, like unpacking a new pair of sneakers. Who does not like the unpackaging process?

Reaching the end of the book it gives you a clear idea about how awesome programming is and why not give it a try yourself?

Conclusion

I 100% recommend this book to anyone. If you are a programmer or you have to work with programmers it’s important to understand their culture.
I enjoyed the book and I hope you have found this review useful.
Thank you for reading this. If you have any questions, comments or funny jokes comment below.

Cooking like a programmer, part 1

Valerica Plesu — Tue, 05 Feb 2019 19:16:26 +0000

The idea for this post and the next ones (yes, there will be a series of articles) came from my passion for coding and cooking. So why not combine both of them.
Both are rule-based and are considered a form of art and science but what I like most is that they leave plenty of room for improvisation (or how I like to say, “I seasoned some personality in”).
This is not something new, but I find myself able to get the similarities between these two and write my own approach about how useful is programming day by day. So, this is my POC.

Background

I felt in love with programming 7 years ago and currently, I have a full-time job as an Android Developer.
I do love the idea of coaching. In my free time, I’m helping others to learn how to code (at MobileAcademy) and I’m an active member of local meetup events (such as women techmakers romania, google developer group bucharest).
Last year was the first time I was invited as a speaker at a well-known conference (devfest) and I enjoyed it a lot.
I’ve got a hacktoberfest t-shirt at #hacktoberfest18 and what I’ve learned is that you should stay positive and show enthusiasm when opening a pull request and accept that your code is not perfect.

I’ve been two times at Google IO event and I found this the most unique conference where you have to go at least once in a lifetime.
Being active in this industry brings you many benefits. I do consider that taking a few days away from the office to participate in a conference is not at all a waste of time.
The mindset I choose to go with is that I can win friends and learn from a variety of points of view, get new ideas and trends, all these impacting my future results.

What I want to accomplish with this series of articles?

I want to learn how to cook based on my programming skills and share programming basic concepts in a funny way, that anyone can understand.
I’ll try to write about basic rules, like the environment, the importance of planning, variables, algorithm, data structures, OOP, app architecture, teamwork, etc. Of course, I’ll do it agile so everything can change :D
I find programming a lifelong pursuit where there is always something new to learn and you need to get as much as you can and also help out the person next to you.
Cooking is not different, and I don’t have big expectations that I will be a great Chef in a few days, so that’s why I propose myself to cook something new every week. (improving my cooking skills week by week, continuous learning).

So, let’s start!

In this article, I will tackle the “Setting up the environment and planning what you want to code! Ups… cook”

The first dish I want to cook is duck breast with orange sauce.

Setting up the environment. In order to start writing code and solve actuals tasks, I need to get everything in place before coming up with a solution to a problem.
So, I start with installing iTerm, AndroidStudio, GIT, android sdk, android ndk, kotlin, sublime text (mac workstation). After everything is setup, I’m ready to go and plan what I need to implement next.

So, with this in my mind, I cleared up the kitchen and everything is in place, as “Mise en place”. Based on my skills I assume that if my work area is clean and my tools are where they should be, I’ll be able to handle this complex recipe.

Planning the work. I like to plan my workday… actually my entire day. If I have to handle a complex problem, I first start writing it down in pseudocode before actually start programming.
I plan the app architecture in advance. I’m thinking of the app specifications and reading a lot about what APIs I’m going to use but in an agile way (things can change). My view has to match my team view, so I need to keep consistency.
I like to write code, but coding is a long run, at each moment there is something from the past to refactor.

Again, I’m using this coding approach to preparing the duck breast. I’m studying about duck meat properties, the ingredients I need for the recipe and extract the steps I need to perform (planning the architecture).

What I’ve learned is that duck is nutritious and delicious, it is lean meat, an excellent source of selenium and zinc, both of which encourage good cellular metabolism.
Duck fat it’s similar to olive oil and low in saturated fat. It’s the perfect choice for a health-conscious diet.

After this recipe, what I’ve learned is like in software, where my app doesn’t work as I’m thinking (bugs are everywhere) my dish tastes a bit strange… but at least looks good :D

Stay tuned for my next steps on learning how to cook like a programmer and discover what software development is like a pro. Stay happy!

Thank you for reading this. If you have any questions, comments or funny jokes comment below.