Recognition

It seems apparent, we’re all in it together (teamwork makes the dream work).

Driving behavioural change in ways that one can understand and adapt (questioning).

Excluding the word I and including others (individuals, teams, departments or cross platform).

Making others aware of the context and giving them credit to the situation (a sense of achievement).

Sharing examples of the past reflections to future enhancements/improvements (simplification of complexities).

Assessing criteria to clarifying misconceptions (missing any detail).

Aligning any hasty judgement with an understanding of logics (2 fast, 2 furious – securing knowledge within speed).

Those logics that cements a clear vision (without needing any visuals).

A vision that can be easily executed and can also be extended (need 4 speed – keeping in sync with process and progress).

Clear mind, clear slate, start fresh (ignite acknowledgment amongst others).

Neither right, nor wrong, hear each other out before proceeding, show examples to reason with and let others clearly see what it is that one is trying to convince.

Recognise the distinction between the two.

2 thoughts on “Recognition

  1. Could you please make a podcast with all these futureproofing concepts?

    I’m new to the hot rod dog world of coding and I don’t know where to begin with this rip-roaring brave new world of nethacks.

    Like

    1. You know that’s not a bad idea, I guess I’ve never done one.

      The reality of the world, newer technologies becoming difficult to teach someone from scratch as it requires the primary bases of low code programming.

      Without this, you may burn fast trying to learn it or battle against it to why things just don’t work as they should, due to odd quirks that is usually discovered part way in a process if using a framework, library, programming language.

      If you do want to start somewhere I would suggest learning the structures of HTML and their default uses and behaviors. Then move on to learning CSS and maybe research how browsers also style HTML elements. Then learn JQuery, having a mind set of binding (just like CSS classes) into methods together to create functionality.

      From there learn JS, that’s where you’ll find it interesting. Then after, look into frameworks and libraries to build things quick.

      Also look into their incremental version for each tech stack, framework and libraries. They have continuous improvements from the previous.

      Hope that somewhat helps indecate where to start.

      One day I will try putting something together, but don’t hold me with it as things do change more often.

      Like

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.