|
DrBones69 wrote: why you have chosen a specific set of tools used for creating the majority of the projects created and what led you to the path you're on
While I answered this obliquely in a reply to a post in this thread, I haven't answered directly.
My choice of languages and technologies is driven primarily by market share. Companies typically hire for specific technologies so to maintain a consistent paycheck I learn whatever is in demand. In the past 30 years I've seen numerous technologies rise to stardom and fade into obscurity, so I focus on what I project will have market share in the foreseeable future -- with the understanding that I'll learn new things as the current ones fade.
The simple fact is that as much as I enjoy programming, my focus is having a paycheck. My experience is that having a paycheck beats the heck out of NOT having a paycheck. 
But market share is not the only consideration -- what *I* want to do is important. We spend too much time at work to do something we absolutely hate for long (although I've done that when the economy was less than stellar).
Most surveys I've read recently put C# at 6th or 7th in popularity. It seems to hold consistently in that place year after year, and C# has good market share in my area (lot of Microsoft-based shops). I like C# and database, so that's my choice.
My advice to everyone is to watch the job boards, even when you have no interest in jumping ship. Stay abreast of where the paying jobs are, and take the trade rag articles on upcoming languages with a grain of salt. Until someone is willing to pay for a skill set, it is of limited value.
|
|
|
|
|
Thanks Bryan!
It seems that C# has the majority vote so far. But I still find myself feeling the strong pull from C++ and Cobol calling to me. I'm always willing to learn any language, technology, helper tools etc... While in the process of learning, I sometimes yell out loud, "SQUIRREL!" lol. (Might have something to do with ADD or ADHD, even though I've never been diagnosed). Thanks again for your wise input. Sounds like C# is waiting for me, so wish me luck but it shouldn't be a big challenge.
-Randy
|
|
|
|
|
Glad to be of service! You don't need luck, just perseverance. 
Your response made me think of something else, the learning process. As IT people we will continue to learn the remainder of our careers, or we will stagnate.
Learn COBOL and C++ if they interest you. The value of learning COBOL for a any programmer is that it teaches us to think differently. So does VB and C and any other procedural language. Dabble in F# or Lisp or any functional language for the same reason. Learn Oracle, SQL Server, and/or My SQL -- yet another paradigm. [NoSQL and MongoDB are on my list of things to learn.]
[IMO we should learn C early in our training, it provides a background for learning many other languages including C++, C#, and Java. I haven't used C professionally in more than 25 years, but the lessons learned influence everything I do, and I still have my dog-eared copy of K&R.]
The more ways we learn to think, the faster we learn new things, the easier it is to keep up with technology changes.
In my first job I was tasked to teach SQL to a woman who had been writing COBOL for 30+ years. She was amazing with COBOL -- if it could be done with COBOL, she could do it. If it couldn't be done with COBOL, I'd give even odds that she'd do it anyway. But she couldn't grasp SQL. IMO she spent too many years thinking only one way, and couldn't make the paradigm shift. [COBOL and her age didn't factor in, IMO, it was the difficulty of thinking in a totally different way.]
That was a warning to me to keep current and keep flexible.
I mentioned I'm currently doing C#/MVC. To do this I'm using C#, JavaScript, HTML, XML, Razor, SQL Server (including DB design and T SQL), Oracle (we are migrating databases), Microsoft's version of MVC including Entity Framework, and probably more that I can't think of at this moment. Flexibility is a requirement for this job. 
|
|
|
|
|
Thanks again, Bryan.
I just read my reply to your post again and I think I should clarify when I said, "It looks like the majority is with C#, but I still feel C++ and COBOL calling for me". I meant that these are the languages (C, C++ and COBOL) that I have been coding in all of my life for business and my own "hobby projects" for years.
The point of my first post was to get opinions, feelings, why's and other aspects of other programmers, white hat hackers, developers and computer code insomniacs why they have chose the road their on and if their road forks in many directions  .
You have a very great outlook on the way people seem to fall into a "wagon trail" and they can't seem to get out of it. Programmers do tend to stick with what they know and what has been working for them. But, with a lot of languages, their usefulness will end someday and where does that leave the stubborn programmer?
Anyway, I am always delving into something new to learn, but I always seem to go back to COBOL or C++. These languages have never failed me with their stability, business reliability and my knowledge of their power. I HAVE THIS NEED TO KNOW IT ALL, but I know that as long as I live that this is impossible. (Not impossible if things never change lol)
-Randy
|
|
|
|
|
Randy,
Yup, I completely misunderstood your background. Communication via text has its drawbacks ...
People are creatures of habit -- most of us tend to stick with what we know. It isn't surprising that many try to stay with what they already know. When I got out of college into my first job, I had a driving need to know everything (you understand this). That drive served me well in setting the stage for a good career. In recent years I realize the drive has diminished ... but recognizing I need to stay current keeps me focused on learning new things.
One thing that is making me wonder -- I can't recall anyone using COBOL for personal projects. Pretty much any other language, but not COBOL. What kind of personal projects do you do with COBOL and what compilers?
|
|
|
|
|
Now a day, I use these three exclusively: C#, JavaScript and SQL. With these two I can build just about any application web or desktop. I know, lots of developers don't like JS, but I like it, especially ES6.
I try not to use third party tool/libraries especially those all-in-one framework tools that are bloated, like DevExpress, Telerik, extjs, etc. I do use third party (open source) libraries, but only those that are light weight and specific. I event shy using jquery.
|
|
|
|
|
I do like your setup, because that's usually what I tend to lean on with the exception of C#. When I'm not using COBOL I turn to C++, SQL with a little bit of VB. Thanks for the input, Leng.
-Randy
|
|
|
|
|
It depends. I do very little visual studio work, and very little web programming.
I support COBOL and various client server systems, many still written in Delphi!
I chimed in because I am the outsider.
Honestly, as long as you are doing solid with your customers, you are fine.
I work with people who are 99% Visual Studio and all C# (and I have done a bit
of C# to help out on projects, and sit through the code reviews).
Why do we stick with Delphi? We have literally a million lines of code, and huge libraries.
We can add features quickly and easily. We are like short order cooks who produce small automation and integration pieces.
But we are doing more projects on the web with C#, and still support PHP files...
Enjoy!
|
|
|
|
|
COBOL is a great language, but there are so many programmers that cringe when I say COBOL lol. I'm going to learn and write my next project in C#. Thanks for your input...
Randy
|
|
|
|
|
Well, lately, I find that I prefer C# using MS Visual Studio. This allows for rapid GUI design and coding, plus C# offers an excellent debugging environment due to how it is designed. The only other language I really consider using is C in the event that I need something that runs as efficiently as possible. I could go right down to assembly or machine code, but that kills portability so I have not done so in decades. Sure I have learned and continue to learn others but I really do not seem to end up wanting to migrate to them.
|
|
|
|
|
Front end:
JavaScript (Angular, React)
Middle: C#, and Node...try it out with EdgeJs and you can have Node consume C#.
Backend: Sql Server, but starting to move towards Cassandra and Redis.
|
|
|
|
|
C#, WPF, and Syncfusion controls for professional, modern looking application. 
You can also use MahApps.Metro. I have used them both.
They are needed because Windows' standard WPF appearance is really ugly, and it's too much of a hassle to skin them yourself.
|
|
|
|
|
I would say there are 2 competing trains for thought for this question.
- Use the best tool for the job.
- Use what you know the best.
As a project, you can assess that maybe C# with .net would be the best fit. However, when you look at the skill set of your team and find they lack the knowledge. You are left to either train them up, which may take some time to make it error and bug free, or hire in the staff.
Conversely, if your team says, well we can make that in Java, in X time, for Y budget, and it wont look as different. They have the knowledge to make it far less error prone and bug free.
mixing the two: deciding on what language or tools to use should be weighed against Skill, Knowledge, Suitability
C# reduces knowledge requirement to get program written (such as memory management)
C or C++ may be closer to the OS, hench can write higher performance code, at the cost or requiring a higher knowledge of the language.
|
|
|
|
|
I'm a former aerospace engineer that of course had a background of BASIC in high school & FORTRAN in college. In the early '90s I took a course through my place of work in C, and the utter elegance of that beautiful language completely captivated me. I went on to learn C++, which I also found elegant, even the tricky parts. I then learned VC++ and became completely smitten by the idea of how easily I could develop a regular Windows app, and decided to switch careers into software development. When .NET came out, while I had a few issues with some of the hokey aspects of C# like the fact that a fundamental object is passed by value whereas any other object is by reference and some peculiarities of callbakcs, I did like the way that abstract classes & virtual functions were done, and of course the memory management - but I what I really liked was the way that it set up the forms & data binding in a very elegant way as opposed to the kludgy way that VC++ did it. I now consider myself a .NET C# developer, albeit "early retired" since there seems to be no market demand for this skill anymore.
|
|
|
|
|
I recently converted my laptop to an SSD (from HDD) and I'm realizing the benefits every day.
Android Emulator
I hadn't given it extra thought but I started a new Android project and started the emulator the other day and it started so fast I wondered how it was possible.
Then I remembered, the entire Emulator OS is really virtual memory (run from disk for the most part).
I just started my emulator running Android Lollipop and the Google API and it goes from zero to fully started in about 5 seconds.  It was probably somewhere around 1-2 minutes with the HDD.
If you're an Android dev and running emulators like this (and you have an HDD), you really need to consider converting to an SSD.
|
|
|
|
|
I have a spare machine with 80G hard drive and loads with Visual Studio 2017.
I want to use SSD to improve the performance as you did.
diligent hands rule....
|
|
|
|
|
I doubt you'll find a single member of this site who will argue against adding an SSD to their system! Having said that, one or two will turn up...
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
David O'Neil wrote: Sudden Sun Death (SSD)
Is that really what I want to add to my system?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Quote: Having said that, one or two will turn up...
See! I jinxed myself! 
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
It all depends on cost vs capacity vs speed of access.
For portables and desktops, I agree that an SSD is the way to go. This is not necessarily the case for a home/office NAS, and is far from being trivially true for a datacentre.
There's still plenty of life in them old horse buggies.
[Full disclosure: my employer, Western Digital, makes both HDDs and SSDs]
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Daniel Pfeffer wrote:
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
Does this mean that you are able to get "all of us" a huge discount on HDD's and SSD's? Maybe even FREE SSD's for everyone that is a member of CODE PROJECT!!!!??
-Randy
|
|
|
|
|
Sorry; it doesn't work that way. I can only purchase a limited number of devices every month, and they may only be used for non-commercial activities. Selling them on is a definite no-no!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
ssd. Bah Humbug! Bring back core memory.
Sin tack
the any key okay
|
|
|
|
|
Modernist! Bring back the Jacquard Loom!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
David O'Neil wrote: doubt you'll find a single member of this site who will argue against adding an SSD
I agree.
David O'Neil wrote: Having said that, one or two will turn up...
You definitely know this site. Or people. Or People of The Internet (PITs)
Here they come.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
