I went to university for this, really?
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
Two short weeks ago:
- Update NuGet packages;
- Deploy new version of application using Squirrel[^];
- Application updates, and all is good;
Next day:
- Add a new feature to the application;
- Deploy new version;
- Notice that application doesn't update to the new version - notice a
MissingMethodExceptionin the event log; - Notice that application now won't start after closing - the update created an empty folder for the new version before crashing, which prevents the launcher from starting the application;
- Discover that Squirrel is not compatible with latest
Mono.CecilandSharpCompressNuGet packages, but hasn't declared that in the requirements; - Discover that this bug was first reported back in February[^], and still hasn't been fixed; :mad:
- Roll-back
Mono.CecilandSharpCompresspackages, recompile, re-deploy; - Spend next couple of days explaining to customers that they need to manually install the latest version of the application, since the auto-update is borked;
Add to notes: When updating NuGet packages, build and release at least two new versions of the application to the test site before rolling out to the live sites, to ensure that the updated updater actually updates. :doh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
And beer. Lots of beer. Don`t forget the beer, it`s important.
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
Nah - I went to college in Brum. The beer was (and probably still is) dreadful.
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
I went to university for Fortran, Pascal and Turbo C... none of which I use today. Should have focused on beer and the ladies. :sigh:
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
"Error CS0122 'ValueBinder' is inaccessible due to its protection level" Aaaaaaargh!!!
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
NuGet: Nothing U Get Ever Works. Including the acronym. ;)
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
are you not using any automation? like check in to source control and schedule a nightly build ? email the build report to devs ? what is this new thing ? back in the old days we used to do it like that ...
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
AFAIK there's no point to going to university for thist stuff. I remember my informatics lections being so theoretical, they're pretty useless for getting stuff done and academia didn't prepare me for stuff going wrong in the field (such as a network connection being less reliable than a SATA cable). I've read on some blog linked in the Codeproject news about how programming should be taught in a master/apprentice-manner rather than in an academic manner and from my own experience in the field, I very much agree. I don't think that academia is entirely useless. When it comes to stuff such as designing embedded OS' or compilers yourself, deep theoretical knowledge surely is helpful. But when you're the guy who uses all those background services to get the actual task done, university is a waste of time. Well, not entirely. I got hired for having a degree sinmply because it indicated to my now-employer that I'm a bright head capable of learning. Apart of that, that's about it.
-
NuGet: Nothing U Get Ever Works. Including the acronym. ;)
Latest Article - A Concise Overview of Threads Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Are you telling us that you went to the university to learn? I was under the impression that university is to collect positive experiences for the later, when you will have no time (family, work and other things)...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
Kornfeld Eliyahu Peter wrote:
Are you telling us that you went to the university to learn?
I learned how to party.
Kornfeld Eliyahu Peter wrote:
when you will have no time (family, work and other things)...
So true... I miss those times, but I am glad I had them
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
AFAIK there's no point to going to university for thist stuff. I remember my informatics lections being so theoretical, they're pretty useless for getting stuff done and academia didn't prepare me for stuff going wrong in the field (such as a network connection being less reliable than a SATA cable). I've read on some blog linked in the Codeproject news about how programming should be taught in a master/apprentice-manner rather than in an academic manner and from my own experience in the field, I very much agree. I don't think that academia is entirely useless. When it comes to stuff such as designing embedded OS' or compilers yourself, deep theoretical knowledge surely is helpful. But when you're the guy who uses all those background services to get the actual task done, university is a waste of time. Well, not entirely. I got hired for having a degree sinmply because it indicated to my now-employer that I'm a bright head capable of learning. Apart of that, that's about it.
Kirill Illenseer wrote:
Well, not entirely. I got hired for having a degree sinmply because it indicated to my now-employer that I'm a bright head capable of learning. Apart of that, that's about it.
This is true of many degree "requirements". They are used by the recruiters to winnow out the chaff.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
In uni, I learned: - how to build a complex 3D engine in an esoteric programming language nobody uses (= no internet resources) - how to assess the complexity of algorithms, theoretically, and measure their actual complexity in the field - an esoteric variant of opcodes, not x86 based, to drive a CPU in an emulated environment - how to build data structures, with a comparable quality to the C++ STL ..and that's just the stuff I remember on the top of my head. In general, I felt the quality of my Uni was good. Totally worth the 1.5K euros a year. Well, maybe a bit less; if you resell your books, it's more like 0.7K a year. :)
-
I went to university for Fortran, Pascal and Turbo C... none of which I use today. Should have focused on beer and the ladies. :sigh:
I went to college (I'm American instead of British) to learn how to think rather than learning tools: guidelines for how to solve a problem when you have no clue how to start. I think my school did a good job: I can generally find a solution to ANY problem my work (or life) throws at me. I frequently don't find the optimum solution first, but I discover a solution. I compare it to being a carpenter. The apprenticeship is not to learn how specific tools work; it is to learn what to do WITH the tools. A good college education is the same.
-
* Nuget update packages * Clean and build * Google error messages * Read stack overflow article about incompatible nuget packages * Repeat And the days just fly by....
-
AFAIK there's no point to going to university for thist stuff. I remember my informatics lections being so theoretical, they're pretty useless for getting stuff done and academia didn't prepare me for stuff going wrong in the field (such as a network connection being less reliable than a SATA cable). I've read on some blog linked in the Codeproject news about how programming should be taught in a master/apprentice-manner rather than in an academic manner and from my own experience in the field, I very much agree. I don't think that academia is entirely useless. When it comes to stuff such as designing embedded OS' or compilers yourself, deep theoretical knowledge surely is helpful. But when you're the guy who uses all those background services to get the actual task done, university is a waste of time. Well, not entirely. I got hired for having a degree sinmply because it indicated to my now-employer that I'm a bright head capable of learning. Apart of that, that's about it.
