Programming Leftovers
-
My favorite little Markdown feature: reordering ordered lists
In short: in Markdown, you can write
1.for every list item instead of1.,2.,3., etc.Markdown lets you make ordered lists, like so: [...]
-
Learn to ‘Make an outstanding Shiny App’ with us
Find out how to customize a shiny app and make it more accessible to users with our workshop on 14/06.
-
Funny Programming Pictures Part XXXV
I laughed no less than three times while putting this together. THREE TIMES I SAY.
-
Git Switch vs. Checkout: A Detailed Comparison with Examples
Git is an industry-standard distributed version control system used for software development and other version control tasks. It facilitates collaboration, allowing multiple contributors to work on a project concurrently without overriding each other's changes.
-
How to discover all the data sources, low-fuss way
Sometimes you need to understand what databases and data sources your company uses. I’d like to show how I do that. I use a small spreadsheet that lists all the data sources, with just half a dozen questions about each data source.
This is mainly a personal tool: it will help you to organize your thoughts if you need to have a discussion with somebody, or with your team.
-
On Software Dependency Engineering
Note: I have worked at Google for the majority of my professional life, which will color my views. Take with a pinch of salt, remember that everything here is my own views and do not represent that of Google or anyone else.
-
[Repeat] Feedback: I try to answer "how to become a systems engineer"
Seriously though, if you look up "systems engineering" on Wikipedia, it talks about "how to design, integrate and manage complex systems over their life cycles". That's definitely not my personal slice of the world. I don't think I've ever taken anything through a whole "life cycle", whatever that even means for software.
In the best case scenario, I suppose some of my software has gotten to where it's "feature complete" and has nothing obviously wrong with it. Then it just sits there and runs, and runs, and runs. Then, some day, I move on to some other gig, and maybe it keeps running. I've never had something go from "run for a long time" to "be shut down" while I was still around.
This is not to say that I haven't had long-lived stuff of mine get shut down. I certainly have. It's just that it's all tended to happen long enough after I left that it wasn't me managing that part of the "life cycle", so I heard about it second- or third-hand and much much later.