update

Author: diviyeshpatel

blog/_posts/2022-04-20-things-ive-learnt.markdown

@@ -0,0 +1,35 @@
+---
+layout: post
+title:  "Things I’ve learnt…"
+date:   2022-04-20 12:15:00 +0000
+categories: career, design, development, profession, reviews
+author: Diviyesh Patel
+---
+
+Identifying problems and providing solutions…
+
+Problem: Teaching only works when the learner is eager to pick up and trial new things outside their comfort zones without worrying about deadlines around time management.
+
+Solution: But of course is aware of time taken to complete the task in hand, informing those that need to know how much time and effort it has taken.
+
+Problem: There are certain types of people that are comfortable explaining vs demonstrating. It’s becoming rare to experience both, explanations and demonstrations at a time of reaching out for help when in-between tasks.
+
+Solution: Arrange a time when it’s suitable to go through and discuss the issue and possibly pair programme to find a solution together.
+
+Problem: There are multiple ways to do the same things in programming, some are very long winded, some are coupled into codes and others copied and pasted from elsewhere.
+
+Solution: The best way is to keep it short and simple just so it’s easier to read and understand without having to write comments inside the code.
+
+Problem: But not everybody is the same, so expect people making things different unintentionally.
+
+Solution: Taking a moment to spare some time training individuals and possibly if there are multiple methods to execute the same feature then maybe discuss the best approach to do it and document it as a guideline.
+
+Problem: Now when dynamics change more often, it becomes harder then ever to keep on top of changes made by others especially those that come and go.
+
+Solution: Go the extra mile if you have a better understanding of what is required by evaluating with teams and possibly rectifying the issues sooner then later.
+
+Problem: Then you have other issues appearing when certain members are trying to improve features that are already agreed with and working as expected with the end users.
+
+Understandably… keeping things consistent with UI, code bases, folder structures.
+
+Solution: These types of changes should ideally be left on a separate branch and thoroughly tested with multiple people before merging into the master or release branch – just think of it as a larger incremental change. E.g. v.1.0 to v.2.0

blog/_posts/2022-06-09-wheres-the-transparency.markdown

@@ -0,0 +1,25 @@
+---
+layout: post
+title:  "Where’s the Transparency?"
+date:   2022-06-09 07:18:00 +0000
+categories: planning, reviews, theories
+author: Diviyesh Patel
+---
+
+Another key element along with communication is transparency.
+
+It’s great communicating information between people, but where’s the transparency around it.
+
+Allow me to explain.
+
+Communication can be easily be lost in translation and also be misunderstood.
+
+It also gets harder with groups of people in meetings, leading to more complexity and become notorious for multiple meetings.
+
+For the purpose of having a meeting, each meeting should conclude informative information, improvements or solutions.
+
+Meanwhile in meetings taking a minute to pause, listen, observe and take information on board, can also help improve the next response in line of communication aka feedback.
+
+Sometimes trying to make a point across can sound negative, but with reasons it helps ease the situation and makes one think more about the point of concern.
+
+Point of concerns shouldn’t be a blame game, but a valid concern that should lead to providing solutions on improving the situation.

blog/_posts/2022-06-25-gimmicks.markdown

@@ -0,0 +1,45 @@
+---
+layout: post
+title:  "Gimmicks"
+date:   2022-06-25 06:19:00 +0000
+categories: activities, career, theories
+author: Diviyesh Patel
+---
+
+As we get older, we get wiser.
+
+We tend to have less time as more responsibilities grow.
+
+In time those have to be sorted by priorities.
+
+Additional drivers causes conflicts.
+
+Those are being talented, being kind and helpful where needed.
+
+Day to day activities include solving many issues and answering many questions.
+
+Questions on the 5 W’s and H of course.
+
+Most of the time, just being present helps, just don’t ask how.
+
+Because of these attractions, there’s also noise from doing the current task in hand.
+
+It could be internal or external. Being at work or leisure.
+
+It could be anything unconfirmed and mentioned later.
+
+Quite frankly, if it doesn’t do any favours then don’t even bother.
+
+You’re wasting you’re precious time.
+
+Time that costs.
+
+Shame it sounds harsh, but that’s reality.
+
+Now, if you’re thinking the opposite…
+
+To make a difference, you need to continuously chase it.
+
+No matter how hard it is, never give up.
+
+One day you’ll get lucky.

blog/_posts/2022-07-14-craftsmanship-vs-continuous-production.markdown

@@ -0,0 +1,33 @@
+---
+layout: post
+title:  "Craftsmanship vs Continuous Production"
+date:   2022-07-14 08:45:00 +0000
+categories: design, development, planning, reviews, testing, theories
+author: Diviyesh Patel
+---
+
+In a line of duty, when duty calls…
+
+Quality craftsmanship is needed when many issues occur.
+
+Sometimes having to question almost everything to understand the start to end process.
+
+Usually when user stories change more often during production and the need to get more clarification.
+
+Whilst keeping on top of demand, it’s urgent – meeting sprint goals.
+
+Think of it as a layer of cake.
+
+Multiple levels of complexity.
+
+Built by different individuals.
+
+Now try adding more features on top of existing layers of complexity.
+
+It becomes difficult.
+
+Allow time for cleaning up the process rather than what’s the next thing to do, either to keep people busy or to get things done.
+
+By doing this, it allows others to contribute more easily until the next cycle of issues occur.
+
+To fix this issue, repeat the method above.