Category: Programming

  • Catching Issues Before Customers Do

    Catching Issues Before Customers Do

    About ten years into my career, I had the opportunity to work on a large-scale, business-critical talent management software system. One part of the platform I focused on was the application workflow — the feature where candidates applied for jobs.

    This workflow might sound straightforward, but it was mission-critical. If it broke, candidates couldn’t apply, customers missed out on talent, and everyone lost valuable time. The challenge was that candidates themselves rarely reported errors; instead, our clients would eventually notice and file a bug report. By then, the damage had already been done.

    (more…)
  • From Reactive to Proactive: My “Light Bulb” Moment With Monitoring

    From Reactive to Proactive: My “Light Bulb” Moment With Monitoring

    About ten years into my career, I had one of those rare light bulb moments that completely reshaped how I approached engineering. Until then, I’d mostly thought of my role in terms of building features, fixing bugs, and keeping things moving. But thanks to a push from a colleague in product, I began to see things differently — not just as an engineer, but as someone responsible for the experience of real people using what we built.

    (more…)
  • From Gamer to Game Builder: My Journey

    From Gamer to Game Builder: My Journey

    It’s been a while since I last posted here. Life, work, and all the usual busyness pulled me away, but I’ve missed writing. So here I am, back again. My plan is to post more regularly, and I thought I’d start with something that’s been on my mind for a while: what it’s like to go from being a player of games to someone who helps build them.

    (more…)
  • johnro.net Now on AWS!

    My WordPress site is now on AWS! I spent a good chunk of my time debugging the All-in-One WP Migration plugin to get my migration working, and I finally realized I skipped an important step in their migration documentation:

    Migrate WordPress from PHP 5 to PHP 7

    1. Make sure that all plugins are deactivated. This will ensure your website error is not caused by any third-party software

    If you are getting stuck in the “Done Preparing Blogs” stage, then it could be because you didn’t deactivate all the plugins.

    Cheers!

  • Happy 2018!

    Happy new year! I have been lazy with my posts the past months (years?) so as part of my new resolutions I plan to write more.

    While I am here, I will leave a tip on how to better yourself as a software developer/enthusiast: practice, learn, practice. Continue to learn, and repetition is key to nailing information in your brain! Also, check out https://www.pluralsight.com or https://www.lynda.com for study material.

    Cheers!

  • xlsjs: “Error: Unrecognized ExtProp type: 2 0”?

    xlsjs: “Error: Unrecognized ExtProp type: 2 0”?

    While working on ETL (Extract, Transform, Load) projects at work, I ran into an unusual issue using xlsjs:

    Error: Unrecognized ExtProp type: 2 0

    After digging through the `xlsjs` source code, I realized that it was following the MS-XLS Specifications, as it should, and section 2.5.108 ExtProp, the extType value that I was running into was not defined in the table. Seeing as the format structure was related to formatting, I forked the `xlsjs` library and created a version that was more forgiving.

    If you are running into this issue and want a workaround, try xlsjs2.

  • git: Please properly rename / move files and directories

    git: Please properly rename / move files and directories

    I get frustrated when I browse a file from a git repository only to realize its history was lost due to improper renaming/moving of the file. It seems common for developers to manually rename/move a file in a git repository by using regular file system commands rather than git commands.

    For example, let’s look at the following:

    $ mkdir test
    $ cd test
    $ git init
    $ echo "hi" > test.txt
    $ git add test.txt
    $ git commit -m"add test.txt"
    $ mv test.txt test2.txt
    $ git status

    So what have we here? We start off by creating a new directory called test. We then go into the directory and start a new local git repository using git init. Next we create a new file called test.txt that contains simple text “hi”. test.txt is then added and committed to the repository. Finally, we use the mv command to rename the file to test2.txt.

    git status shows us the result:

    Git status after 'mv'
    Result of git status

    This is not what we were expecting. This shows that the original file test.txt was deleted and now there is an untracked new file called test2.txt, when it really should say that test.txt was renamed to test2.txt.

    Btw, this goes for moving files as well. For example, rather than renaming the file, if it was moved to, say, a different folder, e.g. newFolder/test.txt, the result would be the same.

    So how can this be solved? It’s actually not far off from the steps above. Let’s start with backtracking by reverting the rename:

    $ git checkout test.txt
    $ rm test2.txt
    $ git mv test.txt test2.txt
    $ git status

    Running the above commands produces the following result:

    Use 'git mv'
    Use ‘git mv’ to rename/move files

    Much better, isn’t it? Renaming/moving files from git repositories the proper way will allow retention of their history, which is what we want.

  • AWS: EB CLI Throws Exceptions VersionConflict and/or DistributionNotFound

    AWS: EB CLI Throws Exceptions VersionConflict and/or DistributionNotFound

    When running EB CLI, do you run into the following error?

    $ eb deploy
    Traceback (most recent call last):
      File "C:Python34libsite-packagespkg_resources__init__.py", line 635, in _build_master
        ws.require(__requires__)
      File "C:Python34libsite-packagespkg_resources__init__.py", line 942, in require
        needed = self.resolve(parse_requirements(requirements))
      File "C:Python34libsite-packagespkg_resources__init__.py", line 834, in resolve
        raise VersionConflict(dist, req).with_context(dependent_req)
    pkg_resources.ContextualVersionConflict: (colorama 0.3.3 (c:python34libsite-packages), Requirement.parse('colorama==0.3.7'), {'awsebcli'})
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "C:Python34Scriptseb-script.py", line 5, in <module>
        from pkg_resources import load_entry_point
      File "C:Python34libsite-packagespkg_resources__init__.py", line 2900, in <module>
        @_call_aside
      File "C:Python34libsite-packagespkg_resources__init__.py", line 2886, in _call_aside
        f(*args, **kwargs)
      File "C:Python34libsite-packagespkg_resources__init__.py", line 2913, in _initialize_master_working_set
        working_set = WorkingSet._build_master()
      File "C:Python34libsite-packagespkg_resources__init__.py", line 637, in _build_master
        return cls._build_from_requirements(__requires__)
      File "C:Python34libsite-packagespkg_resources__init__.py", line 650, in _build_from_requirements
        dists = ws.resolve(reqs, Environment())
      File "C:Python34libsite-packagespkg_resources__init__.py", line 829, in resolve
        raise DistributionNotFound(req, requirers)
    pkg_resources.DistributionNotFound: The 'colorama==0.3.7' distribution was not found and is required by awsebcli

    I ran into this error today. Apparently it was caused by installing AWS CLI after EB CLI:
    pip install awscli
    Reinstalling EB CLI solved the issue:
    pip install awsebcli

  • React: react-router and dynamic page title

    I have been learning React for the past few weeks, and I am loving it. I spent today learning react-router at https://github.com/reactjs/react-router-tutorial. After going through it and implementing a lot of it in my app, I realized that it did not cover one thing that I really need: dynamic page title.

    I have googled and looked at different examples of how others have done it (e.g. react-document-title, document.title) but I finally decided to tinker on my own and see if I can come up with my own implementation. (I know… another one???)

    My sample code will be added to the result of lesson 3 from the tutorial I linked above:

    App.js:

    import React from 'react'
    import { Link } from 'react-router'
    
    export default React.createClass({
      render() {
        return <div>
          <h1>
            React Router Tutorial
          </h1>
          <ul role="nav">
            <li>
              <Link to="/about">About</Link>
            </li>
            <li>
              <Link to="/repos">Repos</Link>
            </li>
          </ul>
        </div>
      }
    })
    

    index.js:

    import React from 'react'
    import { render } from 'react-dom'
    import { Router, Route, hashHistory } from 'react-router'
    import App from './modules/App'
    import About from './modules/About'
    import Repos from './modules/Repos'
    
    render((
      <Router history={hashHistory}>
        <Route path="/" component={App}/>
        <Route path="/repos" component={Repos}/>
        <Route path="/about" component={About}/>
      </Router>
    ), document.getElementById('app'))
    

    Looking at index.js, I thought why not add a title attribute on the Route nodes directly? That would be the most convenient location, in my mind.

    index.js:

    import React from 'react'
    import { render } from 'react-dom'
    import { Router, Route, hashHistory } from 'react-router'
    import App from './modules/App'
    import About from './modules/About'
    import Repos from './modules/Repos'
    
    render((
      <Router history={hashHistory}>
        <Route path="/" component={App}/>
        <Route path="/repos" title="Repositories" component={Repos}/>
        <Route path="/about" title="About Me" component={About}/>
      </Router>
    ), document.getElementById('app'))
    

    We added it to routing, but how will App get its value? This part is easy.

    App.jsx:

    import React from 'react'
    import { Link } from 'react-router'
    
    export default React.createClass({
      render() {
        return <div>
          <h1>
            {this.props.children.props.route.title}
          </h1>
          <ul role="nav">
            <li>
              <Link to="/about">About</Link>
            </li>
            <li>
              <Link to="/repos">Repos</Link>
            </li>
          </ul>
        </div>
      }
    })
    

    That’s it.

  • camelCase? underscore? dashes??

    I think it’s always confusing to know which to use, but I won’t get into that here. Instead, I will list the differences for future reference:

    • camelCase
    • PascalCase
    • snake_case
    • train-case
    • StUdLyCaPs
    • UPPERCASE
    • lowercase

    Juggling multiple programming languages on a daily basis, this still gives me a headache.