The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
I have what I think is a killer idea, but lack the progamming skill to test it
I had a moment of insight at work today, and the idea has been stuck in my head ever since.
It could easily be tested with access to programming software, and the ability to use it. Unfortunately I lack both. I'm downloading the Visual Basic trial to see if I can get anywhere myself, but I'm not optimistic. I don't even know if Visual Basic is capable of what I'm thinking.
I think this idea could significantly improve certain processes where I work. I would hate to give up on it because I'm intimidated.
Well, if you gave a bit more detail about what it is that you're trying to do, people on the board could give suggestions about what programming language would be the easiest to use to implement the idea.
Visual Basic.NET is an extensive improvement over the old Visual Basic 6 and earlier, so may not be a bad place to start, and it does make it extremely simple to get a windows form interface up quickly -- though obviously still with programming required for the various events/buttons on your form. But without knowing more about what you're trying to accomplish it's really impossible to say where you should start.
Let me see if I can explain it without giving too much away.
Where I work currently what is made on the assembly line is completely under control of the person at the head of the line. It all gets made eventually, but usually not very efficiently.
I want to demonstrate that a computer program could be instructed to consider each order and make decisions on what should go down the line next based on complexity of the order, and maximization of efficiency/speed of the assembly line.
Aside from the fact that there would be an obvious efficiency/speed increase, such a program would take out all of the stress on the assembly line workers. Any problem on the line means a problem for the entire operation, everyone would be happier.
I would almost guarantee that there's already some software out there to do exactly that (although it may or may not be cheaper to program it yourself).
.NET (either VB or C#, not much of a difference) should be able to accomplish it, probably using a database as well.
I know for a fact there is software to do what I'm talking about.
But to sell this idea to the people I work for, I need to create a program that simulates our operation exactly. They won't take me seriously otherwise. Probably would just write me off as another college student with too much useless knowledge.
I know for a fact there is software to do what I'm talking about.
But to sell this idea to the people I work for, I need to create a program that simulates our operation exactly. They won't take me seriously otherwise. Probably would just write me off as another college student with too much useless knowledge.
You'd be better off trying to demo that software or simulation than writing something from scratch if you have no knowledge or connections.
solsovly on
0
Deebaseron my way to work in a suit and a tieAhhhh...come on fucking guyRegistered Userregular
I know for a fact there is software to do what I'm talking about.
But to sell this idea to the people I work for, I need to create a program that simulates our operation exactly. They won't take me seriously otherwise. Probably would just write me off as another college student with too much useless knowledge.
Are you actually trying to get your company to use software that you've written? Or are you trying to convince them to purchase an existing piece of software, or pay for something specific to be developed?
Putting together real, functioning software typically is a lot more complex than you might originally think. If the profitability of your employer is at stake, I would be surprised(/concerned) if they would use something not professionally developed.
But it might be a fun/educational experience to write something yourself regardless. I would stay the hell away from VB though. Java or Python might be better languages to begin with. They each have a wealth of intro-to-programming style documentation and support available all over the internet, and some nice, free development tools.
If it's just a simple "is it this, do this, is it that do that, is it this third thing, do that third thing?" then any language will do and it should be relatively simple to get it done. You could probably do it in a day, even learning the language from scratch because everything you'd need to know would probably come from the first few pages of a book or tutorial.
bowen on
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
On top of an excel spreadsheet, you might also want to make a flow chart of the decision making logic. This will help you avoid unexpected situations and can help reveal a lot of unexpected complexity.
The base idea of your program is simple and could probably be done with just about anything. With software dev, though, the devil's in the details. There are almost always a ton of things that come up that you don't expect and I suspect decision making logic for something like this gets pretty complex.
That's not to dissuade you from giving it a go. At worst you get some experience with something new and possibly pick up a new skill set and find something new you enjoy doing.
Your idea could have side effects, like several workers being fired, have you considered that little point?
Fantasma on
Hear my warnings, unbelievers. We have raised altars in this land so that we may sacrifice you to our gods. There is no hope in opposing the inevitable. Put down your arms, unbelievers, and bow before the forces of Chaos!
Your idea could have side effects, like several workers being fired, have you considered that little point?
Arguing against progress (or even mentioning it as a consideration) because it might cut out obsolete jobs is terrible advice. When my company switched to VOIP phones, should they have kept their old telephony staff employed?
Your idea could have side effects, like several workers being fired, have you considered that little point?
Arguing against progress (or even mentioning it as a consideration) because it might cut out obsolete jobs is terrible advice. When my company switched to VOIP phones, should they have kept their old telephony staff employed?
Perhaps one of the employees is his friend, or maybe one of them could be you, what do I know?
Fantasma on
Hear my warnings, unbelievers. We have raised altars in this land so that we may sacrifice you to our gods. There is no hope in opposing the inevitable. Put down your arms, unbelievers, and bow before the forces of Chaos!
Unfortunately I lack both. I'm downloading the Visual Basic trial to see if I can get anywhere myself, but I'm not optimistic. I don't even know if Visual Basic is capable of what I'm thinking.
Visual Basic can do *anything*. Don't listen to code snobs who think that if it's not done properly it's not worth doing. Visual Basic is a complete programming language designed for people like you who do not have programming expertise, but want to get something done, quick and dirty.
Posts
Visual Basic.NET is an extensive improvement over the old Visual Basic 6 and earlier, so may not be a bad place to start, and it does make it extremely simple to get a windows form interface up quickly -- though obviously still with programming required for the various events/buttons on your form. But without knowing more about what you're trying to accomplish it's really impossible to say where you should start.
Where I work currently what is made on the assembly line is completely under control of the person at the head of the line. It all gets made eventually, but usually not very efficiently.
I want to demonstrate that a computer program could be instructed to consider each order and make decisions on what should go down the line next based on complexity of the order, and maximization of efficiency/speed of the assembly line.
Aside from the fact that there would be an obvious efficiency/speed increase, such a program would take out all of the stress on the assembly line workers. Any problem on the line means a problem for the entire operation, everyone would be happier.
.NET (either VB or C#, not much of a difference) should be able to accomplish it, probably using a database as well.
But to sell this idea to the people I work for, I need to create a program that simulates our operation exactly. They won't take me seriously otherwise. Probably would just write me off as another college student with too much useless knowledge.
You'd be better off trying to demo that software or simulation than writing something from scratch if you have no knowledge or connections.
Can you simulate your operations with excel?
Putting together real, functioning software typically is a lot more complex than you might originally think. If the profitability of your employer is at stake, I would be surprised(/concerned) if they would use something not professionally developed.
But it might be a fun/educational experience to write something yourself regardless. I would stay the hell away from VB though. Java or Python might be better languages to begin with. They each have a wealth of intro-to-programming style documentation and support available all over the internet, and some nice, free development tools.
http://en.wikipedia.org/wiki/Programmable_logic_controller
It's also awesomely easy to figure out how to program, you just need software that's capable. It is entirely if/then structures (basically).
The base idea of your program is simple and could probably be done with just about anything. With software dev, though, the devil's in the details. There are almost always a ton of things that come up that you don't expect and I suspect decision making logic for something like this gets pretty complex.
That's not to dissuade you from giving it a go. At worst you get some experience with something new and possibly pick up a new skill set and find something new you enjoy doing.
Arguing against progress (or even mentioning it as a consideration) because it might cut out obsolete jobs is terrible advice. When my company switched to VOIP phones, should they have kept their old telephony staff employed?
Perhaps one of the employees is his friend, or maybe one of them could be you, what do I know?
Visual Basic can do *anything*. Don't listen to code snobs who think that if it's not done properly it's not worth doing. Visual Basic is a complete programming language designed for people like you who do not have programming expertise, but want to get something done, quick and dirty.
Go for it.