Saving fish by writing code! Applications developer in fisheries, specializing in webapps and moving 'enterprise-y' legacy systems to modern agile systems - Email or tweet me if you want to talk!
I guess since I'm asking the question, I'd better tell my own story...
I started coding sometime in either the late 90's or early 2000's. My first coding was really simple websites and javascript. Later, in college, I coded a fair amount in Python for physics simulations. I also coded in Java for intro programming classes.
After graduating, I worked at the US Patent Office for a couple years and didn't really do any professional coding. I did keep tinkering with some of my physics simulations - mostly fine tuning a solar system gravity and relativity model.
In 2009, I was hired at NOAA as an applications developer. I started with junior developer tasks - bug fixes and implementing simple new features, mostly for our email handling daemon. I graduated to implementing new systems from scratch.
The first new system that I designed was an electronic logbook for fishers in the Bering Sea. It is still running and helps them report how much fish they caught, and where, as well as other activities they did during the day.
As I gained skill, I accumulated responsibilities. I became the lead developer for our internal permit issuing application. I created a continuous integration environment and pushed the region to use Maven for Java projects and node+npm for front end projects.
After running the internal permitting system for a while, some shortcomings became apparent. The system was composed of multiple independent domains, each with their own stakeholders and release cycle, but everything was tightly coupled together. At first I patched things together with increased testing and automation, and human-process spackle.
After a certain point, I decided a significant refactor was required, and gained management and stakeholder support for the refactor effort. I developed an architecture to facilitate splitting the system into its child domains, so a problem in domain A is not a problem for domain B. I settled on a message bus based architecture with small domain-specific services talking to each other over a queue.
Meanwhile, on the front end, our Adobe Flex based system clearly needed replaced with JavaScript before the sun set on Flash in the browser. I have been working with a small team to develop a RESTful gateway for the message bus and a collection of React-based JavaScript apps to replace the Flex monolith. We are also taking the opportunity to implement a workflow based system that guides users through the steps they need to take in the order they need to take them.
Now my days look like some front end coding here, some backend coding there, some mentoring here, some planning there, and lots of creating automation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I guess since I'm asking the question, I'd better tell my own story...
I started coding sometime in either the late 90's or early 2000's. My first coding was really simple websites and javascript. Later, in college, I coded a fair amount in Python for physics simulations. I also coded in Java for intro programming classes.
After graduating, I worked at the US Patent Office for a couple years and didn't really do any professional coding. I did keep tinkering with some of my physics simulations - mostly fine tuning a solar system gravity and relativity model.
In 2009, I was hired at NOAA as an applications developer. I started with junior developer tasks - bug fixes and implementing simple new features, mostly for our email handling daemon. I graduated to implementing new systems from scratch.
The first new system that I designed was an electronic logbook for fishers in the Bering Sea. It is still running and helps them report how much fish they caught, and where, as well as other activities they did during the day.
As I gained skill, I accumulated responsibilities. I became the lead developer for our internal permit issuing application. I created a continuous integration environment and pushed the region to use Maven for Java projects and node+npm for front end projects.
After running the internal permitting system for a while, some shortcomings became apparent. The system was composed of multiple independent domains, each with their own stakeholders and release cycle, but everything was tightly coupled together. At first I patched things together with increased testing and automation, and human-process spackle.
After a certain point, I decided a significant refactor was required, and gained management and stakeholder support for the refactor effort. I developed an architecture to facilitate splitting the system into its child domains, so a problem in domain A is not a problem for domain B. I settled on a message bus based architecture with small domain-specific services talking to each other over a queue.
Meanwhile, on the front end, our Adobe Flex based system clearly needed replaced with JavaScript before the sun set on Flash in the browser. I have been working with a small team to develop a RESTful gateway for the message bus and a collection of React-based JavaScript apps to replace the Flex monolith. We are also taking the opportunity to implement a workflow based system that guides users through the steps they need to take in the order they need to take them.
Now my days look like some front end coding here, some backend coding there, some mentoring here, some planning there, and lots of creating automation.