|
Dead man dying
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
|
|
"Indisputable that post is full of bright ideas!"(6,6)
Not too hard, but may catch you out.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
|
"Solving the CCC is the hardest i can imagine"(10)
btw my answer: totaly clever
that post is full -> totaly
bright ideas -> clever
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Totally unspellchecked?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Was CP down for a couple o' minutes? Had a Error and couldn't connect to cp around 7:57 ?
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
because we all were here enjoying Chris's party. Servers got lil bit upset...
"When you don't know what you're doing it's best to do it quickly"- SoMad
|
|
|
|
|
Sweet I'd take that serverrrom
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
|
One of the questions asked at the launch today was, "are you going to start naming it after big cats?"
TTFN - Kent
|
|
|
|
|
Yep - Windows 11 will be called "Tiddles"
PooperPig - Coming Soon
|
|
|
|
|
|
Only if it was designed using TiddlyWiki.
|
|
|
|
|
Haha! Good one!
|
|
|
|
|
I watched the demo and apparently you can resize, minimize and close windows with Windows 10.
It's hard not to turn to satire when being exposed to such 'advances'.
On a side note I guess Windows Nein was a no no, yah?
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
GuyThiebaut wrote: On a side note I guess Windows Nein was a no no, yah? Ja.
I will get my coat.
Whether I think I can, or think I can't, I am always bloody right!
|
|
|
|
|
Android is the sleeper when it comes to public awareness. I'm waiting for my new Samsung Note 4 which is a Smartphone having specs better than my laptop of three years ago. It's 2x the hardware, in every category, compared to the iPhone 6 Plus. I can run a Bluetooth keyboard, use the pen-stylus or my finger on the screen and use MS Office compatible apps and Chrome based apps... Syncs better to my PC than my iPhone ever did.
With BlueStack or Andy, I can run the 1 Million+ Android apps on my PC or Mac.
With Android out-selling iOS 2-to-1, this may be the next frontier. My wife, in her day-to-day work, uses her tablet more than her laptop. Just saying. Maybe, in a year or two, it will be Windows vs MacOS vs Android. After all, Android is Linux with a consumer GUI.
Current digital cameras, Internet of Things, and mobile devices are mostly embedding Android.
|
|
|
|
|
If this is the wrong forum, let me know and I'll move it.
Before you start a new project/contract, what questions do you ask?
Here's what I send my potential clients. I pre-filled some of it...
1. Primary Point of Contact
a. Name, Company, Address, Office and Cell Phones, Email
2. Scope of the Project
a. Time & Cost
i. Expected Date of Completion
1. (Date goes here)
ii. Budget
1. (Amount Goes Here)
b. Infrastructure
i. Web Access
1. Does the app need to be able to remotely access the database?
a. Yes / No
ii. Development Platform
1. Microsoft C#.Net 4.0, Windows Presentation Foundation 4.0
iii. Target Hardware
1. (What kind of computers will the application run on? Desktop, Laptop, tablets, Phones, etc)
iv. Supported Operating Systems
1. Desktop/Tablet/Laptop/Phone Components
a. Microsoft Windows 7, Microsoft Windows 8
2. Server Components
a. Microsoft Window Server 2008 R2
v. Target Databases
1. (SQL Server, VFP, Access, NoSQL)
c. Requirements
i. See Requirements document
ii. Phases
iii. Deliverables
iv. Milestones
v. Interoperability with other applications
1. Will the software interact with other software applications?
2. Will the software use an third party components
vi. Source Code Control
vii. Testing
Do you guys use or do anything like this? Any thoughts on this? Amy I missing anything critical?
If it's not broken, fix it until it is
|
|
|
|
|
Accounting department contact!
I must admit I was never that organised when I was consulting, probably explains why I am a contractor!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Don't be too demanding, contracting has two styles, code guru, and consultant. As a consultant it might be YOUR job to provide many of these answers. Many companies are in this situation, they just don't know what they need to get to where they want to be, and that's your job, to lay it out, to set expectations.
I have been in many contracts like this, and only one that wasn't, so playing lose is IMO the best way to go about it. Communication is the key. And flexibility.
|
|
|
|
|
In my 28 years of consulting, there is one thing that's true....
"The client doesn't know what they want, but they know that what you gave them isn't it"
If it's not broken, fix it until it is
|
|
|
|
|
I would never have done this in writing, always face to face if possible and over the phone if not.
Dialogue is what I always found to be important - ask a question and 90% of clients won't know the answer, so will put down something they think is right, without too much thought.
Once I've had discussions around all of this, I will confirm it to them in writing.
PooperPig - Coming Soon
|
|
|
|
|
This is just a guideline document I created to ensure I hit all the points I need.
I go through this with my clients before each project.
If it's not broken, fix it until it is
|
|
|
|
|
I don't handle this kind of stuff for my current business, but when I was self-employed, or if I were to go back to individual contracting, I'd be more flexible than this. If someone wants to bring a contractor in, it's probably because they don't know exactly what they want (otherwise they'd get code monkeys to just write it), so answering most of those points is part of the brief. I'd get a rough idea of what they wanted, how long they expected it to take to get there and how much money they were prepared to throw at me, and then if it seemed like a job worth taking I'd get into the details of platform, technology stack etc and what the requirements might be.
If you nail everything down at the start you can guarantee it won't be like that any more by the middle, never mind the end. Better to clue the client in on that up front so you can work with changing requirements, not against them.
|
|
|
|