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 … Continue reading Craftsmanship vs Continuous Production
Things I’ve learnt…
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 … Continue reading Things I’ve learnt…
Awareness of Communication
There's no problem talking about real issues that have a large impact. Based on day to day activities, if something is taking longer then usual then you've got a problem. Whether it's a long winded process, a hardware or software system, network, or performance issue - all cost time. Take a random day of the … Continue reading Awareness of Communication
Having time spent reviewing code bases and realising where to optimise productivity. Helping out not just the end users, but the developers either sides of the teams. One of the biggest issue with our monolithic system is where to find certain features. This is because of many reasons. Built by different developers all at different … Continue reading New Strategy
Cleaning up the Process
Right now, having spare time is great. Useful to spend time refactoring code bases. For simplicity and legibility sake. Easy for new recruits to understand and easily maintain with a little bit of help from colleagues around them. Scaling at ease while growing phenomenomly. Reviewing some learning materials to picking something new and trialing its … Continue reading Cleaning up the Process
You're trying too hard or the ones that are looking, searching, judging are one requesting way too much, maybe, sometimes on demand, whether that's internal or external. Spotting the difference is another trait. Don't become the bait, but spot it and report it, where there's a growing concern. Maybe there's something more, inbetween the lines, … Continue reading Maybe just…
Generalists vs Specialists
Do you have a spare moment and own a LinkedIn account? When it comes to designing and developing UI in software or websites, I've always tried my best to think of the end users with UX in mind. Sometimes it's not clear from the start, but it eventually becomes clearer during the process. Sometimes it's … Continue reading Generalists vs Specialists
Just don’t judge or assume, always ask.
When in doubt that is or when there are other great talent around you. But when that isn't the case, try going by experience. Then if you don't have that, try learning it on your own. Don't blame on it, you could be doing it wrong yourself. Try finding those that have the experience. You … Continue reading Just don’t judge or assume, always ask.
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 … Continue reading We’re in transition.
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 … Continue reading Many methods, many implementations.