How difficult can development get?

semblance

Active Member
Joined
Apr 16, 2014
Messages
71
Reaction score
0
Greetings once again fellow developers and coders.

I'm a person who loves problems. I love the complexity of problems. The more challenging they are, the more interest I show in them. I'm sure some of you share this same sentiment.

However, I am battling in my mind to logically arrive at difficulty rating for my profession.

Here are my questions:

a) How difficult can development be in terms of problem solving? Bring out the really big guns here such as high scalability infrastructures, building frameworks and middle-ware for the masses to taking the lead on technologies and where they go.

b) What differentiates a mediocre developer from a great developer? Rather, what would make a developer unique or invaluable?

c) Do you think, in terms of pure problem solving skill and talent, that a developer could be to technology what a doctor can be to a patient? Do you think the problem solving levels are on par?

So in essence, is there a limit to the problems IT has at a given time? In my mind, it seems everything can be solved with software and logical design. Granted there is the limit of hardware (processing and memory), but that's more a resource limit (when solving developmental challenges). If you throw enough money at it (resources), it will be possible.

So what is impossible? What are the 'mysteries' of technology (development wise)?

Enlighten me and thank you!
 
Make money. Most systems I have seen have no real "mysteries" in them and is generally standard code to literally just CRUD database as needed(ecommerce,accounting,record keeping,apps).

Unless you are at the bleeding edge working on new or abstract system ideas, difficulty generally plateaus
 
Generally there isn't any IT problem that can't be designed etc. If you're really wanting a challenge then you probably need to focus on algorithms and probably on some other field/s like math or applied math.
 
The client wants a Bugatti...and when you present the first prototype he wants to know why it doesn't have a hook to to tow a trailer. Plus high road clearance for some casual off-roading.
 
Make money. Most systems I have seen have no real "mysteries" in them and is generally standard code to literally just CRUD database as needed(ecommerce,accounting,record keeping,apps).

Unless you are at the bleeding edge working on new or abstract system ideas, difficulty generally plateaus

Agreed, even factoring in language changes etc, things tend to stay similar.

things that could be challenging though if you had to program from scratch, say an application for this new technology http://io9.com/brain-inspired-microchips-simulate-one-million-neurons-1569184586

or you had to write a program to describe/simulate this http://www.openworm.org/

@semblance how do you define development?

Also I wouldnt say everything can be just solved with software and logical design. For example SKA is going to generate petabytes of information per day/week (cant remember now) and that has to sent to scientists across the world. The hardware is not exactly there to transport that amount of data sufficiently.
 
The client wants a Bugatti...and when you present the first prototype he wants to know why it doesn't have a hook to to tow a trailer. Plus high road clearance for some casual off-roading.
... and are you sure it looks like a Bugatti? I think the Ferrari shape would be better, just keep on calling it a Bugatti though :D
 
... and are you sure it looks like a Bugatti? I think the Ferrari shape would be better, just keep on calling it a Bugatti though :D

While you're at it, put extra seats in, as well as enough space for a week away. Just in case.

Why is it red? Can you make it yellow with spots, like that car I saw the other day. I'll send you the photo.
 
While you're at it, put extra seats in, as well as enough space for a week away. Just in case.
But why is it so slow all of a sudden...I order a Bugatti ffs. Fix it.

...lol not even in the dev game and I can relate.

EDIT: Hope I haven't derailed OPs thread. Sorry if you feel I did.
 
I've had to implement machine learning algorithms to track possible fraud on transactions within our infrastructure.
 
... and are you sure it looks like a Bugatti? I think the Ferrari shape would be better, just keep on calling it a Bugatti though :D

A great developer makes a volksie look like a Ferrari to the client.

One of my best moments was when we changed the name and logo of our in-house app and then the feedback we got was that we had done an amazing job of upgrading the previously very buggy system.
 
Nice, unsupervised or supervised? Are most useful features based on location?

Used a bit of supervision in training, but its mostly unsupervised now. Location is a a minor component in our environment.
 
Greetings once again fellow developers and coders.

I'm a person who loves problems. I love the complexity of problems. The more challenging they are, the more interest I show in them. I'm sure some of you share this same sentiment.

However, I am battling in my mind to logically arrive at difficulty rating for my profession.

Here are my questions:

a) How difficult can development be in terms of problem solving? Bring out the really big guns here such as high scalability infrastructures, building frameworks and middle-ware for the masses to taking the lead on technologies and where they go.

b) What differentiates a mediocre developer from a great developer? Rather, what would make a developer unique or invaluable?

c) Do you think, in terms of pure problem solving skill and talent, that a developer could be to technology what a doctor can be to a patient? Do you think the problem solving levels are on par?

So in essence, is there a limit to the problems IT has at a given time? In my mind, it seems everything can be solved with software and logical design. Granted there is the limit of hardware (processing and memory), but that's more a resource limit (when solving developmental challenges). If you throw enough money at it (resources), it will be possible.

So what is impossible? What are the 'mysteries' of technology (development wise)?

Enlighten me and thank you!

a) How difficult can development be in terms of problem solving? Bring out the really big guns here such as high scalability infrastructures, building frameworks and middle-ware for the masses to taking the lead on technologies and where they go.

That depends a lot on the team you have around you and the support you get as a pool of thinkers. Some developers work best alone, others like myself work better with a team. In my experience, try to specialize in something. I work with a team of 4 coders, we each have a specialization; Web Development, Logistics, Finance and last one on Data. We are all developing the same program but each compliment each other (a scrum environment) so to speak. My area of interest is cargo tracking and vehicle tracking (mileage, incidences, hijackings and theft). Try to find your niche.

b) What differentiates a mediocre developer from a great developer? Rather, what would make a developer unique or invaluable?

Communication. Work closely with your source of information and most of all, give your head developer, client, manager regular updates and don't be afraid to ask for scrum feedback. Grab them by the collar if you're unsure about the process of let's say a stock report. Showing enthusiasm and drive makes you invaluable.


c) Do you think, in terms of pure problem solving skill and talent, that a developer could be to technology what a doctor can be to a patient? Do you think the problem solving levels are on par?

Practice and practice. Talent is 10%, practice and repetition are the other 90. Remember that. Don't be an island in software development when it comes to understanding business practices, always get advice, every company and program is different. I work very closely with my colleagues in shipping and I'll tell you something about people, they love sharing information but what makes you get the job done is to present the software as is, and not allow them to give you the run around on everything they would like to have.

For eg, no software is exactly what you would wish for, but it get's the job done. Don't be to offering and say: "Sure this can be done, whatever you want." That's a huge mistake and they will bog you down from now until next year.
 
I will say lastly and I'm sure every developer here would agree, your best experience gained is the experience of being thrown into projects and learning from there. No one situation is alike so be flexible and most of all, take for granted that some things just work. Don't over-think things just get the job done.
 
Difficulty depends on the problem you are solving. Building enterprise type apps is pretty easy. Doing realtime machine vision is next level stuff...
 
I will say lastly and I'm sure every developer here would agree, your best experience gained is the experience of being thrown into projects and learning from there. No one situation is alike so be flexible and most of all, take for granted that some things just work. Don't over-think things just get the job done.
Agreed. Though I'd like to add that scale matters. i.e.

i.e. Being 100% in charge of a small project provides more learning opportunities than partial responsibility on bigger projects. There is something very "real" about being told...this is your project...succeed and the glory is yours, fail and you will burn. Go.
 
Top
Sign up to the MyBroadband newsletter
X