Andreas Thiel
Silver Contributor
FASTLANE INSIDER
Read Rat-Race Escape!
Read Fastlane!
Read Unscripted!
Speedway Pass
The way I imagine this working is: people who have an idea for a software product can pitch the functional vision, then the members with software development experience can write their take on it. If this thread takes off, it might become a great resource.
How would they approach it? What aspects can it be broken down into? What might be a rough effort estimation for aspects of the project? ... etc.
I know "Should I get into programming?" is a question that is often discussed here. Software-as-a-Service with subscriptions - and hence recurring revenue - has an undeniable appeal as a business model.
The thing about software development is that your intuition can be way off the mark. Subtle changes can make a world of a difference (Tasks), technical concepts (the solution domain) can be really tricky to align with the functional concept (the problem domain).
If my intuition is correct, then patterns should start to emerge and people who are "programming curious" could get a glimpse into the mind of people who have experience with executing on comparable ideas. Discussions could dispel myths and uncover wrong assumptions.
I will try to add my take as often as possible, but full disclaimer:
I am not very familiar with the Apple world and have more of a Desktop Workstation developer background.
I can write what I think I know about the mobile world (the same goes for Apple), but it won't be first hand experience.
I am also not too competent when it comes to operations topics, but since the world is moving into the DevOps direction, I know a little about what software developers can do in the concept phase to make operating the software easier.
How would they approach it? What aspects can it be broken down into? What might be a rough effort estimation for aspects of the project? ... etc.
I know "Should I get into programming?" is a question that is often discussed here. Software-as-a-Service with subscriptions - and hence recurring revenue - has an undeniable appeal as a business model.
The thing about software development is that your intuition can be way off the mark. Subtle changes can make a world of a difference (Tasks), technical concepts (the solution domain) can be really tricky to align with the functional concept (the problem domain).
If my intuition is correct, then patterns should start to emerge and people who are "programming curious" could get a glimpse into the mind of people who have experience with executing on comparable ideas. Discussions could dispel myths and uncover wrong assumptions.
I will try to add my take as often as possible, but full disclaimer:
I am not very familiar with the Apple world and have more of a Desktop Workstation developer background.
I can write what I think I know about the mobile world (the same goes for Apple), but it won't be first hand experience.
I am also not too competent when it comes to operations topics, but since the world is moving into the DevOps direction, I know a little about what software developers can do in the concept phase to make operating the software easier.
Dislike ads? Remove them and support the forum:
Subscribe to Fastlane Insiders.
