|
Another idea might be to pick a not-too-hard project (for example a notepad, then move on to a calculator, or to solitaire), and write it from scratch. A successful project would give experience in design, graphic layout, etc. The advantage of learning from such a project is that there are endless examples of working programs that may be used for guidance.
There is little advantage today to starting from the batch-processing (or console I/O) programming that we started with 40+ years ago.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
He knows nothing about Visual Studio. That alone makes starting even the simplest project a noteworthy task.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
This resonates because it's what I've done in most articles. I'd find it hard to "come up with examples out of thin air" that weren't hackneyed or for newbies. If I'm going to discuss something interesting, it has to come from real code that has been edited to distill its essence.
|
|
|
|
|
But nothing is more relevant than a foo and a bar . Oops - excuse me - I meant fubar .
|
|
|
|
|
Helping Microsoft with Windows 11 can earn you some unique achievements and badges. If you're really good, do you get a sucker?
Although I think the sucker is somewhere else in this equation.
|
|
|
|
|
Kent Sharkey wrote: Although I think the sucker is somewhere else in this equation.
As in:
var aSuckerIsBorn = 1minute; ?
|
|
|
|
|
Kent Sharkey wrote: some unique achievements and badges. The best badge ist the badger
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Not the badgest?
TTFN - Kent
|
|
|
|
|
Badgest? we don't need no stinkin Badgest!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
It's mind-blowing that people would devote time to finding bugs in return for "achievements" and "badges". I hoot in derision in their general direction.
|
|
|
|
|
I suspect it might be more for people that stumble across bugs, then bother to report them.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Win11 - the ultimate troll! "Works as designed! No moolah for you!"
|
|
|
|
|
Kent Sharkey wrote: Helping Microsoft with Windows 11 can earn you some unique achievements and badges. If you get one do you have an iconic status as they like icons (especially well rounded ones)
|
|
|
|
|
Visual Studio Code program manager Chris Dias has defended an intrusive new "Workspace Trust" dialog, saying it is to "raise awareness that there are many attack opportunities when you download code from the internet." Are you really, really, really sure you want to edit that code you just opened?
|
|
|
|
|
I think the stark reality is that *somebody* needs to warn people about code they download from the internet.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
The average engineer spends 6 hours per week — roughly one day — dealing with technical debt, according to the State of Technical Debt 2021 report from Stepsize, a developer of software development tools. You're saying I should take that day off?
|
|
|
|
|
Better 1 in technical debt than 3 in useless meetings.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
That does not exclude each other - it is easy to have both of them.
But: how is the fifth day wasted?
Oh sanctissimi Wilhelmus, Theodorus, et Fredericus!
|
|
|
|
|
🤔
💡
🍻🍷🥃
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
|
Quote: Technical debt causes bugs and outages, and slows down the pace of development, 60% of engineers said in Stepsize’s report. This results in productivity loss because the engineers are spending more time dealing with issues related to technical debt and not on issues related to development.
Ironically, constantly upgrading to the latest version or worse, replacing the long-in-the-fang technology with the newfangled tech has the same effect or more so.
|
|
|
|
|
It's actually way less than I expected
|
|
|
|
|
And how much more wasted on following the "cool kids" to the newest hype? Is const correctness still a war-winning thing?
|
|
|
|
|
"Technical debt" is impossible to avoid without a team so large that maintaining a team of sufficient size crushes a project, and then everybody ends up out of work, and the project dies.
0) Write some code with the latest tools.
1) 1 to 2 years later, release the product.
2) You have technical debt, because you can't just willy-nilly keep introdicing new versions of base framework code/libraries without fully regression testing everything you've done up to that point.
Even modular re-usable code can't help you.
Your only possible successful strategy is to make the executable nothing more than a launcher with ALL of the code inside discrete DLLs. That way, you can upgrade the executable, and follow up with upgrading the various DLLs when you have the opportunity. The problem here is that your STILL have technical debt.
It can't be avoided.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I worked on an ever-evolving product that ran 24/7. I finally arranged to have a tiny stub/launcher that never changed and everything else in multiple DLLs that were dynamically loaded as needed and some of them could even be switched out while the program was running. With care, I could add new features, change existing ones and fix bugs by just sending the customer a floppy disk (or sometimes two) with the upgrades to be loaded into a special directory along with new release notes. All the customers could request new features or make suggestions and, if it was an improvement then all the customers would get it. They all loved it because it never stopped. One customer sent me a screen shot from the status/splash screen the showed the program had been running continuously for nearly four years without stoppage - of course, this was running on a closed network (no internet) under Windows 4 when there weren't breaking O/S updates every five minutes!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|