[{"data":1,"prerenderedAt":1174},["ShallowReactive",2],{"post-cards":3,"categories":529,"post-github-flow-keep-your-main-branch-deployable":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":29,"body":569,"category":1162,"date":9,"description":1163,"extension":1164,"hasImage":11,"meta":1165,"navigation":103,"path":28,"readTime":10,"seo":1166,"slug":30,"stem":1167,"summary":31,"tagSlugs":1168,"tags":1169,"__hash__":1173},"posts\u002Fposts\u002Fgithub-flow-keep-your-main-branch-deployable.md",{"type":570,"value":571,"toc":1150},"minimark",[572,592,597,617,620,624,627,674,683,687,701,867,870,890,896,900,918,922,929,935,939,948,992,997,1001,1015,1018,1022,1035,1103,1109,1113,1116,1122,1128,1132,1146],[573,574,575,576,581,582,586,587,591],"p",{},"If ",[577,578,580],"a",{"href":579},"\u002Farticles\u002Fimprove-your-git-workflow-with-git-flow","Git Flow"," is the structured, ceremony-heavy end of the branching spectrum, GitHub Flow is the opposite. It throws out the long-lived branches and release windows and runs on one rule: anything in ",[583,584,585],"code",{},"main"," is deployable. Everything else follows from that. If you want the head to head, I wrote a ",[577,588,590],{"href":589},"\u002Farticles\u002Fgit-flow-vs-github-flow-choosing-a-branching-strategy","Git Flow vs GitHub Flow comparison","; this post is the hands-on deep dive into GitHub Flow itself.",[593,594,596],"h2",{"id":595},"the-one-rule-that-drives-everything","The one rule that drives everything",[573,598,599,600,602,603,606,607,610,611,613,614,616],{},"GitHub Flow has exactly one promise: whatever is on ",[583,601,585],{}," right now could be deployed to production this second without a second thought. That single constraint is what makes the rest of the workflow so light. There is no ",[583,604,605],{},"develop"," branch collecting work, no ",[583,608,609],{},"release"," branch to harden, no version window to wait for. There is ",[583,612,585],{},", and there are short-lived branches that become ",[583,615,585],{}," once they pass review.",[573,618,619],{},"The trade you are making is honest and worth saying out loud. You get speed and simplicity, and you give up the ability to maintain several released versions at once. For a web app or a service, where the only version that matters is whatever is live, that is a great deal. For shrink-wrapped software that has to support v1 and v2 in the field, it is not, and that is where Git Flow earns its structure instead.",[593,621,623],{"id":622},"the-loop-step-by-step","The loop, step by step",[573,625,626],{},"GitHub's own docs describe GitHub Flow as a lightweight, branch-based workflow, and lay it out in six steps:",[628,629,630,641,647,653,659,665],"ol",{},[631,632,633,637,638,640],"li",{},[634,635,636],"strong",{},"Create a branch"," off ",[583,639,585],{}," with a short, descriptive name.",[631,642,643,646],{},[634,644,645],{},"Make changes"," as small, complete commits, pushing as you go.",[631,648,649,652],{},[634,650,651],{},"Open a pull request"," describing what changed and why.",[631,654,655,658],{},[634,656,657],{},"Address review feedback"," by pushing more commits to the same branch.",[631,660,661,664],{},[634,662,663],{},"Merge"," the pull request once it is approved and checks pass.",[631,666,667,670,671,673],{},[634,668,669],{},"Delete the branch",", since its work now lives in ",[583,672,585],{},".",[573,675,676,677,679,680,682],{},"You will notice \"deploy\" is not its own numbered step in the modern docs. That is because deployability is baked into the philosophy rather than bolted on at the end. Scott Chacon's original 2011 description of GitHub Flow was more explicit about it: once something is merged into ",[583,678,585],{},", you can and should deploy it immediately. Either way, the mental model is the same: branches are temporary, ",[583,681,585],{}," is always ready, and shipping is the easy part.",[593,684,686],{"id":685},"the-command-walkthrough","The command walkthrough",[573,688,689,690,696,697,700],{},"Here is one full trip around the loop in the terminal. I will use the ",[577,691,695],{"href":692,"rel":693},"https:\u002F\u002Fcli.github.com\u002F",[694],"nofollow","GitHub CLI"," (",[583,698,699],{},"gh",") for the pull request bits, but you can do all of it from the web UI too.",[702,703,708],"pre",{"className":704,"code":705,"language":706,"meta":707,"style":707},"language-bash shiki shiki-themes github-dark github-dark","# Start from an up-to-date main\ngit checkout main\ngit pull origin main\n\n# Create a descriptively named branch for the change\ngit switch -c increase-test-timeout\n\n# Make an isolated, complete change and commit it\ngit add .\ngit commit -m \"Increase CI timeout so flaky integration tests stop failing\"\n\n# Push the branch and set it to track the remote\ngit push -u origin increase-test-timeout\n\n# Open a pull request\ngh pr create --title \"Increase test timeout\" \\\n  --body \"Bumps the CI timeout so flaky integration tests stop failing. Closes #123\"\n","bash","",[583,709,710,718,730,742,747,752,766,770,776,787,801,806,812,827,832,838,858],{"__ignoreMap":707},[711,712,714],"span",{"class":713,"line":73},"line",[711,715,717],{"class":716},"sJ8bj","# Start from an up-to-date main\n",[711,719,720,723,727],{"class":713,"line":44},[711,721,15],{"class":722},"sFR8T",[711,724,726],{"class":725},"s4wv1"," checkout",[711,728,729],{"class":725}," main\n",[711,731,732,734,737,740],{"class":713,"line":102},[711,733,15],{"class":722},[711,735,736],{"class":725}," pull",[711,738,739],{"class":725}," origin",[711,741,729],{"class":725},[711,743,744],{"class":713,"line":13},[711,745,746],{"emptyLinePlaceholder":103},"\n",[711,748,749],{"class":713,"line":61},[711,750,751],{"class":716},"# Create a descriptively named branch for the change\n",[711,753,754,756,759,763],{"class":713,"line":46},[711,755,15],{"class":722},[711,757,758],{"class":725}," switch",[711,760,762],{"class":761},"s8ozJ"," -c",[711,764,765],{"class":725}," increase-test-timeout\n",[711,767,768],{"class":713,"line":10},[711,769,746],{"emptyLinePlaceholder":103},[711,771,773],{"class":713,"line":772},8,[711,774,775],{"class":716},"# Make an isolated, complete change and commit it\n",[711,777,779,781,784],{"class":713,"line":778},9,[711,780,15],{"class":722},[711,782,783],{"class":725}," add",[711,785,786],{"class":725}," .\n",[711,788,790,792,795,798],{"class":713,"line":789},10,[711,791,15],{"class":722},[711,793,794],{"class":725}," commit",[711,796,797],{"class":761}," -m",[711,799,800],{"class":725}," \"Increase CI timeout so flaky integration tests stop failing\"\n",[711,802,804],{"class":713,"line":803},11,[711,805,746],{"emptyLinePlaceholder":103},[711,807,809],{"class":713,"line":808},12,[711,810,811],{"class":716},"# Push the branch and set it to track the remote\n",[711,813,815,817,820,823,825],{"class":713,"line":814},13,[711,816,15],{"class":722},[711,818,819],{"class":725}," push",[711,821,822],{"class":761}," -u",[711,824,739],{"class":725},[711,826,765],{"class":725},[711,828,830],{"class":713,"line":829},14,[711,831,746],{"emptyLinePlaceholder":103},[711,833,835],{"class":713,"line":834},15,[711,836,837],{"class":716},"# Open a pull request\n",[711,839,841,843,846,849,852,855],{"class":713,"line":840},16,[711,842,699],{"class":722},[711,844,845],{"class":725}," pr",[711,847,848],{"class":725}," create",[711,850,851],{"class":761}," --title",[711,853,854],{"class":725}," \"Increase test timeout\"",[711,856,857],{"class":761}," \\\n",[711,859,861,864],{"class":713,"line":860},17,[711,862,863],{"class":761},"  --body",[711,865,866],{"class":725}," \"Bumps the CI timeout so flaky integration tests stop failing. Closes #123\"\n",[573,868,869],{},"After review, merge and clean up in one command.",[702,871,873],{"className":704,"code":872,"language":706,"meta":707,"style":707},"gh pr merge --squash --delete-branch\n",[583,874,875],{"__ignoreMap":707},[711,876,877,879,881,884,887],{"class":713,"line":73},[711,878,699],{"class":722},[711,880,845],{"class":725},[711,882,883],{"class":725}," merge",[711,885,886],{"class":761}," --squash",[711,888,889],{"class":761}," --delete-branch\n",[573,891,892,893,895],{},"That is the entire workflow. Branch, commit, push, PR, merge, delete. Because ",[583,894,585],{}," is shippable the moment that PR lands, you deploy right after.",[593,897,899],{"id":898},"branch-names-and-commits-that-do-not-make-you-wince","Branch names and commits that do not make you wince",[573,901,902,903,906,907,910,911,906,914,917],{},"Two small habits keep GitHub Flow pleasant. First, name branches for what they do. ",[583,904,905],{},"increase-test-timeout"," and ",[583,908,909],{},"add-code-of-conduct"," tell your teammates what is in flight at a glance; ",[583,912,913],{},"fix",[583,915,916],{},"wip"," do not. Second, keep each commit to a single, complete change with a message that says what it does. Small commits are easy to review and trivial to revert when something slips through. You are not writing a novel, you are leaving a trail the next person (often future you) can follow.",[593,919,921],{"id":920},"pull-requests-are-the-checkpoint","Pull requests are the checkpoint",[573,923,924,925,928],{},"The pull request is the heart of GitHub Flow, and it is more than a merge button. It is where the change gets explained, reviewed, and discussed. A good PR description says what changed and what problem it solves, links the issue it closes with a keyword like ",[583,926,927],{},"Closes #123"," so the issue closes automatically on merge, and pulls in the right reviewers with an @mention or a review request.",[573,930,931,932,934],{},"This is also where your automation does its job. Branch protection rules can require a passing CI run and at least one approval before the merge button lights up, which is what lets you trust the \"",[583,933,585],{}," is always deployable\" promise in the first place. The PR is your quality gate; treat it like one.",[593,936,938],{"id":937},"keeping-your-branch-fresh","Keeping your branch fresh",[573,940,941,942,944,945,947],{},"Because branches are short-lived, they rarely drift far from ",[583,943,585],{},". When one does, you bring ",[583,946,585],{}," into it before merging.",[702,949,951],{"className":704,"code":950,"language":706,"meta":707,"style":707},"git fetch origin\ngit merge origin\u002Fmain      # safe on shared branches\n# or, on a branch only you have touched:\ngit rebase origin\u002Fmain     # cleaner, linear history\n",[583,952,953,963,975,980],{"__ignoreMap":707},[711,954,955,957,960],{"class":713,"line":73},[711,956,15],{"class":722},[711,958,959],{"class":725}," fetch",[711,961,962],{"class":725}," origin\n",[711,964,965,967,969,972],{"class":713,"line":44},[711,966,15],{"class":722},[711,968,883],{"class":725},[711,970,971],{"class":725}," origin\u002Fmain",[711,973,974],{"class":716},"      # safe on shared branches\n",[711,976,977],{"class":713,"line":102},[711,978,979],{"class":716},"# or, on a branch only you have touched:\n",[711,981,982,984,987,989],{"class":713,"line":13},[711,983,15],{"class":722},[711,985,986],{"class":725}," rebase",[711,988,971],{"class":725},[711,990,991],{"class":716},"     # cleaner, linear history\n",[573,993,994,995,673],{},"Merge is the safe choice on anything someone else might have pulled. Rebase gives you tidy history but rewrites commits, so save it for branches that are yours alone. Resolve any conflicts here, on your branch, not on ",[583,996,585],{},[593,998,1000],{"id":999},"deploy-on-merge-or-deploy-before-merge","Deploy on merge, or deploy before merge?",[573,1002,1003,1004,1006,1007,1011,1012,1014],{},"There is one honest debate worth knowing about. Chacon's original flow says merge into ",[583,1005,585],{},", then deploy immediately. Plenty of modern teams flip that: they deploy the branch to a staging or preview environment and validate it live ",[1008,1009,1010],"em",{},"before"," merging, so ",[583,1013,585],{}," only ever receives code that has already proven itself in production-like conditions. GitHub's own branch-deploy style works this way.",[573,1016,1017],{},"Neither is wrong. Deploy-on-merge is simpler and keeps the loop tight. Deploy-before-merge gives you a real safety net at the cost of more tooling. Pick based on how much you trust your tests and how expensive a bad deploy is for you.",[593,1019,1021],{"id":1020},"hotfixes-are-just-normal-branches","Hotfixes are just normal branches",[573,1023,1024,1025,1028,1029,1031,1032,1034],{},"Here is the payoff of all this simplicity. In Git Flow, an emergency fix means a dedicated ",[583,1026,1027],{},"hotfix\u002F*"," branch off ",[583,1030,585],{},", merged back into two places and tagged. In GitHub Flow, a hotfix is just a normal short branch off ",[583,1033,585],{}," that jumps to the front of the review queue.",[702,1036,1038],{"className":704,"code":1037,"language":706,"meta":707,"style":707},"git switch -c hotfix-login-null-check main\ngit commit -am \"Add null check on the login handler\"\ngit push -u origin hotfix-login-null-check\ngh pr create --fill && gh pr merge --squash --delete-branch\n",[583,1039,1040,1053,1065,1078],{"__ignoreMap":707},[711,1041,1042,1044,1046,1048,1051],{"class":713,"line":73},[711,1043,15],{"class":722},[711,1045,758],{"class":725},[711,1047,762],{"class":761},[711,1049,1050],{"class":725}," hotfix-login-null-check",[711,1052,729],{"class":725},[711,1054,1055,1057,1059,1062],{"class":713,"line":44},[711,1056,15],{"class":722},[711,1058,794],{"class":725},[711,1060,1061],{"class":761}," -am",[711,1063,1064],{"class":725}," \"Add null check on the login handler\"\n",[711,1066,1067,1069,1071,1073,1075],{"class":713,"line":102},[711,1068,15],{"class":722},[711,1070,819],{"class":725},[711,1072,822],{"class":761},[711,1074,739],{"class":725},[711,1076,1077],{"class":725}," hotfix-login-null-check\n",[711,1079,1080,1082,1084,1086,1089,1093,1095,1097,1099,1101],{"class":713,"line":13},[711,1081,699],{"class":722},[711,1083,845],{"class":725},[711,1085,848],{"class":725},[711,1087,1088],{"class":761}," --fill",[711,1090,1092],{"class":1091},"suv1-"," && ",[711,1094,699],{"class":722},[711,1096,845],{"class":725},[711,1098,883],{"class":725},[711,1100,886],{"class":761},[711,1102,889],{"class":761},[573,1104,1105,1106,1108],{},"Same loop, same ",[583,1107,585],{},", just faster. There is nothing special to learn because there is nothing special about it.",[593,1110,1112],{"id":1111},"where-it-fits-and-where-it-strains","Where it fits, and where it strains",[573,1114,1115],{},"GitHub Flow is a great fit for web apps, services, and SaaS, anywhere there is really only one live version and you deploy often. It is friendly to continuous integration because you are constantly merging small changes instead of nursing a giant branch toward a release.",[573,1117,1118,1119,1121],{},"Two places it strains. It has no clean home for maintaining multiple released versions at once, so if customers stay on old releases you will want Git Flow's release branches instead. And \"",[583,1120,585],{}," is always deployable\" is only true if your tests and pipeline actually enforce it; without solid CI, that promise is wishful thinking.",[573,1123,1124,1125,1127],{},"It is worth knowing GitHub Flow's close relative, trunk-based development, which goes one step further: everyone integrates into ",[583,1126,585],{}," constantly, branches live for hours, and anything unfinished hides behind a feature flag. You can think of GitHub Flow as the comfortable middle ground, trunk-based development with pull requests and short feature branches still giving you a natural review checkpoint.",[593,1129,1131],{"id":1130},"wrapping-up","Wrapping up",[573,1133,1134,1135,1137,1138,1141,1142,1145],{},"GitHub Flow really does come down to that one rule: keep ",[583,1136,585],{}," deployable, and let short branches and pull requests carry everything else. If you ship a web app and deploy continuously, start here. If you ship versioned software with multiple releases to support, read the ",[577,1139,1140],{"href":579},"Git Flow deep dive"," instead, and if you are still deciding between them, my ",[577,1143,1144],{"href":589},"comparison article"," lays out exactly how to choose.",[1147,1148,1149],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}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 .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);}html pre.shiki code .suv1-, html code.shiki .suv1-{--shiki-default:#E1E4E8;--shiki-dark:#E1E4E8}",{"title":707,"searchDepth":44,"depth":44,"links":1151},[1152,1153,1154,1155,1156,1157,1158,1159,1160,1161],{"id":595,"depth":44,"text":596},{"id":622,"depth":44,"text":623},{"id":685,"depth":44,"text":686},{"id":898,"depth":44,"text":899},{"id":920,"depth":44,"text":921},{"id":937,"depth":44,"text":938},{"id":999,"depth":44,"text":1000},{"id":1020,"depth":44,"text":1021},{"id":1111,"depth":44,"text":1112},{"id":1130,"depth":44,"text":1131},{"id":13,"name":14,"slug":15,"hue":16},"If Git Flow is the structured, ceremony-heavy end of the branching spectrum, GitHub Flow is the opposite. It throws out the long-lived branches and release windows and runs on one rule: anything in main is deployable. Everything else follows from that. If you want the head to head, I wrote a Git Flow vs GitHub Flow comparison; this post is the hands-on deep dive into GitHub Flow itself.","md",{},{"title":29,"description":1163},"posts\u002Fgithub-flow-keep-your-main-branch-deployable",[15,22,25],[1170,1171,1172],{"name":19,"slug":15},{"name":21,"slug":22},{"name":24,"slug":25},"GiOiAoygsfFsRwg8VIT17hCNuwJ1UT1uFa2JcZK07sQ",1781454357270]