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
Branding Development Marketing

Find Yourself

Spare a moment?

Teach if you can.

Invest in some time.

Learn as much as you can.

Perhaps…

Share a thought together.

Maybe if you’re lucky…

Trade a skill for another?

Who knows what you’ll might find.

From entry level to fullstack…

There’s always something to learn.

Call it what you want.

The cycle of learning forms teaching.

Imagine and reiterate.

The above with the below.

Apply methods with different contexts.

Lifehacker.

Categories
Design Development Reviews

Sometime it’s not clear

It’s not always clear what to expect when building software especially when you’re reliant on user stories that don’t describe the full story.

But then again, sometimes user stories can’t be clear without some visual concepts what the users needs.

From experience with visual concepts, many users thought this was it, concrete.

Maybe that’s because it’s down to how polished a design concept is.

Depending what you’re target audience is, it should be very basic to explain itself to the user what each element of a concept does.

Factor in the user’s knowledge of what they may currently know to build the amount of detail needed in the design concept.

We all have to remember that visuals are just concepts, therefore there may be some changes in the pipeline that weren’t considered back then and that they may need looking into present.

Trying a different approach without the visuals is another challenge.

So when you’re building from scratch it only makes sense somewhere along the line where smaller components fit together but still don’t describe what they do.

Adding titles, labels, icons makes sense.

Then you start to see a pattern of inconsistency delivered in Agile methodology, that’s where you’re suppose to constantly deliver.

Sometime it’s better to extend and add a sprint to rectify these issues before it gets complicated to work with.

Yes it adds some time to productivity, but would you rather have this or the latter?

Categories
Development Reviews

I have a theory, but correct me if I’m wrong…

Working in the Web realm is fascinating, but does have it’s tolerance.

Balancing many factors that one may not be aware of.

Add that with business needs and growing demands from order of hierarchy.

The cycle of success continues with continuous learning, finding, trialing new tech stacks to building and improving software architecture.

Driven by passion and ambition to self learn, is all that was needed.

Without a software degree it’s pretty hard to summarise.

That you may know more then you think you know, but then again you only know more when you are able to investigate and trial these new ideas.

Must thank those who understand and give the time to let one manage their own.

Lessons learnt and upheld adopting the new, due to valid reasons keeping tech stack consistent for upgrading and maintaining purposes with limited resources.

It’s time to let go of the small and think bigger. Push those boundaries. Invest in the new to increment features and aim to replace the old.

First to explore, first to trial, but wait a second, we have a team with individual mindsets and abilities to do the same or similar.

Teach, train and mentor maybe a new territory for one, but not often looked upon due to time management in many businesses.

So there’s concerns in the blind spots. Noted and mentioned to many, but how and who will address it?

Correct me if I’m wrong, but it’s up to the individuals in the team to embrace the journey together.

Setting aside some time and pushing back on the frequent demands.

Better yet, let the order of hierarchy set some time to continuous review information before passing down the chain of commands.

With continuous review of information, refinement of order become transparent, data become valid and less likely to consume time rectified.

While from the bottom continuing with the business needs in a regular pattern that aligns the learning goals, teaching one another, which is one of many challenging business objectives overlooked.

Certainly a challenge this year, but appreciate able to work in the current conditions.

Categories
Design Development Marketing

The point.

If you invest in a little bit more time, you get a whole lot more in return.

Take this as my experience.

If you take a look closer you will see patterns.

Keeping things generic as possible offers flexibility and new ideas.

Although time does come at a cost, think of it as a return on investment.

When you are finally done, release and track your feedback.

The jigsaw to the feedback will be crucial.

With the feedback, improve those negatives to positive.

You then reiterate and evaluate, eventually receiving the cycle of success.

Statistics will show, performance will grow.

Be patient, calm and collective.

One at a time is the focal point.

There is a journey where we are all involved.

Making the end users experience greater together then the previous or current.

Love to hear your thoughts and comments. Please leave them below, thank you.