Very well written !! I always tell my team that business knowledge is more important than how to write code.
I call it “the story behind this requirement”, there is always a background about how each requirement came. If you know the background of the requirement, it will be easier for you to implement it and even suggest improvements.
Recently, Knowing the business, I was able to suggest integration of multiple applications to my product manager and delivered better products reducing the overall time of the process.
This is most of what I learned from the business analytics perspective in school. Converting business processes into a digital platform and retrieving the results is as much a human issue as it is technical. Excellent article.
English lad currently a C#/Java/VueJs/JavaScript/TypeScript engineer.
Extra dribbling can be found at https://codeheir.com
Portfolio found at https://lukegarrigan.com
Love this, I couldn't agree more. Knowing the jargon of the software you're writing and fully understanding the context makes coding much, much easier. Just simple constructs like variable/class/function names will have been decided upon with prior domain knowledge, so just getting to grips with these (Let alone logic) will require some fundamental grasp of the lingo.
Thank you, a great reminder :)!
A software developer should be a partner to product managers/business owners - someone, who's able to spar with ideas, ask challenging questions regarding the domain so both would win.
Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
I think this explains why so many specialized software areas have absolutely terrible software. Electronic health records, dispatch systems, traffic engineering are the examples I can think of off the top of my head. You need a lot of specialized domain knowledge to write software in any of those areas, and oftentimes unless you have had direct experience in that field you won't be able to sufficiently master it. The people writing these systems have spent a lot more time mastering the domain than studying software practices, so even if it looks like garbage or crashes randomly, it's still going to keep selling.
I always collect all good information about coding as much as I can. I love to do that and your information also very good. I'm a college student and after my classes most of the time I would like to spend in coding. And yes for my assignments I take help from edubirdie just because of time shortage. I don't write my writing stuff by myself but yeah all computer work I do by myself.
A web developer who combines branding, user interface design , web development & digital marketing, to improve sales. Proud that all of his clients came from mouth to mouth recommendation.
This applies to user interfaces as well. The last time i made a UI, i spent a LOT of time (More than 40 hours) just asking questions and gaining understanding of how the business worked. It was a complex foreign trade business. It went well cause the CEO was happy to explain it to me. Then I realized some stuff (some things they had on their current user interface) actually made sense, but it could be improved a lot.
Very well written !! I always tell my team that business knowledge is more important than how to write code.
I call it “the story behind this requirement”, there is always a background about how each requirement came. If you know the background of the requirement, it will be easier for you to implement it and even suggest improvements.
Recently, Knowing the business, I was able to suggest integration of multiple applications to my product manager and delivered better products reducing the overall time of the process.
This is most of what I learned from the business analytics perspective in school. Converting business processes into a digital platform and retrieving the results is as much a human issue as it is technical. Excellent article.
Love this, I couldn't agree more. Knowing the jargon of the software you're writing and fully understanding the context makes coding much, much easier. Just simple constructs like variable/class/function names will have been decided upon with prior domain knowledge, so just getting to grips with these (Let alone logic) will require some fundamental grasp of the lingo.
Thank you, a great reminder :)!
A software developer should be a partner to product managers/business owners - someone, who's able to spar with ideas, ask challenging questions regarding the domain so both would win.
I think this explains why so many specialized software areas have absolutely terrible software. Electronic health records, dispatch systems, traffic engineering are the examples I can think of off the top of my head. You need a lot of specialized domain knowledge to write software in any of those areas, and oftentimes unless you have had direct experience in that field you won't be able to sufficiently master it. The people writing these systems have spent a lot more time mastering the domain than studying software practices, so even if it looks like garbage or crashes randomly, it's still going to keep selling.
I always collect all good information about coding as much as I can. I love to do that and your information also very good. I'm a college student and after my classes most of the time I would like to spend in coding. And yes for my assignments I take help from edubirdie just because of time shortage. I don't write my writing stuff by myself but yeah all computer work I do by myself.
This applies to user interfaces as well. The last time i made a UI, i spent a LOT of time (More than 40 hours) just asking questions and gaining understanding of how the business worked. It was a complex foreign trade business. It went well cause the CEO was happy to explain it to me. Then I realized some stuff (some things they had on their current user interface) actually made sense, but it could be improved a lot.
Awesome.... Thanks for this wonderful piece.
This should be first chapter in Programming 101.
Love it!
Great stuff!