Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    media monitoring
    Signals In The Noise: Using Media Monitoring To Manage Negative Publicity
    5 Min Read
    data analytics
    How Data Analytics Can Help You Construct A Financial Weather Map
    4 Min Read
    financial analytics
    Financial Analytics Shows The Hidden Cost Of Not Switching Systems
    4 Min Read
    warehouse accidents
    Data Analytics and the Future of Warehouse Safety
    10 Min Read
    stock investing and data analytics
    How Data Analytics Supports Smarter Stock Trading Strategies
    4 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Here’s a couple of skills developers will need in the years ahead
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Business Intelligence > CRM > Here’s a couple of skills developers will need in the years ahead
Business IntelligenceCRMData MiningPredictive Analytics

Here’s a couple of skills developers will need in the years ahead

JamesTaylor
JamesTaylor
4 Min Read
SHARE

I saw this list of 10 skills developers will need in the next five years – developers not programmers you notice – and I was struck by several things.

First and foremost it still assumed that application developers would be programming – not assembling applications from components, not specifying the behavior of a system in a declarative way but programming. This seems like a major no-no to me. Surely in the next five years application developers will finally realize that declarative and model-driven approaches should replace hard-coding in a procedural language? Using a BPMS to specify workflow and process, a BRMS to specify business logic and a BI tool to specify reports all seem like no-brainers. Why would you code this kind of thing? If you do you are just creating a new generation of legacy applications. Application Development 2.0 is surely called for and a key element in Application Development 2.0 is a focus on declarative.

I was also struck by the absence of analytics from this list. With so much data already in organizations and the volumes/timeliness of this data only increasing, surely developers need to understand the power of analytics to improve systems and decision.…

More Read

Geek out @ LtU – process calculi and the philosophy of the infinite
SQL Visualization in the Spreadsheet
Nations’ Privacy Laws Clash
Predictive analytics – some tips
Podcast: Data Governance is Mission Possible


I saw this list of 10 skills developers will need in the next five years – developers not programmers you notice – and I was struck by several things.

First and foremost it still assumed that application developers would be programming – not assembling applications from components, not specifying the behavior of a system in a declarative way but programming. This seems like a major no-no to me. Surely in the next five years application developers will finally realize that declarative and model-driven approaches should replace hard-coding in a procedural language? Using a BPMS to specify workflow and process, a BRMS to specify business logic and a BI tool to specify reports all seem like no-brainers. Why would you code this kind of thing? If you do you are just creating a new generation of legacy applications. Application Development 2.0 is surely called for and a key element in Application Development 2.0 is a focus on declarative.

I was also struck by the absence of analytics from this list. With so much data already in organizations and the volumes/timeliness of this data only increasing, surely developers need to understand the power of analytics to improve systems and decision-making.

I did like the articles focus on soft skills – always key and easy for those of us focused on technology to forget.

In case you missed them, here are three posts addressing the core issue of declarative logic definition:

  • Business Rules to Programmers: Methink thou doest protest too much I
  • Business Rules to Programmers: Methink thou doest protest too much II
  • Business Rules to Programmers: Methink thou doest protest too much III


Link to original post

TAGGED:decision management
Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

ai in video game development
Machine Learning Is Changing iGaming Software Development
Exclusive Machine Learning News
media monitoring
Signals In The Noise: Using Media Monitoring To Manage Negative Publicity
Analytics Exclusive Infographic
data=driven approach
Turning Dead Zones Into Data-Driven Opportunities In Retail Spaces
Big Data Exclusive Infographic
smarter manufacturing
Connecting the Factory Floor: Efficient Integration for Smarter Manufacturing
Infographic News

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

First Look – IDIOM Decision Manager

11 Min Read

Analytics: Not About Saving Time

7 Min Read

Flexible yet permanent – the power of business rules

5 Min Read

Smart meters need smart systems, not a better user interface

6 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

giveaway chatbots
How To Get An Award Winning Giveaway Bot
Big Data Chatbots Exclusive
ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?