2,918 karma · joined October 31, 2013
In brief though, let's say you're implementing network filtering (inspired by today's LittleSnitch post).
Before writing any code, I would:
- Figure out what actual business case there is behind it and what the management/customer/etc is actually looking for. Maybe feature XYZ isn't the right long/short-term solution for what they want. People give Steve Jobs a lot of flack for "you're holding it wrong", but he was right in the sense that the customer doesn't always know what they want/need, let alone know what's even possible.
- Once the feature is what is required, figure out what's the right fit for the feature within the current architecture with short/medium/long-term goals in view. Maybe it's actually better to hack something in quickly and commit to revisit in 1 week than spend a month doing it right and lose users.
- Then figure out if the APIs actually exist. Some APIs you need simply don't exist. For example, in order to filter network traffic on MacOS, you needed to write a kernel extension until macOS Catalina. If your architecture/business doesn't have room for kernel extensions, then those APIs are out of reach. (Maybe Apple didn't bless your request to code sign kexts. Maybe you have no-one on your team with kernel experience. Maybe your customers are non-admin users on their Macs that can't load kexts.) During this phase, I might write some quick & dirty PoC code later in the process to exercise all the necessary APIs and make sure those actually do what they promise to do within my constraints.
Once you have the business requirements, stakeholders aligned, and PoC that exercises all the APIs which demonstrate your feature's needs, writing the actual code is a breeze. Especially once you get pretty good at this, transforming the PoC code into one that stands the test of time in your product gets easier and easier.
You may ask "wait, writing the PoC code is exactly what you claimed you didn't do!". You've got a point, except in this case, whenever I write PoC code, I write it as a standalone "proving grounds" program. I don't start writing code within the product's architecture. I would estimate in my PoC code, there's less than 3% that is outside of exercising the necessary APIs.
As for public/other computers that I don't get to configure: I found that I never really lost any speed on Qwerty. Whether that's the norm or I got lucky, I am not sure. Also, I find Dvorak to be available on most systems where the user can configure their input settings. Windows, Mac, and most Linux has Dvorak support built-in that are as easy to add as if you were adding another locale's keyboard layout.
I speak from personal experience as this happens regularly in Xcode for large iOS projects. Xcode is notorious for its fragile indexing system. Symbols are often not correctly picked up, and autocomplete is notoriously unreliable when the projects get large. This happened often enough that it actually trained me to become much more comfortable writing code for long periods of time without relying on autocomplete at all.
If autocomplete/IDE indexing system lags behind or is unavailable for even 0.5% of the time, that translates to real time where the developer is waiting for the autocomplete list to appear.
With Python, Ruby, and other languages, one has a plethora of IDEs/editors/environments to choose from. However for Objective-C or Swift, the environment is severely limited. AppCode does exist, and it does have a much better indexer and autocomplete, but it is very different than Xcode and most iOS developers will not be able/willing to move to AppCode. And that's even before considering their licensing costs.
With most helpful aids, I would say that autocomplete is a gift and useful day-to-day, but to make it a central dependency during the development phase seems to be a mistake.
Whether or not this page can be trusted, we'll have to see what people find out (I sure ain't going to pay for it to do that myself).
> Police - 999
> Ambulance - 997
> Fire - 998
> Traffic police - 993 Mobile phones - 112 or 911
> Non-emergency ambulance - 1777
> Police hotline - 1800 255 0000
> Traffic police - 6547 0000
None of them seem to be correct, except for 911. In the United States, 911 is the same for police, ambulance, fire, and "traffic police". Also, non-emergency ambulance/police are all varied depending on your current location and are usually administered by the county/city/district that you're in. There is no global number (that I'm aware of) that is the nearest non-emergency police/ambulance line.
Wow!