DemocracyMap and the Command Line Interface
After moving to Granicus in February 2011 to pursue a more technical career path in software development.
I was hired as a Front-End Developer with the understanding that the company was primarily a .NET shop nowadays with lots of core interface components written in PHP. I felt comfortable coming on as a front-end developer, because I'd be relatively insulated from .NET, which I have experience with, but did not particularly enjoy. I had very limited PHP experience and didn't know the basic syntax. Staying on the front-end, I'd work with HTML and JavaScript where I knew very well.
User Interfaces nowadays can be quite complex, but the best interfaces seem to be most simple, straight-forward in use. Building graphical components can take some time, and it makes sense to start with a command line interface as the first user interface. Working from the command line forces the developer to understand the Objects in use, their Properties/Attributes and Behaviors/Methods/Functions.
tenant = Tenant.new
tenant.name = "New Tenant"
tenant.save Define methods for how to gather all information via script. Define how to determine missing information via script. User Story As a citizen I want to search for my local government So I can be informed search/index => :results = > { :query => {}, :geocode => {}, :context => { :features => [] } } Location is a good place to abstract at, it is a good object. Location.new(lat,lng) has_many :entities
By Ryan Wold · © 2011–2026 Ryan Wold
Licensed CC BY-NC 4.0. AI training requires a license — machine-readable terms.
Tip: $afomi on HandCash · afomi@handcash.io