|
I tend to keep track of data in Excel, and lately I've been using it as a CRM. I keep different sheets in order to answer different kinds of questions: Who asked about cell formatting? Who did I first talk to on our online chat? How many users do we have in Chicago? In theory, each sheet is synced with a master sheet containing all customer data. In practice, maintaining everything by hand was too time-consuming, and my data became scattered. Oh, by the way, this involves scripting Excel... with Python!
|
|
|
|
|
The problem with so many portable devices... was that they required a stylus to work right. Often the stylus made touch into really more of a virtual-mouse. That’s just not the intuitive way to work. On an other level there’s something fundamentally wrong about this. Some tasks simply work better with a stylus and the limits of iOS make them annoyingly limited. The pen is mightier... than the finger?
|
|
|
|
|
From high-end gaming rigs to light-weight, always-connected tablets, Windows 8 supports the broadest range of graphics hardware ever in a single operating system. We hope this post has helped explain some ways in which this work enables a whole new set of rich experiences. Hardware accelerate all the things!
|
|
|
|
|
The 80-20 rule says that often 80% of your results come from 20% of your effort. Applied to software, 80% of your customers may only use 20% of the features. So why not just develop that 20% and let the rest go? Nothing is as simple as we hope it will be.
|
|
|
|
|
Maybe Windows 9 should just be an internet browser and nothing else.
That would satisfy The Endeavor. The rest of the lot who actually want to get some work done could do the rest of the functionality in their spare time
|
|
|
|
|
Sounds like Chrome OS' approach... not a bad idea.
daniero
|
|
|
|
|
A few weeks ago, Tom Slee published “Seeing Like a Geek,” a thoughtful article on the dark side of open data. He starts with the story of a Dalit community in India, whose land was transferred to a group of higher cast Mudaliars through bureaucratic manipulation under the guise of standardizing and digitizing property records.... That’s a serious problem. It’s sad to see oppression and property theft riding in under the guise of transparency and openness. But the issue isn’t open data, but how data is used. Data by the people, for the people, about the people.
|
|
|
|
|
Oracle researchers are "winding down" development of the Fortress programming language for high-performance computing, an effort started nearly 10 years ago by Sun Microsystems. [ ITworld]
|
|
|
|
|
|
That's ok - we'll just pass 'em all to Captain Sea-sharp.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
They don't "do mathematics". Mathematics can describe the non-linear neural processing done by the dolphins' sensory systems. But the dolphins don't do the symbolic and logical manipulations we call mathematics.
"Microsoft -- Adding unnecessary complexity to your work since 1987!"
|
|
|
|
|
Is that the same as arguing that mathematics can describe the processing done in modern computing systems, but computers don't do the symbolic and logical manipulations we call mathematics?
It seems to be a similar argument.
I wonder how you know that symbolic processing isn't going in their brains?
|
|
|
|
|
They do math the way a ball player uses a natural parabola to put a ball through a basket. It's math, not on paper, but it's the same calculations and that's what the article is talking about.
Think of how stupid the average person is, and realize half of them are stupider than that. - George Carlin
|
|
|
|
|
Have you ever taken a look at the list of functions available in PHP? I just counted 5025 on the PHP quick reference page. Granted, it depends on what extensions you have enabled, but still: that’s one heap of functions! While I can’t show you every one of them, if you’re new to the language, I’ll introduce you to seven really handy ones in this quick tip! PHP: the good parts.
|
|
|
|
|
JavaScript sucks: The depths to which JavaScript sucks is well-documented and well-understood. We need JavaScript: Using it for what it is good for, i.e. providing a platform for browser development, but not using the language per se, is therefore desirable, and many are working to achieve this, in varying forms. There are various ways to do it, but we ought to opt for compiling an existing language, Haskell, to JavaScript, because we do not have time to learn or teach other people a new language, garner a new library set and a new type checker and all that Haskell implementations provide. Because it is better to learn Haskell than stoop to actually using JavaScript in any form.
|
|
|
|
|
|
While lambda expressions in .net were derived from Haskell and are a truly gorgeous language feature, I simply don't take enough acid to use Haskell itself.
JavaScript, for it's many faults is at least familiar and actually readable when done well.
|
|
|
|
|
Unfortunately, Haskell also sucks. Does not support OO.
|
|
|
|
|
The advent of the many-core era is not going to push developers to write more parallel code. That hasn't happened as we've gone from 1- to 2- to 4- to 8-core processors, has it? Writing parallel code is not the problem. So, let's stop trying to fix it. Parallel programming is getting easier, but it's not clear most programmers need it at all.
modified 23-Jul-12 7:42am.
|
|
|
|
|
|
|
Thanks for the heads up, guys. Links should be fixed now.
Director of Content Development, The Code Project
|
|
|
|
|
First, people should first learn to program properly using callbacks - especially on the client side this sort of parallel (concurrent?) code greatly alleviates the need for multi-threading - and is dearly needed for most programmers, in web development.
Second, parallel code is easy, as long as you partition your data adequately. If all your threads want to access all your data all of the time, you're embracing congested programming instead.
|
|
|
|
|
One of the mistakes I see people make (and have made myself) is assuming that you must choose exactly one ORM strategy for an entire database/application/system. It’s simply not the case. You can (and should) tailor your ORM strategy to your use case, and make sure you’re picking the right tool (or feature of the tool) for the job. To be ORM not to be... that is the question.
|
|
|
|
|
I come across this question from time to time and here's my take on this
(a) For small # entities - use NHibernate (which I stopped using prefer simple LINQ)
(b) For large data retrival - use relational SQL
(c) For large data insert - use bcp if comma not an issue
dev
|
|
|
|