DEV Community: Wends

Working From Home

Wends — Wed, 20 Jul 2022 19:54:39 +0000

I've been an office employee for over 7 years, I was employed on my first ever job and being in office, I was thought that leaving yourself idle even for just minutes is bad, boss always have to look at employees if they are working in front of the computer, being a programmer in the office, if you're not busy on your computer 8 hours a day you're not being efficient. Because of this, I had to shut down the world around me and make music my fuel for coding. This was me for over 7 years, time in and time out is one of the most stressful things every weekdays, commuting is just pure pain for me as I'm not a morning person and I have a hard time waking up in the morning even as a child. There are times when I have stress at home that I just can't leave at home making me feel grumpy and make bad vibes ooze out of me.

Last year I went fulltime working from home, and it feels a lot lighter for me, I can take breaks when I feel stuck and it's so mind-blowing, all along, when I feel stuck I stress about it as I had to fiddle on my computer because it feels like someone is always watching and just waiting to pounce, it gave me anxiety and my hair fell out, turned me into a stress-eater, when all I need is a break, stay away from the computer and think about the course of action I can make to solve problems, with this I'm still able to perform well and was more eager to focus and finish tasks. I'm actually very surprised that I'm able to scratch out things and start anew with better solutions rather than making ends meet with the current action I'm taking making everything look hacky, terrible and unclean.

With this I realize that I love working from home, I love it when it's more output-driven rather than fiddling in front of the computer when all you need is to step away from it and think without anyone judging.

Today I had some mental and emotional stress I just can't get out of, I also have a meeting I need to attend to, but I excused myself out of it today and just focused on working because with the mental and emotional stress I just can't function as a social person. Am I the only one like this? Is this entitlement? I actually feel a little guilty doing this... How do you cope up when you go through this?

New Android Splash Screen

Wends — Wed, 29 Jun 2022 06:03:15 +0000

I'm a fan of splash screen, for every project I try to create I always wanted to apply splash screen because it's fun to look at! But I never really liked the previous version of applying it so I don't apply it much. But yesterday, since I started working on my portfolio again, I encountered a new good way to implement it.

Put this package in build.gradle (module) in dependencies

implementation 'androidx.core:core-splashscreen:1.0.0-beta01'

If you can't see 'styles.xml' in your project, go ahead and right click on your res folder and create a new xml file, name it as 'styles.xml' and put this code.

<resources>
    <style name="Theme.App.Starting" parent="Theme.SplashScreen">
        <item name="windowSplashScreenAnimatedIcon">@drawable/ic_stat_shop</item>
        <item name="windowSplashScreenBackground">@color/teal_700</item>
        <item name="postSplashScreenTheme">@style/Theme.OnlineShop</item>

    </style>
</resources>

The windowSplashScreenAnimatedIcon is your animated or simple logo, the one you want to see in the middle of your splash screen.

The windowSplashScreenBackground item is the background color of your splash screen, mine is just from the color xml file but you can also put there the background color of your ic_launcher/logo if you have one.

The AppTheme in your postSplashScreenTheme item is the theme name your project is currently using, you can find it inside themes folder inside the themes.xml files.

Add the style to your mainactivity in androidmanifest:

<activity
            android:name=".MainActivity"
            android:theme="@style/Theme.App.Starting"
            android:exported="true" >
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>

Lastly, don't forget to add this code before setContentView(R.layout.activity_main);:

SplashScreen splashScreen = SplashScreen.installSplashScreen(this);

or else you'll encounter this error, as I did:

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.test.onlineshop/com.test.onlineshop.MainActivity}: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.

How I Understand SOLID Principles

Wends — Sat, 20 Feb 2021 16:39:06 +0000

SOLID principles consist of five principles namely:

Single-Responsibility Principle
Open-Closed Principle
Liskov Substitution Principle
Interface Segregation Principle
Dependency Inversion Principle

First, what is principle? According to google, one of the meanings of principle is:

a fundamental truth or proposition that serves as the foundation for a system of belief or behavior or for a chain of reasoning.

So, as how I understood it, these principles are a plan of actions that serves as a foundation for a system.

What exactly are these principles about?

Here we go.

Single-Responsibility Principle

From what I've learned, the only thing that I remember is that a class should only have one job.

If I have to explain to someone who doesn't know anything about programming. I think the best explanation is comparing this definition to a real life object.

I think the best fit for this idea is a faucet. You turn it on and water flows out, you turn it off the water stops flowing, the faucet's only job is to control the flow of water and nothing else. You can't make it work like a sink or a plate or any other things, because it only has one job.

Open-Closed Principle

The key meaning for me is open for extension but closed for modification.

A class should be extendable but close for modification. Alright, so it's like a parent and child relationship. You can never modify a parent's attribute but it can always be (at this situation) be inherited by the child.

Liskov Substitution Principle

Before we proceed, who is Liskov first and why is it important this principle should be named after this name.

Liskov is a computer scientist. According to wikipedia

The Liskov substitution principle (LSP) is a particular definition of a subtyping relation, called (strong) behavioral subtyping, that was initially introduced by Barbara Liskov in a 1987 conference keynote address titled Data abstraction and hierarchy.

Liskov substition is about substitution of related classes, so, if a child class is derived from its parent class, it should have the ability to become a substitute of the parent class.

So like for example, the trackpad and mouse, they bought can be substitutable with each other because they have the same functions needed to move the arrow around the screen.

Interface Segregation Principle

A class should never be forced to implement an attribute from an interface which the class doesn't need.

Consider it like, when you create an interface for game object movement, the main game object (the player character) has the ability to walk, run, climb and dash, adding these to the object movement interface will violate this principle if this interface will be implemented as well with a patrol type enemy, which doesn't need the other functions other than walk or run.

Dependency Inversion Principle

This allows decoupling... but wait, what is decoupling?
According to google, decoupling means

separate, disengage, or dissociate (something) from something else.

Hmm.. I still find this vague. If anyone can explain this to me like I'm a 12 years old, please do. But I will update this later if ever I get the whole idea.

I read SOLID principle from https://www.digitalocean.com/community/conceptual_articles/s-o-l-i-d-the-first-five-principles-of-object-oriented-designhttps://www.digitalocean.com/community/conceptual_articles/s-o-l-i-d-the-first-five-principles-of-object-oriented-design