|
Perfect except
Quote: 301 mod 7 = 1
|
|
|
|
|
Copy-paste strikes again...
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
|
|
|
|
|
The result is the smallest multiple of 7 which satisfies the rule : This result minus one is also a multiple of 2,3,4,5 and 6. So a=(2*3*5*k)+1=n*7, with n and k integers >= 1, and k a product of 2, 3, and/or 5 only.
In increasing possible values of k:
k=2 : a=61, which is prime.
k=2x2 : a=121 = 11x11.
k=5 : a=151 which is prime.
k=2x3 : a=181 which is prime.
k=2x5 : a=301 = 7x43, n=43, and we have a winner.
|
|
|
|
|
... in a new methodology: CommitStrip OTD[^]
Now we all know that's going to happen, don't we?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Now we all know that's going to happen, don't we? They're going to to screw it up!
And then the next one too... And when they finally get the hang of it there will be a new framework, library, methodology, language or other tool that they'll screw up.
All projects will be screwed up to infinity!
|
|
|
|
|
I have exactly this situation - a local running club want me to put together a race timing/admin system - really simple job that could be done in WPF over entity framework in a hot afternoon.
I'm thinking UWP over F# / event sourcing. It will probably never get completed
|
|
|
|
|
They'll screw up three projects with it, then move on to "the next big thing", and screw up three projects with it.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that.
... Then move on to "the next big thing", and screw up three projects with that
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I wonder why CREATIVE programming wasn't enough? Why they came up with all those variants at the first place?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The only 'keeper' methodology seems to obfuscated programming.
Used, most commonly, in local programming sections.
Possibly because it's incorporated into so many applications across so many languages and a great span of time.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Yep, today's Legacy code is like 2 years ago.
|
|
|
|
|
|
"Cut around Germany, or not?" (10)
Good luck.
Andy B
|
|
|
|
|
Indecision
Incision (cut) around Germany (DE)
|
|
|
|
|
Well done, you have the poisoned chalice honour of coming up with tomorrows CCC!
Andy B
|
|
|
|
|
Nice clue!
Slogans aren't solutions.
|
|
|
|
|
|
I suppose I technically qualify as one and I dunno. Sitting around staring at job boards that all want Senior .NET Developers probably wondering where all the employers looking for Junior or even Mid-level devs are. As someone currently looking that's been my experience anyways
modified 14-Feb-17 0:41am.
|
|
|
|
|
I am surprised at that. It shows that things are gummed up where you are. Your articles are a good indication of your ability and I can't imagine why you are out of work. I would not despair.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
I agreed sometime the job description is too ambitious for a junior position. And that turn them away. For my case, I might not looking at the right place.
Bryian Tan
|
|
|
|
|
I remember back in 2005 seeing an ad for an experienced dot net developer with 5, that's right, 5 years experience.
|
|
|
|
|
I remember an email this week from an agent looking for a senior .NET developer with 3+ years experience.
To be fair I've also worked with senior developers with less ability than juniors/graduates. Titles mean far less than client requirements and day rate/salary. Also, years don't necessarily indicate experience.
|
|
|
|
|
The gist of my comment was that dot net officially was launched in 2001, but the ad (placed in 2005) was looking for 5 years experience. Totally unrealistic.
|
|
|
|
|
Sorry, totally misread your comment. Yeah true.
|
|
|
|
|
WinnipegCodeMonkey wrote: The gist of my comment was that dot net officially was launched in 2001, but the ad (placed in 2005) was looking for 5 years experience. Totally unrealistic.
I was to say something similar but even worse, in 2005 as well, they were looking for someone with 10 years experience in .NET, I laughed so much, governments, they know nothing
|
|
|
|
|
It would have been possible for someone in 2005 to have had five years experience with .NET.
You are forgetting that Microsoft had a beta program for .NET.
I was a part of it, and have a vivid memory of being in Redmond, for a week in 1999 for a working session with Microsoft.
One of the reasons it is vivid, is because of one session beginning at 4PM where the Microsoft team comes in in flannel shirts and blue jeans carrying a large tub filled with ice & beer.
Then we got an impromptu session by the guy who wrote ASP.NET. It was pretty amazing watching him break the cardinal rule of presentations by slinging code in Notepad & not ever having anything break.
|
|
|
|