dwmkerr.com

Quick Links: ChatGPT Diagrams on the Chrome Web Store | ChatGPT Diagrams on GitHub The ChatGPT Diagrams browser extension makes it extremely easy to create diagrams with ChatGPT. Here’s how the extension looks in action: How to create diagrams To create diagrams, just follow the steps below: Install the ChatGPT Diagrams from the Chrome Web Store Enter a prompt asking to draw a diagram - and make sure you include the text “use mermaid syntax”, for example: Show the basic building blocks of a chrome extension using mermaid syntax ChatGPT will output some code - press the “Show Diagram” button above the code block to render your diagram That’s it!

installation and setup GOROOT src bin Source Code Structure Modules TODO definition of a module Packages TODO definition of a packge The go.mod File module github.com/dwmker/jac go 1.20 Protobufs Note that if using: protoc --go_out=. --go-grpc_out=. --go-grpc_opt=paths=source_relative proto/*.proto You will spit out a folder tree like github.com/dwmkerr/whatever, to omit this tree and use relative paths, include the options below: protoc --go_out=. --go_opt=paths=source_relative --go-grpc_out=. --go-grpc_opt=paths=source_relative proto/*.proto " Press ? for help

I recently needed to be able to generate a simple face image, with the face being able to scale from happy to sad. (Why I needed to do this is a long story!) This gave me the opportunity to have a play with SVG, which is something I’ve not done in a while and always wished I could spend more time with. You can see the result below, move the slider to see the smile animate:

In this article I’m going to demonstrate some simple tips and tricks which will help you build and maintain beautifully simple mobile build pipelines. These techniques can be applied to different mobile app technologies and integrated into almost any build system: Each tip is demonstrated in the sample apps in the dwmkerr/beautifully-simple-app-ci repo. The Challenges of Mobile App CI Tip 1 - Embrace Makefiles for Consistency Tip 2 - Control Version Numbers with a ‘Touch’ Command Tip 3 - Control App Icons with a ‘Label’ Command Tip 4 - Support Configurable App Ids Tip 5 - Document, Document, Document Conclusion The Challenges of Mobile App CI Conceptually, a mobile app CI pipeline is pretty simple:

If you are interested in improving your Node.js debugging skills, then check out my talk at the recent JSChannel 2016 conference in Bangalore: Comments and observations are always welcome!

I’ve just finished working on a very large project written in React and Redux. The whole team were new to both and we loved them. I’m going to share my experiences of experimenting in Angular 2 with you, from the point of view of someone who needs a pretty compelling reason to move away from my JSX and reducers. The Journey So Far Let me highlight a few key moments in my UI development experiences, to give a bit of context to my ramblings.

If you are looking to get your hands dirty and learn all about Docker, then look no further! In this article I’m going to show you how Docker works, what all the fuss is about, and how Docker can help with a basic development task - building a microservice. We’ll use a simple Node.js service with a MySQL backend as an example, going from code running locally to containers running a microservice and database.

Feeling like having a go with Facebook’s hugely popular React framework but not sure where to start? In this post I’m going to build a simple React application from scratch - using ECMAScript 6. We’ll put together the bare minimum skeleton of a site and keep the folder structure free of noise and clutter so that you can focus on the app code and not the tooling! The simple app we’ll build is at github.

I was working on a small and simple application built with AngularJS the other day. As with most applications like this, I start with a single JavaScript file caled app.js and no module system. In the past I’ve used RequireJS with AngularJS. It’s an awful mistake. It leads to a big jump in complexity with no benefts. Angular apps don’t work well with AMDs, so really your are using RequireJS to combine files into one big file.

Dealing with memory leaks in JavaScript applications can be a complex process. In this article I’m going to show you how to identify whether you have memory leaks, analyse them and ultimately resolve them. I’m using an AngularJS application to demonstrate the concepts and approaches, but much of this material applies to any JavaScript application. Understanding Memory Leaks What is a Memory Leak? Why is a Memory Leak Bad?