Bikeshedding Names Considered Harmfull

[palimondo (Pavol Vaskovic)]

There was more to be said:

On Grammar

I dread the moment when the phrase ”grammatically correct English” inevitably comes up in bikeshedding session, because it is now a dog whistle for all the grammar police to come out. It is the exact moment when the native speakers rediscover their English-pride and start to hijack the naming conversation with arcane minutiae of the proper English. Naming in programming isn’t hard because we didn’t all ace the Cambridge exam; it’s hard because as programmers are we naming abstract concepts we d…

The Swifty Bikeshed

Language matters! Now I am talking about words and what they mean. Swift Evolution seems to have embraced the word bikeshedding, like people that proudly self-identify as grammar police, we have appropriated it to mean “engage in long naming debate”. But it is not right. It has an important meaning. We need to restore that. Otherwise this turn of newspeak serves as an open invitation for endless wasting of our collective time. Bikeshedding offends me, and it should offend you. When I call you o…

I’m not sure there aren’t more , until a proper response to this get’s me back to coding:

Towards Robust Performance Measurement

I’m kind of new around here, still learning about how the project works. On the suggestion from @Ben_Cohen I started contributing code around Swift Benchmark Suite (more benchmarks for Sequence protocol along with support for GYB in benchmarks). I’ve filed SR-4600 back in April of 2017. After rewriting most of the compare_perf_test.py, converting it from scripting style to OOP module and adding full unit test coverage, I’ve been working on improving the robustness of performance measurements wit…