Interesting thoughts this morning when I am brewing my cup of coffee. When dumping my coffee grounds to the bin and I am thinking how much of coffee waste do we produce per as a coffee drinker.

How Much Coffee Waste Do We Produce?​

According to the SCA, the “golden ratio” for brewing coffee is 55g per litre. This works out at just under 14g for a 250ml cup. While this might seem individually insignificant, billions of cups of coffee are consumed every single day.

Waste in Coffee Production​

So why is coffee production so bad for the environment? The decomposition of coffee waste in landfills generates greenhouse gases and whenever these are dumped into landfills, they create methane which are more harmful than carbon dioxide

Reusing Coffee Grounds At Home​

As what I have been doing, majority of used coffee is often thrown to the bin without being separated or treated. I did some googling and found some good ways of reusing coffee ground at home

• Coffee grounds make great fertilizer because they contain several key nutrients required for plant growth. They can also help attract worms and decrease the concentrations of heavy metals in the soil.

• Adding compost to your garden can significantly improve the health of your plants. Coffee grounds can help increase nutrient levels and decrease the greenhouse gas emissions of your compost.

• Like other insects, fleas do not like coffee. Bathing your pet in used coffee grounds may help keep fleas at bay.

• Coffee grounds can help absorb and eliminate odors from your refrigerator, gym bag or smelly shoes. Using them as a hand scrub can also help remove lingering smells from onion or garlic.

• Coffee grounds can be used as an abrasive cleaner. They can help sanitize and remove buildup from sinks, cookware, grills and other surfaces around the house.

• Coffee grounds can be repurposed into an exfoliating scrub for your face and body. They help remove dirt and dead skin cells and promote overall skin health.

• Coffee grounds contain compounds that are toxic to many insects. You can use your coffee grounds to repel mosquitos, fruit flies, beetles and other pests.

• Coffee grounds may help reduce the appearance of cellulite by breaking down fat deposits and increasing blood flow to the affected area.

• Use coffee grounds to weigh down the ashes in your fireplace before cleaning. This makes for easier ash removal and less mess.

• Coffee grounds can be repurposed into an exfoliating scrub for your face and body. They help remove dirt and dead skin cells and promote overall skin health.

• Coffee grounds contain natural acids and enzymes that help tenderize meat and enhance its flavor.

• You can use coffee grounds to buff out scratches on wooden furniture and darken them to match your existing finish.

• Coffee grounds contain caffeine and antioxidants. When applied to the skin, they can help prevent aging and reduce the appearance of dark under-eye circles and puffiness.

• Coffee grounds contain compounds that can raise blood cholesterol. Consuming small amounts on occasion is fine for most people, but they may be problematic if consumed in excess.

Vaper since Year 2015. Can't remember the hype of vaping few years back. Been using various kind of mods, box-mods, squonk mods. So far, the only still surviving is my Taifun - Scarab ( Skarabäus) when I first bought in Paris. Together my favourite Pico RTA. Could be I am tired of chasing for the latest stuff out there, just like how we are chasing for gadgets and shit. Sticking with the same old mod and same old RTA.

Taifun - Scarab (Skarabäus)​

The Taifun Skarabäus Pro is characterized by its relatively simple operation, which excludes the usual disadvantages of a mechanical switches such as arcing, carbon build up, and performance degradation over time. The benefit of the switch design in the Skarabäus Pro results in fast and instant power ramp up for strong hits and consistent performance over time.

Pico RTA​

The Pico RTA by YellowKiss (The Vape) The Pico by YellowKiss (The Vape) in Korea, is an exclusive rebuildable tank atomizer that is designed for some of the most incredible flavour reproduction available from any tank on the market today, packaged in an incredibly small size!

Recently I have been looking for something new to try on. How about baking a cake? Since the cake I like the most is cheesecake, google up and found this in Youtube. Gathered all the ingredient and baking utensils, honestly it's really not hard to make a cheesecake. I would suggest to give a try! Updates: I have been messing around with the same recipe, just giving a try on switching out the brands of cream cheese, percentages of sour cream and I am having fun!

Not long ago, I have been introduced with Python.

Python language was not hard to understand but is kinda hard to write good codes with Python especially for a person like me who do not have good IT knowledge.

But thanks to the Internet, there are plenty of resources online that helped me in better understand the programming language.

As my job are more towards on process automation, what we need was a scheduler that enable us to make a schedule / trigger that's calls out routine to complete business task.

I am using Flask to fire up a python server, once the server is ready in local-host to receive request. Then, request can be submitted through REST method which can direct our flask app.route to call out python method and function that has been coded to do the job.

What I learned and understand so far...

1. Divide and Conquer​

This stay on the top as it's the most important principle, for instances when we are being provided with a business case with huge list of requirements, we started to confuse ourselves and often the solution came up straight away potentially not the best solution. The idea of divide is to decompose a given problem into two or more similar, sub-problems, which then we conquer by composing solutions to the give problem.

2. Increase cohesion​

A good object oriented design must be loosely coupled and highly cohesive. This design principle have been created based on the idea of Loose coupling and high cohesion. Don't mixed up with Cohesion and Coupling, as cohesion refers to what a class, module or function can do. Low cohesion would means that it does great variety of action being unfocused on what it should do. Another way to think of this is to have something that could not be broken down further, and should be doing only one thing.

Example of Low Cohesion:

Staff
check_email()
send_email()
email_validate()
get_salary()

Example of High Cohesion:

Staff
-salary
-email_add
set_salary()
get_salary()
set_email_add
get_email_add

3. Reduce coupling​

This refers to how related or dependent of two classes / modules. Low coupled would mean that changing something in major should not affect the other. High coupling would increase the difficulties of code maintenance, a change of module usually forces a ripple effect of changes in other modules. The lesser dependencies the better

4. Increase abstract​

Abstraction is one of the key principles behind many of the OO design principles such as below and is the hardest in my opinion. The idea is to have a simplified version of something technical and the goal is to reduce complexity.

• Inheritance
• Polymorphism
• Composition
• Benefits of abstraction
• Code is easy to understand
• Manages change and the effect of change
• Creates cohesive code – it finds common fields
• Create loose coupling

https://en.wikipedia.org/wiki/Code_Complete

abstraction is the ability to view a complex operation in a simplified form. A class interface provides an abstraction of the implementation that’s hidden behind the interface

Some examples below:

Concrete

place_triangle(triangle) place_square(square) place_circle(circle)

Abstract

place_shape(shape)

You will just lock down the attributes like x, y, areas

5. Increase re-usability​

Think of writing codes as re-usable as possible, the challenge part could be keeping the balance on spending more time to design and write a general function. I see this as a investment of time to reduce the future time needed to go back and understand the piece of code.

6. Design for flexibility​

Think ahead and anticipate that the fact of there will be a change in the future, as and when the business grows, requirement changes and more. A-lot of time when comes to an end of project, I realised that I have to add some features and based on the way I have written my codes, that's not possible. Ending up spending more time to re-write and re-design the whole program.

7. Anticipate Obsolescence​

• Avoid early release and version of software
• Use software from reputable companies
• Use as few external dependencies as possible
• Avoid poorly documented or maintained projects

8. Design for portability / scalability​

Think ahead about possibility to have your program in other platform. Things can get harder when your client based grows and you do not have the ability to scale your program or port to another platform.

9. Design for testability​

This is important especially for larger code based project. Design the code in a way that you are able to test the code. Think of test case, functional test, unit test, and find out a way to test the code.

10. Design defensively​

Idiot proof your code. Good error messages, handling all the invalid input, handling wrong output.