|
I was going to make a joke about why this was in The Liverpool Echo, but chickened out!
|
|
|
|
|
Go after the bigger group - the problem isn't with those from Liverpool, it's with the Instagram users. Yes, I'm generalizing, and I have no problem making a blanket statement out of it.
Friends, family, acquaintances, all seem to be confused about me. They come to me for technical advice, yet seem to think I'm some sort of luddite for not being all over the so-called social media sites...the "why" falls on deaf ears.
|
|
|
|
|
Pounds as in money. Ahhh. Otherwise, send me the link.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
It's Instagram....a whole new level of stupid.
|
|
|
|
|
Never used Instagram; don't even know what it does ... but, sounds like "telegram" ... so it must be important / legitimate.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
|
|
|
|
|
Just had my first scam email today. Not I suspect from master criminals since they quoted the password they say I use for my viewing of "interesting" sites. Never heard of it.
They will post the video taken from my webcam of me enjoying the sites to all my contacts. If only I had a webcam ...
Still, it's got to be worth $1045, just to be safe. After all, the nice man assured me he'd delete everything if I pay up!
|
|
|
|
|
There was a company back in the VHS / DVD days who specialised in "speculative invoicing": sending an invoice for £700 to random people claiming they were in possession of pirated porn, and threatening legal action for copyright infringement if the invoice wasn't paid in 14 days ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I simply can't resist. James' talk is just too much fun. Don't suppose your contact's name was Solomon...
This is what happens when you reply to spam email | James Veitch - YouTube
6.41 / 9.48
The business is on. I am trying to raise the balance for the Gummy Bear so he can submit all the needed Fizzy Cola Bottle Jelly Beans to the Creme Egg for the Peanut M&Ms process to start. Send £1,500.00 via a Giant Gummy Lizard.
|
|
|
|
|
I just had a line of my code bounced for 'incorrect' syntax. It was a simple if/then - e.g.
if {condition} then {do something}
Which I had coded, as above, on a single line. The Code Reviewer said it should be on 3 lines. Both syntaxes are allowed in the language I am coding in, so I checked the Coding Standards document - and there's no mention of a preferred if/then syntax. Also, looking at the code-base, both syntaxes are used throughout.
My view is: if they can't be bothered to document something as a standard, I, as a developer, am free to choose the syntax I prefer. I stood my ground, (and won out), not because I didn't want to spend 2 minutes changing the code, but because I value properly documented standards.
What do you think guys?
|
|
|
|
|
I'm happy with
if (parameter == null) return; and so on, but anything more complex than "return" or "throw" I put in brackets over three lines:
if (parameter == null)
{
...
} The only time I will omit the brackets is for a very short instruction on the same line as it's test.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I do brackets because, sooner or later, I'll be adding something else in there.
|
|
|
|
|
I agree. I always do brackets even for one-liners because, in the words of Forrest Gump, "That's one less thing to worry about".
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
|
braces and comments reduce performance
Real programmers use butterflies
|
|
|
|
|
Draws breath
Nah, bugger it. Save the religion stuff for another couple of days. It's only Thursday.
Closes mouth and turns away.
|
|
|
|
|
Only of the build.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Real programmers use butterflies
|
|
|
|
|
Very true for interpreted languages!
...and who wants to waste time writing the parser for a comment when devs do not use comments anyway.
|
|
|
|
|
Confused, because I can always add the brackets if I add more lines.
|
|
|
|
|
Firstly, I'm coding in a very old language. Here's the exact line of code. Hopefully you can translate to a 'proper' language.
IF ERROR.MSG = "" THEN ERROR.MSG = "Error ":ERROR.CODE
It was a catch-all I inserted, (without being asked), to ensure that an error message would always be returned, even when it was an unknown error code. Yes, it's a single "=" for both conditions and assignments. And I was made to change it to upper-case. FFS!
What they wanted, was:
IF ERROR.MSG = "" THEN
ERROR.MSG = "Error ":ERROR.CODE
END
But, the point that I was trying to make was: not that my way is right, but: if they want it doing a particular way, it should be documented - particular as the code-base contains a, pretty much, 50:50 split of both syntaxes.
|
|
|
|
|
|
Richard MacCutchan wrote: Cobol?
It's slightly easier than that! It's a (fairly significant) variation on Basic, which comes as part of the Universe DBMS. It's derived from Pick DataBasic (another one you won't have heard of!) and is actually very easy to develop with - albeit limited in scope. i.e. It's for dumb terminal applications. I like it though.
|
|
|
|
|
5teveH wrote: Pick DataBasic (another one you won't have heard of!) Don't be too sure. I have been writing code on quite a few different systems (a few whose name I cannot remember) since 1966 (yes, that is really nineteen-sixty-six).
|
|
|
|
|
You do it all wrong! The correct syntax is:
if (parameter == null)
{
return;
}
else
{
}
Reason: always add an else to an if, even if it's empty, because otherwise a future nested if could accidentally add an else at the wrong nesting level!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
Take thy code to The Weird and The Wonderful[^] where it belongs!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|