Explore >> Select a destination
|
You are here 
|
rgoswami.me | ||
| | | | |
vxlabs.com
|
|
| | | | | Introduction Just the other weekend, I had to exchange contact details using quite primitive means with a fantastic new friend after a deeply enjoyable hike up Table Mountain via the India Venster route. We could not get the flashy new iPhone-bump method to work. Although the animation triggered with each bump, no contact details were exchanged, a failure which caused the Android user at the table much mirth. That incident drove me to retrieve some old Python code I had written to try out Segno, a QRCode... | |
| | | | |
www.teamblind.com
|
|
| | | | | I work currently for a company with about 400 people. Recently we had a bunch of engineering resignation. All staff level and above, some of the most senior founding engineers left. Corporate is playing this as an "opportunity" for everyone to ste... | |
| | | | |
www.paedubucher.ch
|
|
| | | | | Personal Website of Patrick Bucher (paedubucher), mostly about IT-related topics (programming) | |
| | | | |
enterprisecraftsmanship.com
|
|
| | | Hard coding is often considered an anti-pattern. Having values that can change over time hard-coded in the source code requires recompilation every time these values actually change. While this statement is true, I think that hard coding should be the default choice when developing an application. Hard coding vs configuration file When you work on a project or feature, there always are some magic numbers or strings that potentially can change in future. | ||
