Tag: Experience

Categories
Practical Reviews Theories

Uncertainty?

As human beings we assume a lot, but realising after it’s not the case anymore.

We accept those that have worked longer in employment to know more.

But when we talk about agendas, we realised that’s not the case.

Opening up and talking about topics we enjoy can show how in depth knowledge we may know and also highlight to those that may didn’t know.

But it’s a start.

By accepting they don’t know raises awareness to those that can teach. Be open to understand why we do certain things in the way we do.

There are concept designs, there are many theories on different agendas, then there’s the practical side of implementation with time limits.

The puzzle is knowing each strength and to pull together our minds to solve existing problems in the manner of time.

Continuous reviews draws continuous improvements, adds value across the board.

Change is unavoidable, but can be greatly rewarded in time.

Categories
Reviews

Quick Changes

There are times when things need completed urgently.

But there are methods to go about it.

First think about the 5 W’s.

Who, what, when, why, where.

Apply this logic to one of your tasks.

The ‘who’ will factor the ‘how’ situation, so don’t worry there.

But wait just there!

That’s great for adding features.

Anyone thought about removing features?

Check first if there are other features around the feature you’re about to remove.

If it’s the only feature there, question yourself again the following…

Does it look odd?

Before removing a feature that’s self isolated, try creating a replacement feature.

Without these scenarios, things will turn out half baked.

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.

Categories
Web Technologies

Every business needs it…

When scaling as a business, usually there’s a pattern of manual processes that requires time and effort in which usually becomes repetitive processes.

This is where businesses need to start building automated processes to cut out the need for manual tasks.

It allows the average person to work on something much more meaningful and with that in mind discovers new ideas and and a keen willingness to go beyond personal interests to discover more.

That’s the reality the average person needs to know.

Categories
Reviews

Event Driven Architecture

So here’s where my head is at… from working on MVC (modal, view, controller) using JQuery and JS to manipulate single pages to building reusable components and converting the current state of software to single page application… was something on the horizon, but yet not discovered – knowing/ hearing the tech industry is shifting in that direction.

The new process reduces the amount of callbacks to the servers, which on a large scale, is a huge factor for medium to large scale businesses that rely on online activity every day.

The main positive impact is saving server processes which leads to less server maintenance and the amount of servers processing.

Preventing servers from computing overtime or overclocking, which leads to increase in heat and burnout – one of the main reasons why servers need a maintain temperature room.

The new process allows online users to process the data from client side and then return the data back to the servers.

The end result is fast and efficient, browsing experience.

Here we are scaling up as a team, thinking on decision what is possible and what are shades of gray.

As we build, trail and error, finding problems along the way and realising there are many methods to get to the end goal.

The main issue lies in the decision making, which path as a team we should take given what other problems may occur when scaling applications up.

When you get to the specific details on how to pass data around components to manipulate and store gets complex, dealing with a framework that’s new and gives options, but yet as a language executes on load.

Welcome to event driven architecture…

Categories
Reviews

Tackling programming languages from the past

Tasked to solve – is pretty much what one has been doing to date.

Not knowing, but yet comfortable challenging them while time is ticking away.

Rewind back to years, where self teaching new programming languages was ever so daunting.

The instincts of knowing a language that would update in increments or a full re-write that would extend maintenance time and having to explain that up the chain.

Working with PHP this week and some experience of WordPress remembered in the past – felt like a task that one should attempt, be it if one has only touch the surface of this language.

The attempt was successful and the feeling of confidence has gained tremendous.

So the lesson learned here was be calm and carry on.