browse by category or date

Found via HN, rephrased for future reminder:

  1. Do not repeat yourself, always refactor/reuse, avoid copy-paste
  2. Name your variables for what they are for, not its type of data
  3. Name your methods for what they are going to do
  4. Don’t use magic number or string literals, use constants or readonly variables
  5. Strive to make your method testable (unit test, dependency injection, mock object)
  6. Don’t be afraid to ask for help
  7. See a bug? Fix it while you’re there, then move on
  8. Share your knowledge, it will help the point no. 6
  9. Don’t interrupt colleagues who are ‘in the flow’, related to point no. 6
  10. Take criticism with open-mind, defensive stance might turn this into religious-wars

Original source: 10 golden rules for becoming a better programmer

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

Yesterday I was editing the data of Complete Ferry Schedule using JSON Table Editor in Chrome. Immediately I found that the “Output to JSON” button is no longer works. I opened JSON Table Editor in other browsers (Firefox, Microsoft Edge, Opera) but found that the button works fine.

Looking into Chrome’s Developer Tools, I found why the button was not working.

json.table.security.error

Alas, it’s an Uncaught Security Exception. This is the offending line:

if (opener && opener.JSONTableEditor)
{
	// ... Snipped ...
}

This part of the code was supposed to check if the current window is actually a child of previous instance of JSON Table Editor (this happens when you edit a cell which has value of a complex JavaScript object). If it does, it will update the cell value in the parent window. If it doesn’t, it will show the formatted JSON on the bottom of the page.

The obvious work around would be putting this checking inside a try-catch:

var checkedOpener;
try {
   if (opener && opener.JSONTableEditor)
      checkedOpener = opener;
}
catch (ex) {
   //Nothing to do here
}
if (checkedOpener)
{
	// ... Snipped ...
}

Problem solved!

Final Thoughts

The error is unique to Google Chrome. This bug is already reported to Chromium team on Feb 2015. Unfortunately, until today the bug’s is not yet resolved.

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

About seven months ago, John Oliver, the Mega Reverend and CEO of the -now defunct- Our Lady of Perpetual Exemption (Be praise, be praise) warned USA about the dire state of the country’s infrastructures.

But alas, nobody heed to his call. And now they have this:

us.floods.2015

This reminds me of what my father used to say, “Prepare your umbrella before it rains”. But in this case, “prepare your dams before it rains heavily”.

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant: