Categories
Design Development Reviews Upgrade

We’re in transition.

Following on from my previous post, we’ve updated and maybe tidied a few duplicates.

There’s also been many discoveries along the way too. Stuff that doesn’t work nor spotted in system, which makes one think are these features ever been used?

Prioritising the ‘must’ from ‘nice to have’ fixed bug features is good, but could be better managed. Questioning whether they are in use or not, and to fix any major issues found along the way.

Of course business doesn’t just stop when there’s a major change, so there’s new features made in the pipeline ready for deploy.

The issue is having merge conflicts, between branches especially if there’s been many tweaks across branches.

Sometimes doing less is as valuable as doing more. So the point to take away here is accept temporary changes inbetween branches.

Yes, it’s not great for the user experience as things may look different between merges, but then again question whether there’s greater value in doing these changes in a time of merging features?

Reducing number of conflicts reduces number of hours spent revisiting repositories to review changes and a larger gain to being productive developing and improving features.

A valid point, do users prefer working software oppose to something just looking nice?

Ideally, best of both worlds would be great, but the reality is, there’s a limit to most things in development and a far greater possibility to revise designs/styles once features are merged and streamlined into few branches.

That’s where we can now develop new features in priority starting with aesthetics.

On a side note, how many developers have worked with Bootstrap 4 and noticed something interesting?

There’s a class for nearly every style, no need to customise the CSS, but for colours.

Why so many classes?

It also reduces the amount of conflicts found across the system when styling with classes especially if you’re not used to CSS (from an entry level) or the system if it was made before your time.

It’s also safe when upgrading a system, if a team were to use existing classes instead of custom classes or CSS.

Categories
Development Reviews Testing Upgrade Web Technologies

Many methods, many implementations.

Just like in coding there’s many methods, there’s also many implementations.

From NuGet to NPM, to CDN’s.

A mammoth system using all three can get confusing very quickly.

Let’s start by the most famous framework out there Bootstrap!

Imagine there are different variations of it.

The original, the Sass, the older version (just because it was release with a version name), the third party types (usually plugins that provide additional functionality with their version of compatibility to Bootstrap).

And let’s associate this is within NuGet.

Then bring in NPM an alternative, where front end tech stacks can be searched online and installed through command lines using webpack or something similar to bundle and serve.

Of course you may find Bootstrap in NPM and many variations of it, so be careful.

Then add the CDN, often used to serve code from different servers across the globe for performance boost.

It soon becames apparent there are multiples of frameworks or packages being used.

Then you’ll find them also added in different places, let’s say in different pages.

It really doesn’t get any easier and wondering how it became like this is probably best to ignore and forgive as there could be multiple factors involved.

So the aim is to consolidate the variation to one and keep any plugins used by checking their compatibility.

Where there’s multiple implementation, replace it with one direct access checking it’s version in the process or upgrade it to its latest.

In an ideal world, keeping on top of version control is an advantage.

Developers can stop hacking and develop features faster and for users to gain access earlier.

It was time to address this mess, for our development purpose mostly, but also our users.

Allow me to explain.

In development, developers often find using a framework and looking at new online documentation just because it’s available.

Usually with the less experienced developers you may find them hacking their current version to look or behave the same as to the online documentation.

That’s a no no right there, don’t even go there situation.

Developers should check their current version and find the relavent document version and work from there.

Then there’s the fact of customised features built on top of the framework.

This is the bit that can get complex, if not done the Bootstrap method using it’s classes.

On the other hand for the users, it would be a big performance boost.

Again, allow me to explain.

Refresh rates feeling like a flicker rather than a loading spinner.

But that also depends on the scenarios.

If a user is just loading a page that’s great.

If a user is querying the database it could take some time, depending how complex the search is and how much data is there.

So expect loading spinners there.

If it’s a simple search with very little data to filter from, expect a performance boost.

Apply the users to busy environments and you may find an increment of performance a cross the floor.

Categories
Development Testing Upgrade Web Technologies

Fascinating or some what frustrating?

So many courses from different providers.

Which ones are politically correct?

Spending time, involves patience.

As we grow, time feels short.

It’s not always a simple as it looks.

Sure you can follow…

But there are obstacles along the way.

The kind that are not transparent in guidance.

Lessons learned, it will never be.

Acknowledging this…

The cycles of improvement are never-ending.

So the main thing to take from this…

You’re in control, you can’t please all, but you can align the balance with the majority.

Simplify processes not just for yourself, but for everyones case.

With simplicity comes flexible, growth, speed and expansion.

Navigate the play field.

Be your best in the given circumstances.

Die trying, you may get lucky.

Categories
Reviews

I left the process.

Finally finding out you’re the only one with a technical mind, a logical system thinker.

Trying to make ends meet and continuing to learn as much as I could with the limited time I had in and out of office hours.

I didn’t see any clear opportunities left after knowing the learning qualifications were in another’s name.

The situation was just getting worse hiring external Back End Developers and my role slightly moving towards Project Management – not something that really interested me, but I had no choice.

I was at a breaking point; realising managing external developers is a nightmare. Set deadlines and external developers not responding in time for client expectations.

It was that time; I knew I couldn’t do anything more and thinking about the other colleagues in the moment of time and my personal activities – like my sister’s wedding preparations coming up…

I decided enough is enough; a much advance developer is needed for this role and with this in mind I handed my notice and continued to work till the end of the process.