Professional Documents
Culture Documents
Life As A Software Engineer
Life As A Software Engineer
SOFTWARE
ENGINEER
HUDYA (@PEROGEREMMER)
What does the main key to be a
Software Engineer?
FAITH
LIFE AS A SOFTWARE ENGINEER
Agenda
1. General description of Software Engineering
2. Requirements to be a Software Engineer
3. The spectrum of Software Engineering
4. How Software Engineer collaborates
5. Tips & Tricks to be the Chosen One
General Description of Software Engineering
5M
1. Eager to Learn
2. Understanding the Problem
3. Problem-solving
4. Critical Thinking
5. Leadership
6. Communication
Eager to Learn
Being a knowledge-hungry is good. Knowledge-hungry is
not the same as HUSTLE CULTURE!
"Let's learn something new about javascript "I'd rather spending my weekend sleeping all
within 2 hours on Saturday then I want to day, watching k-dramas, and push my rank to
watch hometown cha-cha-cha" mythical glory"
Understanding the Problem
It means you understand why it is called a problem and
understand what is part of the problem.
WHY IT IS CALLED A PROBLEM
PEOPLE COULDN'T
YOU CAN'T WORK
REACH YOU
• Communicative, being a person to ask something • Silent, keep yourself silent even you don't understand
when you don't understand one or two things. the problem.
• Ensure, being a person to ask something in order to • Act like know it all, thinking about your perspective is
match your perspective with your colleague. right and act like you don't need a con rmation.
LIFE AS A SOFTWARE ENGINEER
• Creating the best • Create a web using • Create a highly reliable • Create a highly • De ne a standard • De ne a standard
database design server side web app using reliable mobile app of environment of testing which
system, how to technology like lightweight tech, with native which used on used on CI/CD.
improve the query. PHP, Ruby, Python, currently Javascript. experience, such staging and • Create a new case
• Creating API, a NodeJS. • Focus on improving as Kotlin. production of testing when
bridge between • Usually creating a the user experience • Focus on environment. new features
database and small tra c web through features. improving the user • Monitoring tra c developed.
Mobile/Front-end. app like company • Create a component experience while spikes • Testing with the
• Focus on internal system, or based UI, in order to through features. tra c comes due worst case to the
Algorithms & Data simple CMS blog. reuse the component • Create a to high user app.
Structure. • Handling between for a lot of future component based activities. • Tell the developers
• Talking with server- logic to the development. UI. • Monitoring log to to change
side lang like database and the • Create a standard • Create a standard understanding something when
Python, PHP, Ruby, user interface. component component how features it's not come to the
Go, or NodeJS. development. development. a ected users. the standard.
Spectrums Software engineering has a lot of colors. Choose what kind of colors to
be your favorite.
HOW SOFTWARE ENGINEER COLLABORATES
DOCUMENTATION
It's very important and every engineer has to understand
how to write good documentation.
HOW DOCUMENTATION WORKS
CONTINOUS DEVELOPMENT
DESCRIBE BETTER THAN IMAGES
You will leave the company one day, but
Images are good, but they could be
your code remains there maybe for a
perfectly combined with text-based.
long time. By doing documentation, you
With documentation, it helps you to
help other people to understand the
describe everything better.
work ow or your code.
TIPS AND TRICK TO BE THE CHOSEN ONE
Email
mhudyaramadhana@gmail.com
Blog
perogeremmer.com
Social Media
@perogeremmer on
Twitter, Instagram,
Telegram, and Github.