This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.
Agree? Disagree? Feel free to let me know at @JanStette.
Keep it simple, stupid. You ain't gonna need it.
| package kubernetes | |
| name = input.metadata.name | |
| kind = input.kind | |
| is_service { | |
| kind = "Service" | |
| } |
| /* | |
| X-Frame-Options: DENY | |
| X-XSS-Protection: 1; mode=block | |
| Referrer-Policy: no-referrer | |
| X-Content-Type-Options: nosniff | |
| Strict-Transport-Security: max-age=31536000; includeSubDomains; preload | |
| Feature-Policy: geolocation 'none'; midi 'none'; sync-xhr 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; fullscreen 'none'; payment 'none' | |
| Content-Security-Policy: default-src * 'unsafe-inline' 'unsafe-eval'; script-src * 'unsafe-inline' 'unsafe-eval'; connect-src * 'unsafe-inline'; img-src * data: blob: 'unsafe-inline'; frame-src *; style-src * 'unsafe-inline' |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.
| I think you mean team... | |
| I think you mean squad.. | |
| I think you mean gang... | |
| I think you mean pals... | |
| I think you mean buds... | |
| I think you mean posse... | |
| I think you mean phalanx... | |
| I think you mean crew... | |
| I think you mean crüe... | |
| I think you mean nerds... |
| ;original | |
| (filter filter-fn some-collection) | |
| ;parallel filter | |
| (map :val (filter (fn [m] (:allowed-by-filter m)) | |
| (pmap (fn [v] {:val s :allowed-by-filter (filter-fn v)}) some-collection))) |
| From a31eb2863043937881e51cffb544ef9a641a62af Mon Sep 17 00:00:00 2001 | |
| From: Yorick Peterse <SNIP> | |
| Date: Thu, 12 Mar 2015 11:08:46 +0100 | |
| Subject: [PATCH] Added a simple Maybe monad. | |
| This is a rather simple implementation of the Maybe monad [1] / Option type [2]. | |
| It only provides the absolute bare-minimum instead of providing a fully blown | |
| functional programming library. | |
| Using this class allows you to turn code such as this: |
| ;; Tomas Osland | |
| ;; [email protected] | |
| ;; @tomasosland | |
| ;; Welcome to this presentation about functional music. In this lightning talk we | |
| ;; will construct a drum machine and make som beats, play the piano, and experiment with synthesizers. | |
| ;; Start overtone.cid | |
| (ns overtone.examples.timing.one-bar-sequencer |
Every couple of weeks, I hear someone complaining about some difficulties with Bundler. Yesterday, it happened twice. But somehow I just never have those difficulties. I'm not saying Bundler is perfect; certainly in its early days it wasn't even close. But for the past two years it's been incredibly solid and trouble-free for me, and I think a large part of the reason is the way I use it. Bundler arguably does too much, and just as with Git, a big part of it is knowing what not to do, and configuring things to avoid the trouble spots.
