ryangittins
Joined 12 years ago
Joined 12 years ago
Respectfully, it is not.
It may feel silly to have a whole unit test for a one-line regex, but that one line can be really dense. If you wrote a function to parse the string without regex, that function would be complex enough to warrant a unit test, after all.
Introducing regressions when tweaking a regex in your application is also a big risk which unit tests can help mitigate.
If you really want to get technical: ., ?, and + are also shorthands. The formal definition of a regular expression is very minimal on purpose.
`.` is just `(a|b|c|...)` - List of all literal characters
`x?` is just `(x|)` - "x or empty string"
`x+` is just `xx*` - "x followed by zero or more x characters"
Whether this is exactly how they are implemented in any particular regex engine is an implementation detail, but formally there are very few operations which aren't just syntactic sugar.
The Doorman Fallacy is exactly this—thinking that one function of a job is the whole job. The doorman doesn't just open doors nor relay messages. They're eyes and ears, security, friendliness, an extra hand with bags, local knowledge, emergency response... The list goes on and on. Almost none of their functions can be replaced with an intercom.
We looked at Linear and other options but ultimately ended up going with Shortcut. We wrote our own small migration script and moved over the old Pivotal IDs to keep as much historical context as we could. Shortcut's been a good tool overall, though I preferred Pivotal's Goldilocks level of compactness as far as the UI was concerned, as well as the general design.
Pivotal's API was tidy and integrated nicely into our development process. We have some git aliases such as `git start <branch>` where the branch name will end with a story ID by convention. The alias would do the work of creating the branch, setting the remote to the dev's fork of our repo, marking the story as started, and assigning the dev as the owner. It saved a lot of manual steps, so thank you for your involvement in the project which allowed such a nice workflow!
RIP Pivotal Tracker, and thank you for your involvement! It was a nice piece of software.
I didn't realize I've been reading HN nearly its whole existence. For all my complaining about what's happened to the internet since those days, HN has managed to stay high quality without compromising.
As a kid I would browse their website endlessly, just fascinated by all the weird stuff. It scratched the same itch that watching Mythbusters would scratch. In adulthood I rediscovered them and went to their Milwaukee location for the first time. We spent hours there, looking through all the cool stuff they have. It really gives you ideas!
I wouldn't sweat this too much. Mathematically, most people have fewer friends than their friends have.
> Swoopers write a story quickly, higgledy-piggledy, crinkum-crankum, any which way. Then they go over it again painstakingly, fixing everything that is just plain awful or doesn’t work. Bashers go one sentence at a time, getting it exactly right before they go on to the next one. When they’re done they’re done.
I always found this frustrating in high school, as some assignments required submission of a first draft, second draft, and final version of a paper. I always wrote the final version first and then worked backwards to created a second and then a first draft by removing sentences and generally making it worse.
[ my public key: https://keybase.io/ryangittins; my proof: https://keybase.io/ryangittins/sigs/-IhsGZ4wOekWSyKWamev1azKTSNuQQTZyFn1H33ucAI ]
meet.hn/city/us-Madison