Archive for the ‘code’ Category
TL;DR I’ve been using Advent of Code as a way to practice Dart, try out ChatGPT, and learn from how other people approach the problems. ChatGPT quickly disappointed, but there’s still been plenty to learn, and I’ve found some things I’ll definitely take into my future coding. Also (value judgement here) I’m finding it much […]
Filed under: code, Dart | 1 Comment
Tags: Advent of Code, ChatGPT, Dart, Rust
TL;DR Bad input validation is the main underlying cause of many application security issues, because we haven’t made it easy enough for developers to implement good input validation. So how about a TypeScript[1] like language to resolve that – ValidScript – a language that makes it easy to do input validation? Background Wendy Nather recently […]
Filed under: code, security, technology | Leave a Comment
Tags: appsec, input validation, javascript, OWASP, security, TypeScript, ValidScript
Background I use Enterprise GitHub at work, and public GitHub for my own projects and contributing to open source. As the different systems use different identities some care is needed to ensure that the right identities are attached to commits. Directory structure I use a three level structure under a ‘git’ directory in my home […]
Filed under: code | Leave a Comment
Tags: .config, directory, email, enterprise, git, github
Marginal cost of making mistakes
In a note to my last post ‘Safety first‘ I promised more on this topic, so here goes… TL;DR As software learns from manufacturing by adopting the practices we’ve called DevOps we’ve got better at catching mistakes earlier and more often in our ‘production lines’ to reduce their cost; but what if the whole point […]
Filed under: code, culture, software | Leave a Comment
Tags: architecture, cost, design, DevOps, economics, mistakes, risk
Originally posted internally 16 Aug 2016: The title of this post comes from a tweet by Evan Goer I saw last week. It’s derived from Michael Pollan’s statement from In Defence of Food: ‘Eat food. Not too much. Mostly plants.‘ Write code Just as food fuels our bodies, code fuels our industry. The world is moving […]
Filed under: code, DXC blogs | 1 Comment
Tags: documentation
Originally posted internally 12 Jan 2016: PC sends out a weekly update for things happening in the Workplace offering, and this week he touched on the topic of programming languages. Rather than replying to him 1:1 by email I’m writing here because I’d like to have a more open debate. Before we start… take a look at […]
Filed under: code, DXC blogs | 1 Comment
Tags: coding, Go, golang, programming, R, Rust, Scala
Originally posted internally 6 Jan 2016: I’d meant to post this before the Christmas break as a guide to things to tinker with over the break, but then I hit the point where pretty much everybody seemed to already be on leave, and it was clearly too late…. So Happy New Year, if you’re not already […]
Filed under: cloud, code, Docker, DXC blogs | 2 Comments
Tags: Ansible, aws, cloud, code, config management, containers, Docker, Fork and Pull, git, github, infrastructure
micro:bit Simon
The BBC micro:bit is a computerised project board that’s being given to every year 7 (11-12yr old) kid in the UK. It’s supposed to encourage experimentation and learning to program in the same way that the BBC Micro (and associated BBC programmes) did back in the 80s. I’ve been pretty excited about it since the announcement, […]
Filed under: code, micro:bit | 2 Comments
Tags: accelerometer, game, micro:bit, python
Upgrading Docker
Dockercon #2 is underway, version 1.7.0 of Docker was released at the end of last week, and lots of other new toys are being launched. Time for some upgrades. I got used to Docker always restarting containers when the daemon restarted, which included upgrades, but that behaviour went away around version 1.3.0 with the introduction […]
Filed under: code, Docker, howto | 1 Comment
Tags: Docker, script, upgrade
Multi tier apps in Docker.io
Docker provides the means to link containers, which comes in two parts: Outside the container (on the docker command line) a ‘-link name:ref’ is used to create a link to a named container. Inside the container environment variables REF_… are populated with IP addresses and ports. Having linked containers together it’s then necessary to have a little […]
Filed under: code, Docker, howto | 3 Comments
Tags: address, app server, database, Docker, Docker.io, Dockerfile, enviornment, link, linking, MySQL, Nginx, port, Ruby, Sinatra, SSL, ToDoMVC, web server
Chris Swan's Weblog 