How Do You Build Systems Using Python?

[viruscore1]

True but we don't learn by learning how to create systems first doing abstract things like architecture design. It's more logical to learn how to program first. You don't go straight into a career as a system architect, without having earned your spurs writing the bits and pieces .
And with modern Agile development we generally write programs that provide immediate functionality and then incrementally extend them, rather than doing all the system development up front. This isn't the 1970's anymore.
For a beginner it's a pretty reasonable path to learn how to get some data, run a simple indicator over it, and produce some trades which they can then trade manually. That IS a system. It might not have been formally specified up front or be pretty, or have nice abstraction, but it's going to teach the beginner a lot of what they will need to do a much better job with the next iteration, or the bigger project which does more complicated things.
Learning some formal system design principles can come later, it's better to learn how to write decent code first, and even before that the OP is going to have to learn to write cruddy code.
GAT

you know agile is a joke invented by Australians that didn't understand the systems development lifecycle. And for newbies attempting to impress others but throwing around buzz words like scrum for meetings. Agile didn't invent anything new, just more bs for something that aready existed but that's beyond your comprehension. Anyhow i took the title literally. The writer may have many years of programming in another language attempting to develop a system in python. No matter how you cut it. All the deliverable's must be addressed one way or another, regardless of formality or granularity to complete a system or a program. Been there done that too many times and become tired of dealing with newbies that think a program is a system. hahaha

 

[viruscore1]

If you read the first post in this thread, you may agree with me he's most likely talking about "trading systems", not necessarily wanting a fully-fledged "application system", or some other sort of system like an "OS". Otherwise, why not just use what's prepackaged and already available for free?

So this is why programmers rarely hold any fun parties, and why many people complain about developers (and Ops-people) not listening properly.

I rarely ponder much on the differences between a system vs a program anyways, as it all depends on requirements. To develop trading systems you need to experiment and learn, so making a rigid application system may not be the best priority. If you aim to beat the market leaders in this segment, you may spend so much time making the application system, you never get to actually trade.

Sorry but you're miss informed. A system has many programs and procedures. No one is talking about an OS, you know that's an acronym for "operating system", such as windows, linux, and whatever fruit computers use, which really their version of unix, they only debeloped the UI. Anyhow this is not the right forum to educate you in systems development.

 

[Simples]

Sorry but you're miss informed. A system has many programs and procedures. No one is talking about an OS, you know that's an acronym for "operating system", such as windows, linux, and whatever fruit computers use, which really their version of unix, they only debeloped the UI. Anyhow this is not the right forum to educate you in systems development.

Thanks for not educating me. Be sure to update Wikipedia about your findings though.

 

[viruscore1]

True but we don't learn by learning how to create systems first doing abstract things like architecture design. It's more logical to learn how to program first. You don't go straight into a career as a system architect, without having earned your spurs writing the bits and pieces .
And with modern Agile development we generally write programs that provide immediate functionality and then incrementally extend them, rather than doing all the system development up front. This isn't the 1970's anymore.
For a beginner it's a pretty reasonable path to learn how to get some data, run a simple indicator over it, and produce some trades which they can then trade manually. That IS a system. It might not have been formally specified up front or be pretty, or have nice abstraction, but it's going to teach the beginner a lot of what they will need to do a much better job with the next iteration, or the bigger project which does more complicated things.
Learning some formal system design principles can come later, it's better to learn how to write decent code first, and even before that the OP is going to have to learn to write cruddy code.
GAT

I come across so many wannabes. I had some java programmers working for me. They programmed a small UI piece and were ready to implement. They had no idea they competed a small part of the data entry phase of the system. No clue of system integration, how the data entered was verified or where it goes etc. The list goes on. Like i said anyone can cobble a program but to develop a system is alittle bit more is involved. Formal or not formal, it's all addressed but you won't understand. The analogy is like playing a game of baseball. Hitting the ball is not the whole game. However formal the game of baseball can be, a simplified version is explained huddled around home plate (similar to agile scrum hahaha), then the kids run off to play. However, the game is played. Are you smart enough to read between the lines, or you're fooling me.
What i'm getting at. All the basic rules of baseball will be address while playing, regardless of formality. One kid is pitcher, the other is catcher, another is 1st base, 2nd base, need a batter, hitting out of the school yard is a homer etc. There's no shortcut. You still need to address the points in systems development or as granular as programming. Over simplified, You still need to know what you are programming, platform, vision, etc...

 

[userque]

"Is this real life?"

 

[viruscore1]

Thanks for not educating me. Be sure to update Wikipedia about your findings though.

These are not my findings, just basic knowledge that you should know before miss informing others.

 

[Turveyd]

Coding is fun, well it was on my Dragon 32 33 years ago, be fine, but total newbie with a steep learning curve ahead of him, both coding and trading method wise, be fun.

I wouldnt even consider a trading system, well unless I'm being paid to develop 1 and get paid regardless of results.

I actually dont think a computer program can ever trade all markets, wayyyyy to complex, computers can't think, only for hft or monitoring to alert trader to look at something fir me, both of which I did try but abandoned years ago.

 

[d08]

I actually dont think a computer program can ever trade all markets, wayyyyy to complex, computers can't think, only for hft or monitoring to alert trader to look at something fir me, both of which I did try but abandoned years ago.

Why does it have to trade all markets? There is no one-size-fits-all system for all instruments and all time-frames.

 

[Deuteronomy_24_7]

miss informed

Does she have a sister?

 

[Turveyd]

Why does it have to trade all markets? There is no one-size-fits-all system for all instruments and all time-frames.

Sorry not refering to that kind of all markets, even 1 market say DAX with differing market conditions.

You can't teach software experience, or a newbie sadly it has to be earned via blood sweat and few nervous breakdowns.