Small Teams Should focus on Dev not Ops 😱
You can read the article here https://alnutile.medium.com/small-teams-should-focus-on-dev-not-ops-63d7938a314a
Enjoy!
BETA: This is a Code Heavy Read :)
Not all apps need to be an SPA (Single Page Application). Sure they have their place but in most cases the task might benefit from just a Blade template and Angular widget. This saves you from having to write an angular route which can be a tedious duplication of work. Also Blade is fast and fun to work with.
You can read the article here https://alnutile.medium.com/small-teams-should-focus-on-dev-not-ops-63d7938a314a
Enjoy!
As a freelance developer, my relationship with clients extends far beyond coding. The engagement is educational, helping clients become efficient product owners, understand the value of iterative development, and adopt a proactive approach to Quality Assurance (QA). Also on my end making sure I really understand their domain, their goals and help break down those goals into realistic achievable features.
While I may get paid to code, my ultimate goal is to build the right features. And this is rarely if ever exactly what the Product owner expected.
Read more https://alnutile.medium.com/a-developer-must-help-their-client-learn-to-be-a-product-owner-e178435899d1
Whether you are working Waterfall, or Agile we still need to quote out the time it will take for new features . We still need to give the product owners, or the people with the money, a sense of timing. And it is this skill or lack thereof that drives the experience we are going to have when we code.
Other links
https://martinfowler.com/bliki/ShuHaRi.html
Recently the Zaengle team was asked to look over an existing Laravel application and give a review of the overall state of the code. We were to act as an independent third party, between a new studio who had inherited the codebase, and the client, who was anticipating launching the product.
Startups need people able and willing of doing the actual work. They need programmers, designers, and eventually folks to do marketing, support, and more. What they don’t need, though, is someone who’s just going to be The Idea Guy.
Sometime in 2014, PHP-land started to debate whether Active Record was a tolerable ORM pattern, and whether one should use Active Record or Data Mapper ORMs. In PHP, this comes down to something like Laravel’s Eloquent ORM as an Active Record implementation vs. Doctrine, the reigning mainstream (and probably only) PHP data mapper implementation. After a surge of interest in Domain-Driven Design (DDD) and Hexagonal Architecture in the Laravel, and overall PHP communities, people began to detest one of the very things that drew them to the framework in the first place. This was fueled by a number of vocal and notable Laravel community members learning Doctine, talking about it heavily, and some evangelizing it. With outside influence from the PHP world providing the same judgement against the impure Active Record pattern, the pitchforks started to come out from all over.
We are working on using FeatureFlags or Toggles in our applications. For one we are aiming to do all our work on mainline branch at all times so this would be a key coding discipline to use FeatureFlags so we can hide a feature in progress knowing it will not interfere with the application. For example if a hotfix or another feature is ready to go to production we can push that with no worries of the in progress feature.
If you type git pull and expect a fast-forward update, but get a merge instead, don't panic! This usually happens when we're collaborating on a branch with other people, and we've made changes on our local version of a branch, and someone else (or the other you, if you use git to sync between multiple dev platforms) has made changes to the remote version of a branch in the meantime. It also happens really frequently in teams where all commits are to the master branch ... yet another reason to have a decent branching strategy.
Stay up to date
For any inquiries, please email us at hello@podcastworld.io