Interesting resources for Dynamics professionals from Ignite 2018

Learning never stops, never ends, never finishes

Ignite has a wealth of resources for Dynamics professional.  The problem is not having enough videos to watch, the problem is there is too many and finding the ones interesting to Dynamics professionals.

I have picked out some of the presentations that look interesting.  I haven’t watched them all but I have watched a bunch of them.

This has been really useful to see how the changes, new features and new services (PowerApps, Common data service, Logic Apps, Flows) fit into future projects.

Interesting resources for Dynamics professionals from Ignite 2018

Successful people are constantly learning

Advertisements

Change will make or break your project

“It is always easier to talk about change than to make it.” ~ Alvin Toffler

Change will make or break your project, changes can‘t be controlled your reaction can.  A fixed mindset breaks instead of bends when confronted with change.  Change is constant, some don’t adapt, others adapt enough to survive, a few use change to be successful.  The less rigid and more adaptable you are, the fewer times you get stuck.

Technology, resources, environment and tools change, it costs you time and effort to change but the cost of not changing will be higher.  What was successful in the past, might not be successful in the future.  By focusing on the past, you won’t be prepared for the future.  The past has gone and can‘t be changed but the future is yet to be defined, embrace change and improve your situation.

Code and change

The art of develop lies in the constant adjustments to change

Robust code is decoupled, ensuring it can adapt to the evolution of requirements and manage the effects of change.  Agile development leaves design decisions to as last as possible, giving more time to gather information and decide based on better understanding.

Requirements and solutions evolve, the more detail you uncover, the more feedback you receive the greater your awareness of the problem and the solution.   You can’t capture requirements up front and get a deep understanding without going through iterations of designs and problems.

Project change

A project won’t change but you can change yourself and the approach to be successful.  A project which does not adapt to the changes will fail.  We are servants of projects, they will tell you when it‘s not working.   Think about the pain points, how could this work differently.

Nothing is fixed, people, requirements, technology and politics change, be fluid, formless and adaptable.  Take a flexible approach, what was successful on previous projects might not be successful with these requirements, environments and people.  When you think requirements are certain, you risk creating brittle designs and brittle plans that will break when change happens.

It’s not if change happens but when and how you react.

Projects evolve, the design at the start is not the functionality in production.  This is because the requirements change with understanding and feedback.

Each projects rhythm is unique and the most efficient way of working different.  You have to adjust and keep improving, finding a smoother way to move functionality from requirements to production.

Conclusion

Don’t fight change and don’t wait for it to happen, embrace change and use it as an opportunity for improvement.  Change is not comfortable or easy and involves conflict but through this something better emerges.

Knowing change is coming won’t make it easier because you will need to move past the friction but it’s the only way to make progress

Hosk’s recommended Dynamics 365 and other articles October 2018

Quotes

Some solutions are so complex, only an architect could create them

There are two great days in a person’s life – the day we are born and the day we discover why. William Barclay

Articles of the Month

awesome-1

Great Dynamics 365 articles this month

Programming/Scrum

Other/Business/Leadership/Management

The Hosk – currently reading

The Hosk – last 5 recommendations

Selected  HoskWisdom

  • To a developer, every problem looks like it needs code to fix it
  • All future development roads lead through CDS, PowerApps and Flow. So start heading in that direction now
  • Architecture is where the fun is, Development is where the pain is felt
  • You have to battle with code more than once, to make it maintainable
  • You’re only as good as the code you create
  • Projects approach methodology like people approach religion, they don’t implement all of it and use the bits they like
  • Write great code if you can, refactor when possible but get the job done
  • Technology should not dictate solutions, it should enable solutions

Last months Monthly articles

Last months recommended monthly articles

Hosk’s CRM Developer Articles

A collection of my favorite CRM Developer articles I have written

Write your code, do your job, focus on the details, predict problems

You’re only as good as the code you create #HoskCodeWisdom

It’s easy to get distracted by the noise of work but it puts more pressure on yourself and your team.  If everyone focused on their role and responsibilities, doing their tasks to the best of their abilities we get more done and it will be to a higher quality.

People get distracted by

  • The internet
  • People
  • Are other people doing their job properly
  • Helping other people do their job
  • The quality of the whole code base
  • New tools, new features, new services, new everything
  • New JavaScript languages
  • Is the project going to fail
  • What is the customer doing?
  • What’s for lunch

There will be noise, distractions and under performing people but don’t add to those problems by letting them distract you.  When you become distracted, you are lowering the quality of your work by diverting time, effort and thought to something else or someone else.

Write your code

Do your job first, do it a high standard, work consistently, finish.  Focus on the details and uncover potential problems.  It’s in the details where the assumptions, logic error, design flaws you don’t see until you drill down into the task at hand.

If everyone did their job and stopped worrying or helping other people do their jobs,  process will work with greater efficiency.

Start by doing your job to the best of your abilities, write the best code you can,  so no one else has to worry.

People who make an impact at work are not just the leaders at the front but the people in the engine room, contributing code, delivering functionality in a dependable way, they are the people who reduce the noise and get it done.

What is development?

Writing good code requires solid fundamentals, working hard and focusing on the task.If each developer does this then the project progresses well and confidence builds within the team and with the customer.

Coding isn’t about flashes of brilliance, innovative designs, hero’s saving the day, it’s about team work, graft and grit.  Turning up every day and working towards the goal, one line at a time.  Wearing problems and requirements down with persistence.

Development is everyone doing the basics and pulling in the same the direction, people who get distracted and head off in another directions, pulls the project in the wrong way and slows everyone down.Get your work done and don’t add to the distractions

Related articles