Skip to main content

Basic Prototype App with Symfony3

The objective of this is to build a simple route, and controller that handles this entire “application.”

The components of this simple prototype are essentially a bunch of HTML pages with interaction hard-coded or baked into the twig templates. So the objective here is to build the structure such that building a new template is all that is required and the application will then pick it up.


  1. Separately a custom controller handles exception catching and 404 errors.
  2. Everything, including authentication/authorization can be “faked”
    1. Presumably you’d hide this behind HTTP-Basic or keep local only.

The Route

The Controller

How it Works

Now all you need to do is build your filenames to match and you can create template files that work out of the box.

Now your routes map to filenames, which for the purposes of a simple static HTML prototype makes things very easy for any designer or developer to add and work with:

Route (path) Template filename
/jake/home DemoBundle\Resources\views\Jake\home.html.twig
/auth/forgot-password DemoBundle\Resources\views\Auth\forgot-password.html.twig
/jake/dashboard DemoBundle\Resources\views\Jake\dashboard.html.twig

The death of my friend MP3

In the wake of recent news Fraunhofer Institute for Integrated Circuits IIS has officially put the MP3 out to pasture, I am reminded of the joys technology can bring to our lives.

Excluding the moral debate (or not) of a particular file-sharing platform, I recall my non-malicious use of said platform very fondly as I was a teenager discovering music in ways exponentially faster than my parents did a generation before. At the time I was the lucky one with a broadband connection, and my friends and I would binge share music we had discovered. I distinctly remember being introduced to a local band in Chicago named SOiL (a must if you enjoy hard-rock/metal). Something I would have never discovered without the advent of the MP3 and thereby file-sharing in its infancy, like it or not. Similar experiences followed with Mudvayne, Local H, Chevelle, From Zero and even Brawl (before they became Disturbed, we “ripped” their CDs and shared voraciously).

Rest In Peace MP3; my old friend.


An agile life made simpler with JIRA “subscriptions”

I spent more or less every working second of my day affixed to JIRA in one way or another. Whether reporting to product owners, clients, executives or even fellow engineers one way or another a question asked is answered with a JIRA query.

A great many of these questions are asked repeatedly; perhaps multiple times each day.

For these questions, there are subscriptions. A wonderful feature in JIRA that is shockingly under utilized by my peers and colleagues.

I present to you, the simple 6 step process that will surely free up some of your precious time (and patience).


Step One

“Search” for issues, and identify the query you are attempting to run. Typically I’m asked “how many bugs are being worked on right now?” at least once per day. A simple query that can be easily addressed with a custom search.

Step Two

Here you simply select the filter options you care about; doesn’t get much more straight forward.


Step Three

Optionally, you may want to customize this beyond the simple point and click solution built in with JIRA.

For example, you may want to find all bugs being worked on right now by everyone but yourself. In that case you’d click Advanced and alter your query to this:

issuetype = Bug AND status = 'In Progress' AND assignee NOT IN(jake.litwicki)


Step Four

When you’ve got the data you want, I’d recommend saving this filter via Save as so you can access this again on demand with your Quick Filters on the left menu. (It will appear here after saving).


Step Five

Separately, you’ll click Details which will give you the option to the New subscription option, which is where the money is made


Step Six

Finally, you customize the subscription here as desired. You can be as granular as you’d like, going to far as to customize identically to a crontab entry. Or a simple “email me once every day at 5PM” for the simple queries your colleagues ask you every day.

In either case, if you haven’t already discovered this option, you’re welcome!