A great post about the trap of becoming a senior before you’re ready. Avoid being the biggest fish in a small pond. Read on below.
The ability to filter by multiple tags will elevate my prioritization process.
When viewing a list on all platforms (Mac, iPad, or iPhone), you can filter by more than one tag.
- Mac: Press and hold Command (⌘), then click your desired tags.
- iPhone: Filter by tag, select one tag, then return the same menu for the ability to check more tags.
The “Using Tags” support page by Cultured Code gave a handy example:
It’s useful […] if you want to see all your 🏷 Work to-dos that are also🏷 Important.
The global pandemic induced a mass workplace migration. Many office inhabitants were thrown into the wild remote working paradise. The expected decrease in Covid-19 case numbers will see most people abandon the remote working paradise, but for some, the distributed work environment is here to stay. I’m writing this guide for those who will become permanent remote workers.
I have worked remotely for over 7 years and still find both glorious and challenging. Along with flexibility and control, remote work requires great discipline and support.
Over the next few weeks I’ll be posting on the pillars of remote work success. I’ll touch on inner circle support, time boundaries, self care and much more. If you are interested in learning more about remote work and other related topics please subscribe below.
This is the list of topics I’ll blog about in the coming weeks. I’ll update the titles with links to the posts as I publish them.
1 – The right kind of support – Draft
2 – Time boundaries – Draft
3 – Find a dedicated space – Draft
4 – Remove Distractions – Draft
5 – Structure every day – Draft
6 – Take great breaks. – Draft
7 – Get out and away for remote work success – Draft
8 – Work hard on yourself – Draft
9 – Look after yourself – Draft
These topics are the pillars that have helped me over the years and I’m sure it will guide you in figuring out how to succeed in a remote working environment.
It was a privilege for me to feature in episode 003 of a fantastic podcast called Howzit. The podcast episode touches on remote work, faith, writing, and personal development. I’m grateful to Travis for inviting me.
I published my first blog post on April 16, in the year of our Lord 2012. Since then, eight years and 170 posts later, I wonder how I can use my writing more purposefully. How does one commit to writing in a way that fosters the best outcome?
Purpose helps others understand our actions. Sharing the reason we’re doing things with those who care, helps them motivate us when we’re stuck. Purpose is a driving force that is able to help you stay consistent over decades.
What purpose should you have for writing that transcends your current context?
My motivation is a moving target: To become better at writing, because writing is a superpower. It is true, “The pen is mightier than the sword”. Being great with words could be the difference between life and death. Being skill full in the art of writing has the potential to unlock many opportunities.
For the sake of writing, writing could undoubtedly be reason enough, but I also have a second reason. That is, to grow my community of influence, the network—of shared opportunities.
I hope to use this blog to demonstrate my skills and these are the topics that I hope to cover as I aim to improve my ability to put what I learn into words:
- Software Engineering industry and practice.
- Personal development
With a greater sense of purpose, I’d like to intensify my efforts and would like you to join me, either by creating your own blog or following along and reading mine.
If you’re just setting up a Mac and find the touch bar setup to be irritating. Follow instructions at this link.
I enjoyed this humorous talk on public speaking. Some of the advice feels gimmicky, but if you compare it to what you hear when presidents and leaders speak you’ll see that they all use it, well with a few exceptions.
The main points are
- Be confident
- Combine 3 breathless sentences for dramatic effect.
- Repeat words three times for impact : “My people, my people; my people“.
- Use balance: “In this life, and in the next”.
- Reach for unique metaphors: “Love is a fruit in season at all times and in reach of every hand.“
- Exaggerate a bit for effect not to cover up the truth.
- Rhyming. It tricks the brian into being comfortable with the information given as it sounds so right.
Go ahead and watch it for yourself:
Link to video if the embed above fails:
Carla Harris, Vice Chairman of Morgan Stanley Wealth Management, explains exactly how she got ahead in a male dominated industry.
Here’s what stood out for me:
- Your authenticity is your advantage.
- There are two currencies when it comes to success. 1 Is performance currency and 2, relationship currency. You need both to succeed, but only relationship currency get’s you to the pinnacle.
- She pointed out how doubtful some people are. She learned a thing from her white male colleagues. They were “frequently wrong, but never in doubt”, in other words they had confidence all the time.
- Perception is realities’ cop-pilot. What people perceive you to be is often how they think you actually are. You need to make sure that you make it easy for people to perceive in the same good way you do yourself. You can train others on what they should think about you. How should people describe you when you’re not in the room?
- If you offer that which is not valuable you will not get any reward for it.
Watch the video below
In case the video fails to show, heres the link : https://www.youtube.com/watch?v=yflSZODY6YU
It is easy to define software complexity, but not so easy to define how complex a specific piece of software is. There have been lots of work in academia to find ways to describe it, but these approaches are not generally applied. Complex software directly refers to its effects on the human mind.
The software industry has a few methods for evaluating complexity. A well-known method is Cyclomatic Complexity, by Thomas J. McCabe, Sr. Cyclomatic complexity plots the number of linearly independent possible paths through a program. The reason why more possible paths introduce complexity is this; when changing a program, the maintainer needs to understand and keep those paths in mind to avoid introducing new bugs. Our human brains have limited capacity for the number of options we can consider at the same time.
Along with looking at the actual program, you must also consider the context. One must weigh in the problem it attempts to solve, the domain it targets, and a few other factors. In some cases, you can simply glance and call it complex, but for others, complexity is revealed as you dig deeper.
All software starts as a set of requirements, and this initial phase is often where we sow seeds of complexity. Software Requirements are usually initiated by people who know what they want, but not necessarily how to build it. This may result in oversimplification of the efforts required, which may lead to shortcuts resulting in unwanted complexity. The requirements phase is the first place to root out complexity.
One can’t always blame those who create these requirements, as they are often at the mercy of a complex problem domain. Think about aerospace or naval technology as examples. Certain fields are by nature complex and thus making the systems they produce have a higher level of necessary complexity.
There are two complexity flavours, according to academia. The first one, obviously named, is Essential complexity. It is a level of complexity that is absolutely required for the system to function. The next one, also accurately named, is avoidable complexity. Though these names are clear, figuring out which parts are avoidable takes a lot of time. Software needs to be taken on the road and through all its paces. We’ve seen people use software in ways the designers haven’t thought about forcing one to rethink avoidable and essential. Essential to whom? Avoidable for whom?
Simple processes can produce complex outcomes. Only the user experiences complexity. Why are we writing software? Is it for Business, business systems, end-users, or the next maintainer?
Attributing levels of complexity is a very subjective act. You should take into account all dimensions involved in a systems life cycle.
It is easy to think that complexity is a problem, but as long as a piece of software addresses a set purpose, the complexity is secondary. If the goal is for it to be simple, complexity is primary.
My colleague Charles wrote about the uprising in America, more specifically Atlanta.
“Tell them that a Black life should be worth more than a pane of glass, or a store…”
When they ask you why Atlanta was burning last night, tell them it was an uprising.
If you want a quick answer, you can quote the economist Thomas Piketty
Every human society must justify its inequalities: unless reasons for them are found, the whole political and social edifice stands in danger of collapse.
Capital and Ideology, Thomas Piketty
Tell them that a Black life should be worth more than a pane of glass, or a store, but that nearly a thousand Black lives in Atlanta’s surrounding counties have been lost because a governor refused to take action to protect them from deaths of inequality.
There were fires and police beatings taking place down on DeKalb Avenue not far from where I live. If you know Civil War history, this was where General Sherman began his march to the Sea in 1864.
They will tell you that this 1864 march this…
View original post 758 more words