|
"The chief of the team that helped find Osama Bin Laden, for instance, recruited a key deputy for the effort at the Starbucks, said another officer who could not be named" [^].
I am filled with confidence, black, thanks.
« I had therefore to remove knowledge, in order to make room for belief » Immanuel Kant
|
|
|
|
|
"It is one of the busiest Starbucks in the country, with a captive caffeine-craving audience of thousands of analysts and agents, economists and engineers, geographers and cartographers working on gathering intelligence and launching covert operations inside some of the most vexing and violent places around the world."
It is also now the only coffee shop in the world being targeted by ter'r'rists, so the rest of us can drink our coffee in peace.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Whenever I hear a Dutch speak of coffee shop, I assume he means something else:
Quote: so the rest of us can drink our "coffee" in peace.
|
|
|
|
|
You callin' me Dutch!
<rolls up sleeves>
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
<putting on height increasing shoes>
Yes what else am I going to call you?
|
|
|
|
|
Call me when you get a round in, but don't you go associating me with them dirty Dutchies!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
You ain't much if you ain't dutch.
Within you lies the power for good - Use it!
|
|
|
|
|
This coming from a guy whose name, essentially, is "a Dutch guy's pyjamas"*.
Is that the Canadian equivalent of "a big girl's blouse"?
* "Arend" is a dutch boy's name, for those not in the know.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Mike* says it best[^].
* Not Caine; Myers, who wrote the script, and who spent part of his early career working in NL.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
+5
Within you lies the power for good - Use it!
|
|
|
|
|
Oh! Terrorists! And here I thought "the effort at the Starbucks" was about getitng into the baristas pants.
|
|
|
|
|
Can I have fries with that, just got a new meaning.
|
|
|
|
|
|
|
|
|
Hmm. Maybe I'll stop in and check that out. I'm driving to Rochester today (I live in Ohio), for work next week.
Software Zen: delete this;
|
|
|
|
|
I'm developing a proposal to replace a 40 30+ yo manufacturing system with newer technology. Can't believe I just said that. Given it's a manufacturing system, we have the following basic components:
- database backend: probably sql server, no real preference
- reporting system: any reporting system is better than they have
- user interface for production: something flexible - conundrum.
The UI - I'm still trying to plow through the WinForms / WPF / WinRT debate. I have an enterprise license for a GUI toolkit that supports all of them, so I'm flexible, although I admit to wanting to do something new. This will be my first serious application in C#, so I want to have some fun.
What I will do is have a clean data layer - then I can target anything I want. I can see a desktop plus a tablet interface. In some cases, they may want a web interface, but I would farm that out. Ugh.
So - leaning toward WPF with a thought to rt. What would you pick?
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
modified 1-Oct-14 5:01am.
|
|
|
|
|
My personal preference would be SQL Server, SSRS for reporting and a Winforms or WPF front-end.
Create a backup database using log shipping and for your reporting create another database using replication from which you run SSRS. That way you can keep the live data on a database that is not being hit by requests for reports.
With regards to the front end while WPF is a great technology, if you have not used it before it is going to be an incredibly steep learning curve.
It is very different to winforms and you can't really jump right in until you have understood something the fundamentals of WPF, as I have discovered.
Good luck 
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
charlieg wrote: a 40 yo manufacturing system
charlieg wrote: reporting system: any reporting system is better than they have
They already used Crystal Reports 40 years ago? 
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
haha - no. years ago we would have custom s/w that generated the reports. We do this now in "report systems" that work on a different abstraction layer.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I would second Guy's recommendation. However I would use a WCF to service the data requirements and probably an OData or Json transport format. This should allow you to have 1 service and any UI can feed of it.
While WPF is going to be a challenge it is well worth the effort. SQL Server and Reporting Services is really a no brainer if you have experience with them.
Look into a set of UI controls, we use Telerik and are reasonably satisfied with them. There are also alternative reporting tools but I like SSRS for the service (RDL) and embedded (RDLC) formats.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
WCF - that qualifies as shiny.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: WCF - that qualifies as shiny.
No, that qualifies as a solid and best practice way to access your data layer. That way all your apps can use the service to access the data; wpf, internet, mobile, etc....
Just saying.
Edit: Didn't want to come off harsh. Just want you to know, that WCF is not shiny technology. Who is going to be developing this new system, in house software engineers or are you going to have to hire out?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
