[{"data":1,"prerenderedAt":1028},["ShallowReactive",2],{"post-cards":3,"categories":529,"post-git-flow-vs-github-flow-choosing-a-branching-strategy":567},[4,27,38,54,68,78,87,97,111,124,134,145,160,172,185,196,207,218,229,240,251,264,277,292,307,321,335,347,358,369,379,389,399,409,419,429,439,449,459,469,479,489,499,509,519],{"path":5,"title":6,"slug":7,"summary":8,"date":9,"readTime":10,"hasImage":11,"category":12,"tags":17,"tagSlugs":26},"\u002Fposts\u002Fgit-flow-vs-github-flow-choosing-a-branching-strategy","Git Flow vs GitHub Flow: Choosing a Branching Strategy for Your Team","git-flow-vs-github-flow-choosing-a-branching-strategy","Git Flow and GitHub Flow take very different approaches to team branching and releases. Let's compare them, see where trunk-based development fits, and sort out how to handle versioned releases, hotfixes, and everything in between.","2026-06-14",7,false,{"id":13,"name":14,"slug":15,"hue":16},4,"Git","git",158,[18,20,23],{"name":19,"slug":15},"GIT",{"name":21,"slug":22},"Workflow","workflow",{"name":24,"slug":25},"GitHub","github",[15,22,25],{"path":28,"title":29,"slug":30,"summary":31,"date":9,"readTime":10,"hasImage":11,"category":32,"tags":33,"tagSlugs":37},"\u002Fposts\u002Fgithub-flow-keep-your-main-branch-deployable","GitHub Flow: Keep Your Main Branch Deployable","github-flow-keep-your-main-branch-deployable","GitHub Flow is the lightweight branching workflow built on a single rule: anything in main is deployable. Here is the whole loop, branch, pull request, review, merge and deploy, with the git and gh commands and an honest look at where it fits.",{"id":13,"name":14,"slug":15,"hue":16},[34,35,36],{"name":19,"slug":15},{"name":21,"slug":22},{"name":24,"slug":25},[15,22,25],{"path":39,"title":40,"slug":41,"summary":42,"date":43,"readTime":44,"hasImage":11,"category":45,"tags":50,"tagSlugs":53},"\u002Fposts\u002Fstarting-with-rust-installation-first-program","Starting with Rust: From Installation to Your First Program","starting-with-rust-installation-first-program","Learn how to install Rust and write your first \"Hello, world!\" program.","2024-03-23",2,{"id":46,"name":47,"slug":48,"hue":49},6,"Rust","rust-programming",38,[51],{"name":52,"slug":52},"rust",[52],{"path":55,"title":56,"slug":57,"summary":58,"date":59,"readTime":44,"hasImage":11,"category":60,"tags":65,"tagSlugs":67},"\u002Fposts\u002Fflutter-version-management-fvm","Flutter Version Management","flutter-version-management-fvm","Managing multiple Flutter versions does not need not be a headache. Let's jump into FVM and see how it can simplify your Flutter journey.","2023-10-07",{"id":61,"name":62,"slug":63,"hue":64},5,"Flutter","flutter",230,[66],{"name":63,"slug":63},[63],{"path":69,"title":70,"slug":71,"summary":72,"date":59,"readTime":73,"hasImage":11,"category":74,"tags":75,"tagSlugs":77},"\u002Fposts\u002Fsetting-up-cocoapods-fvm","Setting Up CocoaPods for FVM-managed Flutter Projects","setting-up-cocoapods-fvm","A guide to installing CocoaPods for a Flutter project while using FVM to manage Flutter versions, ensuring a smooth setup for iOS development.",1,{"id":61,"name":62,"slug":63,"hue":64},[76],{"name":63,"slug":63},[63],{"path":79,"title":80,"slug":81,"summary":82,"date":59,"readTime":73,"hasImage":11,"category":83,"tags":84,"tagSlugs":86},"\u002Fposts\u002Ftroubleshooting-xcode-15-build-issues-flutter","Troubleshooting Xcode 15 Build Issues in Flutter Projects","troubleshooting-xcode-15-build-issues-flutter","Uncovering solutions to common issues faced when updating to Xcode 15 in a Flutter project using an older version of CocoaPods.",{"id":61,"name":62,"slug":63,"hue":64},[85],{"name":63,"slug":63},[63],{"path":88,"title":89,"slug":90,"summary":91,"date":92,"readTime":13,"hasImage":11,"category":93,"tags":94,"tagSlugs":96},"\u002Fposts\u002Fgit-tracking-a-remote-branch-upstream-for-changes","Git: Tracking a Remote Branch for Changes","git-tracking-a-remote-branch-upstream-for-changes","When you fork a project, you need a way to pull in changes from the original repository, usually called upstream. Here is how to wire up an upstream remote, actually sync your fork, and set up branch tracking so plain git pull and git push just work.","2018-11-04",{"id":13,"name":14,"slug":15,"hue":16},[95],{"name":19,"slug":15},[15],{"path":98,"title":99,"slug":100,"summary":101,"date":92,"readTime":102,"hasImage":103,"category":104,"tags":108,"tagSlugs":110},"\u002Fposts\u002Fjavascript-array-map-filter-reduce-functions","JavaScript's map, filter, and reduce methods","javascript-array-map-filter-reduce-functions","JavaScript provides some amazing functions that can be called against your arrays to help filter them, manipulate them, or even reduce them down to a single value or grouped values.",3,true,{"id":44,"name":105,"slug":106,"hue":107},"JavaScript","javascript",92,[109],{"name":105,"slug":106},[106],{"path":112,"title":113,"slug":114,"summary":115,"date":116,"readTime":73,"hasImage":103,"category":117,"tags":121,"tagSlugs":123},"\u002Fposts\u002Fphp-fizzbuzz-example","FizzBuzz in PHP: A Fresh Approach","php-fizzbuzz-example","FizzBuzz is a very popular programming question that tests your logic to see if you can build a simple program.","2018-11-02",{"id":73,"name":118,"slug":119,"hue":120},"PHP","php",264,[122],{"name":118,"slug":119},[119],{"path":125,"title":126,"slug":127,"summary":128,"date":129,"readTime":44,"hasImage":103,"category":130,"tags":131,"tagSlugs":133},"\u002Fposts\u002Fphp-array-reduce","PHP's array_reduce is not only for outputting single values","php-array-reduce","PHP's array_reduce is a simple way to partition a set of data or return a single value. It is super powerful and worth spending time learning.","2018-11-01",{"id":73,"name":118,"slug":119,"hue":120},[132],{"name":118,"slug":119},[119],{"path":135,"title":136,"slug":137,"summary":138,"date":139,"readTime":46,"hasImage":11,"category":140,"tags":141,"tagSlugs":144},"\u002Fposts\u002Fimprove-your-git-workflow-with-git-flow","Improve Your Git Workflow with Git Flow","improve-your-git-workflow-with-git-flow","Git Flow is a structured branching model built around versioned, scheduled releases. Here is how its branches fit together, a hands-on walkthrough of features, releases and hotfixes, and an honest take on when it is still the right call.","2016-12-06",{"id":13,"name":14,"slug":15,"hue":16},[142,143],{"name":19,"slug":15},{"name":21,"slug":22},[15,22],{"path":146,"title":147,"slug":148,"summary":149,"date":150,"readTime":46,"hasImage":11,"category":151,"tags":155,"tagSlugs":159},"\u002Fposts\u002Fusing-css-transitions","Using CSS Transitions","using-css-transitions","CSS transitions are the standard way to apply transitions to your elements, and have been for years, replacing the old approach of using JavaScript. In this article, I'll go through each of the transition properties available, and provide examples of how to use them.","2016-12-05",{"id":102,"name":152,"slug":153,"hue":154},"HTML & CSS","html-css",55,[156],{"name":157,"slug":158},"CSS","css",[158],{"path":161,"title":162,"slug":163,"summary":164,"date":165,"readTime":13,"hasImage":11,"category":166,"tags":167,"tagSlugs":171},"\u002Fposts\u002Fstructuring-your-website-with-html-5-semantics","Structuring Your Website With HTML 5 Semantics","structuring-your-website-with-html-5-semantics","Prior to HTML 5, there was no real markup to help explain the intent behind your HTML code. The goal of HTML 5 was to offer a more readable way of writing your code, so that any author that comes after you can have an easier time going through what you've created.","2016-12-04",{"id":102,"name":152,"slug":153,"hue":154},[168],{"name":169,"slug":170},"HTML","html",[170],{"path":173,"title":174,"slug":175,"summary":176,"date":177,"readTime":44,"hasImage":11,"category":178,"tags":179,"tagSlugs":184},"\u002Fposts\u002Finterpolation-in-stylus-css-pre-processor","Interpolation in Stylus","interpolation-in-stylus-css-pre-processor","You can also use interpolation to improve your functions for reuse, as well as your other code within your stylesheet. The way it works is that you can wrap your expression within {}, which will then be outputted as the identifier.","2016-12-03",{"id":102,"name":152,"slug":153,"hue":154},[180,183],{"name":181,"slug":182},"Stylus","stylus",{"name":157,"slug":158},[182,158],{"path":186,"title":187,"slug":188,"summary":189,"date":190,"readTime":73,"hasImage":11,"category":191,"tags":192,"tagSlugs":195},"\u002Fposts\u002Fcreating-configuration-files-in-stylus-css-pre-processor","Creating Configuration Files In Stylus","creating-configuration-files-in-stylus-css-pre-processor","It's super simple to create a configuration file for instance that would manage your media query break points. You could also use a configuration file for managing colors, font sizes, and other variables such as gutter spacing and more.","2016-12-02",{"id":102,"name":152,"slug":153,"hue":154},[193,194],{"name":157,"slug":158},{"name":181,"slug":182},[158,182],{"path":197,"title":198,"slug":199,"summary":200,"date":201,"readTime":13,"hasImage":11,"category":202,"tags":203,"tagSlugs":206},"\u002Fposts\u002Fusing-functions-and-mixins-with-stylus-css-pre-processor","Using Functions and Mixins with Stylus","using-functions-and-mixins-with-stylus-css-pre-processor","Stylus allows you to create functions and mixins of reusable code for your stylesheets. You can also handle mathematical operations, unary operations, and more allowing you complete control over your stylesheets with ease.","2016-12-01",{"id":102,"name":152,"slug":153,"hue":154},[204,205],{"name":157,"slug":158},{"name":181,"slug":182},[158,182],{"path":208,"title":209,"slug":210,"summary":211,"date":212,"readTime":44,"hasImage":11,"category":213,"tags":214,"tagSlugs":217},"\u002Fposts\u002Fsetting-variables-in-stylus-css-pre-processor","Setting Variables in Stylus","setting-variables-in-stylus-css-pre-processor","Unlike CSS, in Stylus you can assign expressions to variables that can be reusable throughout your stylesheets.","2016-11-29",{"id":102,"name":152,"slug":153,"hue":154},[215,216],{"name":157,"slug":158},{"name":181,"slug":182},[158,182],{"path":219,"title":220,"slug":221,"summary":222,"date":223,"readTime":61,"hasImage":11,"category":224,"tags":225,"tagSlugs":228},"\u002Fposts\u002Fusing-selectors-in-stylus-css-pre-processor","Using Selectors in Stylus","using-selectors-in-stylus-css-pre-processor","Selectors are a way to pick the elements that you want styled. In Stylus, similar to CSS, you can apply a set of styles to any element by separating them by a comma delimited list. Stylus though, also allows you to select multiple elements by separating each on their own line.","2016-11-28",{"id":102,"name":152,"slug":153,"hue":154},[226,227],{"name":157,"slug":158},{"name":181,"slug":182},[158,182],{"path":230,"title":231,"slug":232,"summary":233,"date":234,"readTime":73,"hasImage":11,"category":235,"tags":236,"tagSlugs":239},"\u002Fposts\u002Flearning-stylus-a-css-pre-processor","Learning Stylus: A CSS Pre-Processor","learning-stylus-a-css-pre-processor","This mini-series will be a little different to how you may see other articles on my site. Really this article is more geared as notes for me as I go through the documentation for Stylus, and learn the ins and outs of this beautiful language.","2016-11-27",{"id":102,"name":152,"slug":153,"hue":154},[237,238],{"name":157,"slug":158},{"name":181,"slug":182},[158,182],{"path":241,"title":242,"slug":243,"summary":244,"date":245,"readTime":13,"hasImage":11,"category":246,"tags":247,"tagSlugs":250},"\u002Fposts\u002Fbem-methodology-overview-and-naming-conventions","BEM Methodology Overview and Naming Conventions","bem-methodology-overview-and-naming-conventions","BEM or Block Element Modifier is a naming convention used to help organize your code base. In this article, I discuss its uses within your CSS projects.","2016-11-26",{"id":102,"name":152,"slug":153,"hue":154},[248,249],{"name":157,"slug":158},{"name":169,"slug":170},[158,170],{"path":252,"title":253,"slug":254,"summary":255,"date":256,"readTime":73,"hasImage":11,"category":257,"tags":258,"tagSlugs":263},"\u002Fposts\u002Fintroduction-to-ecmascript-6","Introduction to ECMAScript 6","introduction-to-ecmascript-6","The latest in ECMAScript 6 introduces new features to JavaScript which makes it so much more fun to use, while solving problems that have been around for years. The intent of this article is to provide you with resources you can use to start learning ES6 today.","2016-11-25",{"id":44,"name":105,"slug":106,"hue":107},[259,260],{"name":105,"slug":106},{"name":261,"slug":262},"ECMAScript","ecmascript",[106,262],{"path":265,"title":266,"slug":267,"summary":268,"date":269,"readTime":102,"hasImage":11,"category":270,"tags":271,"tagSlugs":276},"\u002Fposts\u002Fbabel-installation-and-configuration","Babel Installation and Configuration","babel-installation-and-configuration","Babel offers a convenient way to transform your ES6 code to JavaScript that all browsers can understand. In this article we'll go over a basic configuration that will enable you to start using it with any project right away.","2016-11-24",{"id":44,"name":105,"slug":106,"hue":107},[272,273],{"name":105,"slug":106},{"name":274,"slug":275},"Babel","babel",[106,275],{"path":278,"title":279,"slug":280,"summary":281,"date":282,"readTime":73,"hasImage":11,"category":283,"tags":284,"tagSlugs":291},"\u002Fposts\u002Fconfiguring-stylus-css-pre-processor-with-gulp-and-sourcemaps","Configuring Stylus CSS Pre-Processor with Gulp and Sourcemaps","configuring-stylus-css-pre-processor-with-gulp-and-sourcemaps","In this article we'll go over how to configure your project to process Stylus files using Gulp. We'll also create source map file which your browser will use to help point you in the right direction of your files when developing","2016-11-23",{"id":44,"name":105,"slug":106,"hue":107},[285,286,287,288],{"name":105,"slug":106},{"name":181,"slug":182},{"name":157,"slug":158},{"name":289,"slug":290},"Gulp","gulp",[106,182,158,290],{"path":293,"title":294,"slug":295,"summary":296,"date":297,"readTime":44,"hasImage":11,"category":298,"tags":299,"tagSlugs":306},"\u002Fposts\u002Fconfiguring-gulp-with-less-css-pre-processor","Configuring Gulp With Less CSS Pre-Processor","configuring-gulp-with-less-css-pre-processor","Less is a CSS pre-processor allowing you to create variables, mixins, and functions in an effort to make your CSS more maintainable.","2016-11-22",{"id":44,"name":105,"slug":106,"hue":107},[300,301,302,305],{"name":289,"slug":290},{"name":105,"slug":106},{"name":303,"slug":304},"Less","less",{"name":157,"slug":158},[290,106,304,158],{"path":308,"title":309,"slug":310,"summary":311,"date":312,"readTime":44,"hasImage":103,"category":313,"tags":314,"tagSlugs":320},"\u002Fposts\u002Fusing-browser-sync-with-gulp-for-live-reloading","Using Browser Sync with Gulp for Live Reloading","using-browser-sync-with-gulp-for-live-reloading","Browser Sync is a nice tool to use while developing. It allows your browser to reload live when changes are made to your files. For instance, assuming we're watching our CSS file for changes we can have the browser auto refresh\u002Fsync when it sees those changes made.","2016-11-21",{"id":44,"name":105,"slug":106,"hue":107},[315,316,319],{"name":105,"slug":106},{"name":317,"slug":318},"Browser Sync","browser-sync",{"name":289,"slug":290},[106,318,290],{"path":322,"title":323,"slug":324,"summary":325,"date":326,"readTime":44,"hasImage":11,"category":327,"tags":328,"tagSlugs":334},"\u002Fposts\u002Fgulp-watch-automate-your-gulp-tasks","Gulp Watch: Automate Your Gulp Tasks","gulp-watch-automate-your-gulp-tasks","Gulp watch is perfect for when you're editing project files since it allows you to not have to run the gulp command manually each time.","2016-11-20",{"id":44,"name":105,"slug":106,"hue":107},[329,330,333],{"name":105,"slug":106},{"name":331,"slug":332},"Yarn","yarn",{"name":289,"slug":290},[106,332,290],{"path":336,"title":337,"slug":338,"summary":339,"date":340,"readTime":46,"hasImage":11,"category":341,"tags":342,"tagSlugs":346},"\u002Fposts\u002Fconfiguring-gulp-on-a-new-project","Configuring Gulp On A New Project","configuring-gulp-on-a-new-project","Gulp may seem like a scary thing to wrap your head around at first, but it's actually quite easy to start using once you understand the basics.","2016-11-19",{"id":44,"name":105,"slug":106,"hue":107},[343,344,345],{"name":105,"slug":106},{"name":289,"slug":290},{"name":331,"slug":332},[106,290,332],{"path":348,"title":349,"slug":350,"summary":351,"date":352,"readTime":102,"hasImage":11,"category":353,"tags":354,"tagSlugs":357},"\u002Fposts\u002Fyarn-publishing-a-package","Yarn: Publishing a Package","yarn-publishing-a-package","Publishing a package to the npm repository has never been simpler. With a few steps, you can create a package that is redistributable to all of your projects.","2016-11-18",{"id":44,"name":105,"slug":106,"hue":107},[355,356],{"name":105,"slug":106},{"name":331,"slug":332},[106,332],{"path":359,"title":360,"slug":361,"summary":362,"date":363,"readTime":102,"hasImage":11,"category":364,"tags":365,"tagSlugs":368},"\u002Fposts\u002Fyarn-fast-and-secure-dependency-management","Yarn: Fast and Secure Dependency Management","yarn-fast-and-secure-dependency-management","Yarn is a super simple dependency management tool which is way faster to use instead of traditional npm. It acts as a drop-in replacement, so you can get started using yarn right away. The best way to install yarn is by using npm.","2016-11-17",{"id":44,"name":105,"slug":106,"hue":107},[366,367],{"name":105,"slug":106},{"name":331,"slug":332},[106,332],{"path":370,"title":371,"slug":372,"summary":373,"date":374,"readTime":73,"hasImage":103,"category":375,"tags":376,"tagSlugs":378},"\u002Fposts\u002Fsupport-for-keys-in-list-or-its-new-shorthand-syntax-in-php","Support for keys in list(), or its new shorthand syntax [] in PHP","support-for-keys-in-list-or-its-new-shorthand-syntax-in-php","Now as of PHP 7.1, you can define the keys of your array that will be parsed when destructuring your arrays. Prior to PHP 7.1, you could only use arrays with numeric indexes. Now with this new addition, our lives just got easier.","2016-11-16",{"id":73,"name":118,"slug":119,"hue":120},[377],{"name":118,"slug":119},[119],{"path":380,"title":381,"slug":382,"summary":383,"date":384,"readTime":73,"hasImage":103,"category":385,"tags":386,"tagSlugs":388},"\u002Fposts\u002Ftype-hinting-with-the-iterable-pseudo-type-in-php","Type Hinting With The Iterable pseudo-type In PHP","type-hinting-with-the-iterable-pseudo-type-in-php","As of PHP 7.1, you can now type hint your method\u002Ffunction arguments with the keyword iterable for handling arrays or even objects that implement the Traversable interface.","2016-11-15",{"id":73,"name":118,"slug":119,"hue":120},[387],{"name":118,"slug":119},[119],{"path":390,"title":391,"slug":392,"summary":393,"date":394,"readTime":73,"hasImage":103,"category":395,"tags":396,"tagSlugs":398},"\u002Fposts\u002Ftype-hinting-callable-functions-in-php","Type Hinting Callable Functions in PHP","type-hinting-callable-functions-in-php","As of PHP 5.4, you can type hint your method arguments with the callable keyword allowing you to enforce the type of data that is passed via your arguments.","2016-11-14",{"id":73,"name":118,"slug":119,"hue":120},[397],{"name":118,"slug":119},[119],{"path":400,"title":401,"slug":402,"summary":403,"date":404,"readTime":73,"hasImage":103,"category":405,"tags":406,"tagSlugs":408},"\u002Fposts\u002Fsetting-visibility-for-your-class-constants-in-php","Setting Visibility for Your Class Constants in PHP","setting-visibility-for-your-class-constants-in-php","Now in PHP 7.1+, you can set different visibility modifiers for each of your class constants. The available visibility modifiers consist of public, protected, and private.","2016-11-13",{"id":73,"name":118,"slug":119,"hue":120},[407],{"name":118,"slug":119},[119],{"path":410,"title":411,"slug":412,"summary":413,"date":414,"readTime":73,"hasImage":103,"category":415,"tags":416,"tagSlugs":418},"\u002Fposts\u002Fanonymous-classes-php","Using Anonymous Classes in PHP","anonymous-classes-php","As of PHP 7, you can now create quick throwaway objects for use within your projects. This can be especially useful for your automated tests, for instance, with allowing you to create quick implementations of your interfaces.","2016-11-12",{"id":73,"name":118,"slug":119,"hue":120},[417],{"name":118,"slug":119},[119],{"path":420,"title":421,"slug":422,"summary":423,"date":424,"readTime":73,"hasImage":103,"category":425,"tags":426,"tagSlugs":428},"\u002Fposts\u002Fsymmetric-array-destructuring-in-php","Symmetric Array Destructuring in PHP","symmetric-array-destructuring-in-php","As of PHP 7.1, you can now use the shorthand array syntax to destructure your arrays for assignment. Previously you would have had to use a function like list, but now you can use the simple new array shorthand syntax.","2016-11-11",{"id":73,"name":118,"slug":119,"hue":120},[427],{"name":118,"slug":119},[119],{"path":430,"title":431,"slug":432,"summary":433,"date":434,"readTime":44,"hasImage":103,"category":435,"tags":436,"tagSlugs":438},"\u002Fposts\u002Fphp-array-map-to-format-your-arrays-without-loops","Using PHP's array_map to format your arrays without loops","php-array-map-to-format-your-arrays-without-loops","So let's face it, loops are a bit boring. So how can we mix it up? Let's assume we have a case where we have a CSV file that we want to quickly parse.","2016-11-10",{"id":73,"name":118,"slug":119,"hue":120},[437],{"name":118,"slug":119},[119],{"path":440,"title":441,"slug":442,"summary":443,"date":444,"readTime":10,"hasImage":103,"category":445,"tags":446,"tagSlugs":448},"\u002Fposts\u002Fsolid-principles-in-php","SOLID Principles in PHP","solid-principles-in-php","The 5 basic principles for Object-Oriented Design, SOLID, were first created in an effort to improve maintainability in our code bases. SOLID is a mnemonic acronym that stands for each of the following principles: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.","2016-11-09",{"id":73,"name":118,"slug":119,"hue":120},[447],{"name":118,"slug":119},[119],{"path":450,"title":451,"slug":452,"summary":453,"date":454,"readTime":73,"hasImage":103,"category":455,"tags":456,"tagSlugs":458},"\u002Fposts\u002Ffiltering-arrays-without-using-loops-in-php","Filtering Arrays Without Using Loops in PHP","filtering-arrays-without-using-loops-in-php","PHP has a built-in function called array_filter that allows you to filter through your arrays without the need for a loop. Personally, this approach feels much cleaner to me and simpler to comprehend.","2016-11-08",{"id":73,"name":118,"slug":119,"hue":120},[457],{"name":118,"slug":119},[119],{"path":460,"title":461,"slug":462,"summary":463,"date":464,"readTime":73,"hasImage":103,"category":465,"tags":466,"tagSlugs":468},"\u002Fposts\u002Fvoid-return-types-in-php","Void Return Types in PHP","void-return-types-in-php","As of PHP 7.1, we can now use void return types within our methods. This is useful for cases where you have methods that are just setting or processing data without the need of returning any values.","2016-11-07",{"id":73,"name":118,"slug":119,"hue":120},[467],{"name":118,"slug":119},[119],{"path":470,"title":471,"slug":472,"summary":473,"date":474,"readTime":73,"hasImage":103,"category":475,"tags":476,"tagSlugs":478},"\u002Fposts\u002Ftype-hinting-with-nullable-types-in-php","Type Hinting with Nullable Types in PHP","type-hinting-with-nullable-types-in-php","As of PHP 7.1, you can now set your type declarations as nullable by simply prefixing them with a question mark ?. In doing so a null value can be passed in as a parameter or returned as a value for your methods.","2016-11-06",{"id":73,"name":118,"slug":119,"hue":120},[477],{"name":118,"slug":119},[119],{"path":480,"title":481,"slug":482,"summary":483,"date":484,"readTime":73,"hasImage":103,"category":485,"tags":486,"tagSlugs":488},"\u002Fposts\u002Fphp-group-multiple-use-declarations","PHP Group Multiple use Declarations","php-group-multiple-use-declarations","As of PHP 7, you can now group your imported classes, functions, and constants from under the same namespace.","2016-11-05",{"id":73,"name":118,"slug":119,"hue":120},[487],{"name":118,"slug":119},[119],{"path":490,"title":491,"slug":492,"summary":493,"date":494,"readTime":73,"hasImage":103,"category":495,"tags":496,"tagSlugs":498},"\u002Fposts\u002Fphp-null-coalescing-operator","PHP Null Coalescing Operator","php-null-coalescing-operator","One of my new favorite additions to PHP 7, is the Null Coalescing Operator. It cleans up your code by removing a tedious step of checking if some value is isset() and not NULL and returning it or if not setting a default.","2016-11-04",{"id":73,"name":118,"slug":119,"hue":120},[497],{"name":118,"slug":119},[119],{"path":500,"title":501,"slug":502,"summary":503,"date":504,"readTime":44,"hasImage":103,"category":505,"tags":506,"tagSlugs":508},"\u002Fposts\u002Fphp-spaceship-operator","PHP Spaceship Operator","php-spaceship-operator","One of the new features to hit PHP 7 is the Spaceship Operator. This new trick helps improve the way you'd compare 2 expressions. In short, the comparison returns 1 of 3 values (-1, 0, or 1) depending on the result of the comparison.","2016-11-03",{"id":73,"name":118,"slug":119,"hue":120},[507],{"name":118,"slug":119},[119],{"path":510,"title":511,"slug":512,"summary":513,"date":514,"readTime":102,"hasImage":103,"category":515,"tags":516,"tagSlugs":518},"\u002Fposts\u002Freturn-type-declarations-in-php","Return Type Declarations in PHP","return-type-declarations-in-php","PHP 7 now makes it possible to declare return types for your methods. This allows you better control over the data that will be returned from each method in your application.","2016-11-02",{"id":73,"name":118,"slug":119,"hue":120},[517],{"name":118,"slug":119},[119],{"path":520,"title":521,"slug":522,"summary":523,"date":524,"readTime":73,"hasImage":103,"category":525,"tags":526,"tagSlugs":528},"\u002Fposts\u002Fscalar-type-hints-php","Scalar Type Hints in PHP","scalar-type-hints-php","Starting with PHP 7.0, it's now possible to declare scalar type hints for your method arguments. Previously, we were able to use array and callable, but now with PHP 7+, we have much more control.","2016-11-01",{"id":73,"name":118,"slug":119,"hue":120},[527],{"name":118,"slug":119},[119],[530,537,543,549,555,561],{"id":531,"description":532,"extension":533,"hue":120,"meta":534,"name":118,"slug":119,"stem":535,"weight":73,"__hash__":536},"categories\u002Fcategories\u002Fphp.json","PHP articles and tutorials ranging from new language features to using interesting packages.","json",{},"categories\u002Fphp","h_EmN4YMO4b2mBt3MPLs7RvscJx0NBmwDIZPxqPqKLE",{"id":538,"description":539,"extension":533,"hue":107,"meta":540,"name":105,"slug":106,"stem":541,"weight":44,"__hash__":542},"categories\u002Fcategories\u002Fjavascript.json","JavaScript articles and tutorials ranging from new language features to using interesting packages.",{},"categories\u002Fjavascript","7gmVgkw5BRo26i1bFoSv96bwDJ4nTtZcJ9Ud6u5p0yk",{"id":544,"description":545,"extension":533,"hue":154,"meta":546,"name":152,"slug":153,"stem":547,"weight":102,"__hash__":548},"categories\u002Fcategories\u002Fhtml-css.json","HTML & CSS articles and tutorials ranging from new language features to using interesting packages.",{},"categories\u002Fhtml-css","vXvPlRA-iaeCJ64Wi3sLyUR0kqL48zYcZWORRqt8N70",{"id":550,"description":551,"extension":533,"hue":16,"meta":552,"name":14,"slug":15,"stem":553,"weight":13,"__hash__":554},"categories\u002Fcategories\u002Fgit.json","Git articles and tutorials ranging from new language features to different workflows.",{},"categories\u002Fgit","qOqFsFTKI9XB444UodUKW_3AakFadHzW-ss8V-maUmE",{"id":556,"description":557,"extension":533,"hue":64,"meta":558,"name":62,"slug":63,"stem":559,"weight":61,"__hash__":560},"categories\u002Fcategories\u002Fflutter.json","Dive into Flutter, the open-source UI software development toolkit, as we explore its capabilities in creating natively compiled applications for mobile, web, and desktop from a single codebase.",{},"categories\u002Fflutter","aD1moU8CgoYt4FRnSeA4Iy9xxnnopdEKBEYP2arAzdI",{"id":562,"description":563,"extension":533,"hue":49,"meta":564,"name":47,"slug":48,"stem":565,"weight":46,"__hash__":566},"categories\u002Fcategories\u002Frust-programming.json","From setting up your environment to advanced concepts, this is your go-to resource for all things Rust.",{},"categories\u002Frust-programming","LscnqSsk-htWc9yZg9eXaIUJwNfTK5oaZOClYKagNC4",{"id":568,"title":6,"body":569,"category":1017,"date":9,"description":575,"extension":1018,"hasImage":11,"meta":1019,"navigation":103,"path":5,"readTime":10,"seo":1020,"slug":7,"stem":1021,"summary":8,"tagSlugs":1022,"tags":1023,"__hash__":1027},"posts\u002Fposts\u002Fgit-flow-vs-github-flow-choosing-a-branching-strategy.md",{"type":570,"value":571,"toc":1008},"minimark",[572,576,581,584,587,591,594,641,650,653,656,660,666,669,690,743,759,765,768,772,778,781,784,788,795,816,823,858,877,881,884,908,966,975,987,994,998,1001,1004],[573,574,575],"p",{},"There's no single \"right\" way to branch your code. Git Flow, GitHub Flow, and trunk-based development are all popular, all battle tested, and all used by teams shipping great software every day. The trick isn't picking the \"best\" one, it's picking the one that matches how your team actually releases. In this article we'll compare the two big names, see where trunk-based development fits in, and sort out how to handle versioned releases along with the fixes that inevitably follow.",[577,578,580],"h2",{"id":579},"two-ways-to-think-about-branching","Two Ways to Think About Branching",[573,582,583],{},"It helps to picture branching strategies on a spectrum. On one end you have Git Flow, which is structured and ceremony-heavy, built around scheduled, versioned releases. On the other end you have GitHub Flow, which is about as simple as it gets: one long-lived branch that's always ready to deploy.",[573,585,586],{},"Most teams land somewhere along that line. So before you copy a workflow just because a big company uses it, ask yourself one question: how often do we ship, and do we need to support more than one released version at a time? Your answer points you to the right end of the spectrum.",[577,588,590],{"id":589},"git-flow-structure-for-versioned-releases","Git Flow: Structure for Versioned Releases",[573,592,593],{},"Git Flow has been around since 2010, and it's the most formal of the bunch. It uses two long-lived branches plus three kinds of supporting branches.",[595,596,597,609,615,624,633],"ul",{},[598,599,600,604,605,608],"li",{},[601,602,603],"code",{},"main"," (or ",[601,606,607],{},"master",") is what's in production.",[598,610,611,614],{},[601,612,613],{},"develop"," is the integration branch where finished work collects.",[598,616,617,620,621,623],{},[601,618,619],{},"feature\u002F*"," branches come off ",[601,622,613],{}," for each new piece of work.",[598,625,626,629,630,632],{},[601,627,628],{},"release\u002F*"," branches freeze ",[601,631,613],{}," so you can harden a version before shipping it.",[598,634,635,620,638,640],{},[601,636,637],{},"hotfix\u002F*",[601,639,603],{}," to patch production in a hurry.",[573,642,643,644,649],{},"I won't rehash every command here, since I already walked through the full setup in ",[645,646,648],"a",{"href":647},"\u002Farticles\u002Fimprove-your-git-workflow-with-git-flow","Improve your Git workflow with Git Flow",". What matters for this comparison is the shape: work flows from feature, to develop, to release, to main, with versions tagged along the way.",[573,651,652],{},"That structure really shines when you ship versioned software on a schedule. Think desktop apps, libraries, mobile releases, or anything where multiple versions live in the wild at once and need separate maintenance.",[573,654,655],{},"Now for the honest caveat. Even Vincent Driessen, who created Git Flow, later added a note to his original post saying that if your team practices continuous delivery, you should probably reach for something simpler. Atlassian these days describes it as a legacy workflow. None of that makes it wrong, it just means the extra branches are overhead you only want to pay for when versioned releases actually earn it.",[577,657,659],{"id":658},"github-flow-keep-main-deployable","GitHub Flow: Keep Main Deployable",[573,661,662,663,665],{},"GitHub Flow throws out almost all of that ceremony. It has exactly one rule: anything in ",[601,664,603],{}," is always deployable.",[573,667,668],{},"The loop is short:",[670,671,672,678,681,687],"ol",{},[598,673,674,675,677],{},"Branch off ",[601,676,603],{}," for your change.",[598,679,680],{},"Open a pull request and let your team review it.",[598,682,683,684,686],{},"Merge back into ",[601,685,603],{},".",[598,688,689],{},"Deploy.",[691,692,697],"pre",{"className":693,"code":694,"language":695,"meta":696,"style":696},"language-bash shiki shiki-themes github-dark github-dark","git checkout -b add-search-filters\n# do the work, commit\ngit push -u origin add-search-filters\n# open a PR, get a review, merge, deploy\n","bash","",[601,698,699,717,723,738],{"__ignoreMap":696},[700,701,703,706,710,714],"span",{"class":702,"line":73},"line",[700,704,15],{"class":705},"sFR8T",[700,707,709],{"class":708},"s4wv1"," checkout",[700,711,713],{"class":712},"s8ozJ"," -b",[700,715,716],{"class":708}," add-search-filters\n",[700,718,719],{"class":702,"line":44},[700,720,722],{"class":721},"sJ8bj","# do the work, commit\n",[700,724,725,727,730,733,736],{"class":702,"line":102},[700,726,15],{"class":705},[700,728,729],{"class":708}," push",[700,731,732],{"class":712}," -u",[700,734,735],{"class":708}," origin",[700,737,716],{"class":708},[700,739,740],{"class":702,"line":13},[700,741,742],{"class":721},"# open a PR, get a review, merge, deploy\n",[573,744,745,746,748,749,752,753,755,756,686],{},"There's no ",[601,747,613],{},", no ",[601,750,751],{},"release"," branches, and no waiting for a release window. Branches are short-lived, usually open for hours or a day or two rather than weeks. Because ",[601,754,603],{}," is always shippable, you can deploy the moment a PR lands. I walk through the whole loop, commands and all, in ",[645,757,29],{"href":758},"\u002Farticles\u002Fgithub-flow-keep-your-main-branch-deployable",[573,760,761,762,764],{},"This is a great fit for web apps and services, where there's really only one \"version\" running: whatever is live right now. It's also friendlier to small teams and to continuous integration, since you're constantly merging small changes instead of nursing a giant ",[601,763,613],{}," branch toward a release.",[573,766,767],{},"Where it strains is exactly where Git Flow is strong. If you need to support several released versions at once, or you do heavy release hardening, GitHub Flow's single main branch starts to feel a little thin.",[577,769,771],{"id":770},"a-quick-word-on-trunk-based-development","A Quick Word on Trunk-Based Development",[573,773,774,775,777],{},"If GitHub Flow felt minimal, trunk-based development goes one step further. Everyone integrates into a single trunk (your ",[601,776,603],{},") constantly, with branches that live for hours, not days. Anything that isn't ready for users hides behind a feature flag instead of sitting on a long-lived branch.",[573,779,780],{},"This is the workflow most associated with modern continuous delivery and high-performing DevOps teams, because it keeps merges tiny and integration pain close to zero. It does lean on solid automated tests and feature flags to stay safe, so it asks more of your tooling than it does of your branching.",[573,782,783],{},"You can think of GitHub Flow as the comfortable middle ground: simpler than Git Flow, but with pull requests and short feature branches still giving you a natural review checkpoint.",[577,785,787],{"id":786},"fixed-version-releases","Fixed Version Releases",[573,789,790,791,794],{},"Whichever flow you choose, the moment you start shipping versions you'll want a sane way to number and mark them. That's what semantic versioning is for. A version looks like ",[601,792,793],{},"MAJOR.MINOR.PATCH",":",[595,796,797,804,810],{},[598,798,799,803],{},[800,801,802],"strong",{},"MAJOR"," when you make a breaking change.",[598,805,806,809],{},[800,807,808],{},"MINOR"," when you add functionality in a backward-compatible way.",[598,811,812,815],{},[800,813,814],{},"PATCH"," when you ship a backward-compatible bug fix.",[573,817,818,819,822],{},"So ",[601,820,821],{},"2.4.1"," is the second major version, its fourth feature release, with one patch on top. Tag each release so you can always check out exactly what you shipped.",[691,824,826],{"className":693,"code":825,"language":695,"meta":696,"style":696},"git tag -a v2.4.1 -m \"Release 2.4.1\"\ngit push origin v2.4.1\n",[601,827,828,847],{"__ignoreMap":696},[700,829,830,832,835,838,841,844],{"class":702,"line":73},[700,831,15],{"class":705},[700,833,834],{"class":708}," tag",[700,836,837],{"class":712}," -a",[700,839,840],{"class":708}," v2.4.1",[700,842,843],{"class":712}," -m",[700,845,846],{"class":708}," \"Release 2.4.1\"\n",[700,848,849,851,853,855],{"class":702,"line":44},[700,850,15],{"class":705},[700,852,729],{"class":708},[700,854,735],{"class":708},[700,856,857],{"class":708}," v2.4.1\n",[573,859,860,861,863,864,867,868,870,871,873,874,876],{},"In Git Flow, this is where ",[601,862,628],{}," branches pay off. You cut ",[601,865,866],{},"release\u002F2.4.0"," off ",[601,869,613],{},", fix only the release blockers there, then merge it into ",[601,872,603],{},", tag it, and merge back into ",[601,875,613],{}," so nothing gets lost. Pair your tags with a short changelog and your team (along with your users) always knows what changed and when.",[577,878,880],{"id":879},"hotfixes-warmfixes-and-coldfixes","Hotfixes, Warmfixes, and Coldfixes",[573,882,883],{},"Not every fix is an emergency, and treating them all the same is how you either move too slowly or ship recklessly. It helps to think of fixes on a temperature scale.",[573,885,886,889,890,892,893,895,896,898,899,901,902,904,905,907],{},[800,887,888],{},"Hotfix."," Production is on fire: a crash, a security hole, a checkout that won't check out. You branch straight off ",[601,891,603],{},", make the smallest change that works, and ship it now. In Git Flow that's a ",[601,894,637],{}," branch off ",[601,897,603],{},", merged back into both ",[601,900,603],{}," and ",[601,903,613],{}," and tagged with a new patch version. In GitHub Flow it's just a normal short branch off ",[601,906,603],{},", except it jumps the queue.",[691,909,911],{"className":693,"code":910,"language":695,"meta":696,"style":696},"git checkout -b hotfix\u002Flogin-crash main\n# smallest possible fix, commit\ngit checkout main\ngit merge hotfix\u002Flogin-crash\ngit tag -a v2.4.2 -m \"Hotfix: login crash\"\n",[601,912,913,927,932,940,950],{"__ignoreMap":696},[700,914,915,917,919,921,924],{"class":702,"line":73},[700,916,15],{"class":705},[700,918,709],{"class":708},[700,920,713],{"class":712},[700,922,923],{"class":708}," hotfix\u002Flogin-crash",[700,925,926],{"class":708}," main\n",[700,928,929],{"class":702,"line":44},[700,930,931],{"class":721},"# smallest possible fix, commit\n",[700,933,934,936,938],{"class":702,"line":102},[700,935,15],{"class":705},[700,937,709],{"class":708},[700,939,926],{"class":708},[700,941,942,944,947],{"class":702,"line":13},[700,943,15],{"class":705},[700,945,946],{"class":708}," merge",[700,948,949],{"class":708}," hotfix\u002Flogin-crash\n",[700,951,952,954,956,958,961,963],{"class":702,"line":61},[700,953,15],{"class":705},[700,955,834],{"class":708},[700,957,837],{"class":712},[700,959,960],{"class":708}," v2.4.2",[700,962,843],{"class":712},[700,964,965],{"class":708}," \"Hotfix: login crash\"\n",[573,967,968,971,972,974],{},[800,969,970],{},"Warmfix."," This one is informal, you won't find it in any spec, but it's a handy label for the middle of the scale. A warmfix is important but not on fire. You don't want to wait a full release cycle, but you also don't need to bypass your normal checks. In practice it rides an expedited path: a patch release cut soon, or folded into a ",[601,973,628],{}," branch that's already in flight, rather than going straight to production.",[573,976,977,980,981,983,984,986],{},[800,978,979],{},"Coldfix."," A routine fix with no urgency. It goes through the front door like any other change: into ",[601,982,613],{}," (or onto ",[601,985,603],{}," via a PR in GitHub Flow), and out with the next scheduled release.",[573,988,989,990,686],{},"The point isn't the vocabulary, it's having a shared sense of how fast something needs to move and what you can safely skip to get it there. When you're coordinating fixes across a team, it also helps to keep your local copy in sync with everyone else's, which I covered in ",[645,991,993],{"href":992},"\u002Farticles\u002Fgit-tracking-a-remote-branch-upstream-for-changes","tracking a remote branch for changes",[577,995,997],{"id":996},"so-which-one-should-you-use","So Which One Should You Use?",[573,999,1000],{},"Here's how I'd decide. If you're a small team shipping a web app or service and you deploy often, start with GitHub Flow, then graduate to trunk-based development once your tests and feature flags can support it. If you ship versioned software on a schedule and have to support multiple releases in the wild, Git Flow's extra structure earns its keep.",[573,1002,1003],{},"But honestly, the specific convention matters less than picking one and sticking to it. A team that agrees on how branches are named, when things merge, and how releases get tagged will outship a team that's improvising every time, no matter which workflow is on the whiteboard. So pick the one that fits how you actually release, write it down, and get everyone using it. That consistency is the real win, and that's all there really is to it.",[1005,1006,1007],"style",{},"html pre.shiki code .sFR8T, html code.shiki .sFR8T{--shiki-default:#B392F0;--shiki-dark:#B392F0}html pre.shiki code .s4wv1, html code.shiki .s4wv1{--shiki-default:#9ECBFF;--shiki-dark:#9ECBFF}html pre.shiki code .s8ozJ, html code.shiki .s8ozJ{--shiki-default:#79B8FF;--shiki-dark:#79B8FF}html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":696,"searchDepth":44,"depth":44,"links":1009},[1010,1011,1012,1013,1014,1015,1016],{"id":579,"depth":44,"text":580},{"id":589,"depth":44,"text":590},{"id":658,"depth":44,"text":659},{"id":770,"depth":44,"text":771},{"id":786,"depth":44,"text":787},{"id":879,"depth":44,"text":880},{"id":996,"depth":44,"text":997},{"id":13,"name":14,"slug":15,"hue":16},"md",{},{"title":6,"description":575},"posts\u002Fgit-flow-vs-github-flow-choosing-a-branching-strategy",[15,22,25],[1024,1025,1026],{"name":19,"slug":15},{"name":21,"slug":22},{"name":24,"slug":25},"VuijSGlI2ryVmD7gF9RvYkPZR15z01wY3vPeTyPrQRg",1781454357270]