|
That's not the idea - if it's a bug, then it will be fixed.
If it's an exploit, then the points will be removed, and there is a good chance your account may suffer as well.
Earn your rep legitimately - it's not difficult, honest!
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
OriginalGriff wrote: it's not difficult, honest!
Is there a way you can hack the system and jump your points?
OriginalGriff wrote: Earn your rep legitimately
It will not be illegal if we use our skills
|
|
|
|
|
contracting1990 wrote: hack the system
contracting1990 wrote: not be illegal
What part of "logical inconsistency" do you not understand?
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
Hacking is not illegal when its for good purpose...
|
|
|
|
|
Since when did you decide that avoiding doing the actual work but cheating instead was a "good purpose"?
Did you use this approach to your exams?
Do you think that it reflects well on your character as a person?
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
The good purpose I mentioned was in hacking the system for the reason of finding flows so it will be fixed
|
|
|
|
|
contracting1990 wrote: The good purpose I mentioned was in hacking the system for the reason of finding flows so it will be fixed
Um.
contracting1990 wrote: How to make my points jump like that?
Yeah. Right. Sure you did...
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
OriginalGriff wrote: How to make my points jump like that?
Yeah. Right. Sure you did...
Yes this is called brainstorming and that is the first thing you should do
modified 19-Oct-13 3:48am.
|
|
|
|
|
Ha, I'll bet its a good thing when he does it, and a bad thing when others do it
|
|
|
|
|
For research purposes only, of course!
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
On a more serious note, I have noticed some articles that gets a lot of votes and isnt really that outstanding, however the authours seem to quit rather quickly though.
|
|
|
|
|
Sock puppet article voting...
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
Oh, no I wasnt talking about my articles
|
|
|
|
|
The only instant messaging I do involves my middle finger.
English doesn't borrow from other languages.
English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
|
|
|
|
|
A priest, a rabbi and monk walk into a bar. The bartender looks at them and says, "What is this, a joke?"
|
|
|
|
|
Quote: What is this, a joke? Apparently not.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
The blonde sitting on the end stool says, "Well, at least it's not on me this time."
Software Zen: delete this;
|
|
|
|
|
|
A beer for the ballerina!
|
|
|
|
|
First of all, thanks very much to everyone who kicked in with thoughts regarding MVC. I'm currently doing some upgrades / installs for VS 2012 since I've been running 2010 so that I can give MVC 4 a go.
Since I'm reevaluating technologies, here's something I just don't get - but perhaps I'm missing something. A year or two ago I played with LINQ. Essentially, it's a nice little chunk of technology to move your db queries into your code.
My approach has traditionally been to use stored procedures, keeping SQL stuff in the database and procedural code / logic in the application. Why on earth would I want to move my queries into C# code?
As long as the params and columns returned don't change, I can make changes all day long in Sql Server and never touch web apps or services. If my db logic is in the code, I have to recompile and deploy the binaries every time I touch something.
I know it's the shiny new thing to play with but other than resume enhancement, I just don't see what value it brings to the table. What am I missing?
|
|
|
|
|
You're thinking of LINQ as "database only" for one thing. LINQ works on other things, like anything that implements or can be cast to a IEnumerable<T> or IQueryable<t>.
LINQ also lets you build a query, piece by piece, defering execution of the query to when you actually use the would-be-returned data.
|
|
|
|
|
You're absolutely right, that was my context. So yes, it would be great to have a structured way of managing data sources that don't live in a relational database. Advantage: LINQ.
How about working with a database, though - any advantages there? That's the part I'm just not seeing.
|
|
|
|
|
On heavily loaded client/server applications, stored procedures can cause major bottlenecks. I was on the fringe of at least two projects where anything more than simple stored procedures were prohibited for this reason (and they had tests to prove it.)
|
|
|
|
|
While I don't doubt what you're saying, the logic escapes me. Either way, you have to hit the database and fetch the data.
What's special about a stored procedure that would make it more of a performance bottleneck than retrieving the same data from the code? Seems like the db is serving up the same amount of bytes either way.
|
|
|
|
|
Because stored procedures take computing time and aren't always trivial. Stored procedures aren't just a few lines of code to do, say, a select or simple update trigger, they can be entire programs which may have little to do with setting/retrieving data, but in manipulating that data. So, who should manipulate the date, the client or the server? (The answer is, of course, it depends.)
|
|
|
|