Here’s a second part of february and here are my list of articles i’ve been reading to improve my general understanding across different domains. I figured these are some articles that I thought are useful to share with my readers. Not the toughest or most technical to read, thus very digestible and pleasant to understand; allowing you to be a better version of yourself rather quickly and effectively. Remember, it’s not about going from 0 - 100 in a sprint. Keep me accountable to continuously learn as well!
It’s about going from 0 - 10,
10 - 20,
20 - 30… and so on until reach 100.
Build sustainable habits through gradual progression.
Between stimulus and response there is a space. And in that space is our power to choose our response, and in our response lies our growth and our freedom. Reactions are instinctual with no filtering process. Where as a response is a deep breath, a pause, or a brief moment of mindful presence. Emotionally intelligent people knows how to leverage that space to maintain calm.
In stressful situation, be mindful, pause, then consider a thoughtful, and compassionate response.
To be successful in our interactions with the people around us, continue to respond to each interaction instead of mere reaction.
That frees Fridays up for life’s many delightful chores — like visits to the DMV. “For instance, today we’re going to go and get our license plates,” Parlow says.
But that also leaves time on the weekends … for the weekend.
This approach slashes off unproductive hours in office. This allows employers to expect the same quality and quantity of work to be delivered with 80% of the time available. This gives employees motivation to get their work done in expectation for a longer weekend they may receive. Now, their benefits are directly correlated to their productivity at work. It is interesting to see how employees’ motivation and morale at work is, one way or another, correlated to amount of control they are able to exercise in their day-to-day work schedule.
Dan Price the CEO and founder of Gravity Payments chanced upon the issue which a friend of hers whom works in the same city as him actually had her rental increased by 200 dollar and is struggling to pay her own bills. He was angry how the world has become an unequal place, and it suddenly struck him that he is actually part of the problem. His friend actually brought home to him that a large majority of his 35 employees actually faces this similar issue in which he decides to change that.
The solution by the boss is actually to raise the min wage of all his employees to $70,000 in which some 30% of them actually have their pay doubled over night. This definitely left some distaste w their senior employees concerned that it will make the employees complacent and company uncompetitive. But that hasnt happened. What happened was that employees started to pull more weight, in which now the senior management can actually now take on the leaves that they are entitled with. Also, the revenue of the company doubled as well.
Raising salaries didn’t change people’s motivation - he says staff were already motivated to work hard - but it increased what he calls their capability.
Instead of going to work to think about making money, now they become focused on “How can i do good work?”
Such a story always leave me wondering how realistic and possible is this approach? Many did mentioned at the end of the day, it is just business; though i wonder if there’s a way to allow the business you create be a platform for a bigger voice to the business world: the end goal is not about earning MORE. The end goal is to develop people to produce world-class services in which we are adding value both to the society and most importantly, to the people through whom you provide your company’s service.
With a fair compensation and a culture that places people development as its core values, that could be of many steps, the one step towards a work culture that people actually enjoys and seeks after.
I guess in such a chaotic world, the heart posture that sits best with me is one that’s kind; One that seeks to do onto others what you want others do onto you.
- Five people to look out for affiliation marketing guidance
- Shawn collins
- Tricia meyer
- Kim Rowley
Essentially I think learning is fundamentally Pain. You have to take on the pain before the learning can alleviate it, if you try to skip the pain then you have only a superficial idea of what you’re talking about.
There are five key types of language constructs:
Structured: if, if-else, loop, function, switch without fall through
- Better understanding of what is structured programming
- Strive for clarity in code:
Local Goto: goto, continue, break, early return, switch with fall through
Program-wide Goto: setjmp/longjmp, exception, finally, yield, coroutine
System-wide Goto: blocking, non-blocking async callback, device input, framework
Come From: come from, aspects, dependency injection, destructor, defer
- Vue 3.0 has improvements in render time and speed.
- Decrease size of VueJS projects.
- Increasing maintainability as they transit from Flow to Typescript
- Compiler rewrite also includes source maps that will indicate the location and line number of the error.
- Vue 3.0 will be platform agnostic and will not assume web features such as Node.js on its main build.
A very clear and concise article about how we should name our code objects.
Firstly, be consistent with the naming of a single concept. If you wish to name a concept of getting user details from the Database, name it as “getUserProfile”, “getUserAge”, “getUserObject”. You standardise any fetch methods to start with “get”. You do not wish to have different naming such as: “fetchUser”, “queryUserData”, “searchUserProfileInDB”. Negative demonstration.
Second, the name should communicate the concept it is trying to describe to the broadest audience possible. It should not be left to the reader to interpret the intent of the name, in which provides understandability.
Third, the name should be specific and not overly vague. Example you do not wish to have is such as: “userHandler”.
Fourth, the name should not be too long or too short. Too long will usually be a good indicator that the function or the name is doing too much (Violating principle of Do One Thing). Too short and perhaps goes back to the second part about understandability.
Fifth, the name should be searchable, thus it can be easily searched across the code base for clear renaming processes. Adding onto point 4, names that are too short can impact the searchability of the name.
sixth, the name should be pronounceable for everyday communication, relatively unsurprising and unique. You wouldn’t want a name so tedious to spell and write developers have to consistently reference to check the spelling of a variable name.
Lastly, the anme should not be clever or rely on temporary concepts. Remember the point 2 about understandability?
When in doubt, choose names that are literal and dry.
The process of using what you build yesterday to help build bigger tools today is called abstraction.
While computer science has very little to do with snowmen, it has everything to do with patterns.
“Like a fractal, we will same patterns reoccurring in deeper and deeper shades of abstraction, and as we learn more, our tools will begin to work on many different levels simultaneously. “. That is the power of abstraction. These patterns are context-agnorstic, and thus applies at different levels.
We will go deeper into this book and what we can learn from this in another post (Look out for this space)
Under the topic of devops:
How is the architecture done right.
What tools are they using.
What are these tools and what purpose do they serve?
Did automation helped them? In what way?
Continue to learn through books! Find your books here.