Friday, April 04, 2003 | |
Source: Incessant Ramblings (Technology Entries); 4/4/2003; 1:29:02 PM. Tips for debugging IE-hosted assemblies. Here's an article with some excellent tips on debugging .NET assemblies that are hosted in IE. Many of these tips are also relevant for HREF-deployed apps that are launched via IE but not necessarily embedded in the browser: Hosting .NET Assemblies in... [Incessant Ramblings (Technology Entries)] 1:33:52 PM trackback [] Articulate [] |
Source: Keith's Weblog; 4/4/2003; 9:19:12 AM I think I've finally found it. An RSS reader I like!! What a relief! Via Bill Kearny's weblog at Syndic8.com, check out NewsDesk. I've installed it, and I'm switching to it right now! Great features:
It's just really really awesome. Now for some nit-picky things.
See how minor my problems are? I'm very pleased. I'll update this if I run into any problems, but for now, I'm very happy. Watch for my Blogroll to be updated directly with the feeds from my OPML file, now that I use an aggregator that has categories. Also make sure you check out John Abbe's great and comprehensive list of RSS readers. Ok, one crash, while I was dragging stuff around into different categories. Though, it caught the exception and didn't seem to have a problem continuing. I reloaded my feed list just in case... update: yeah, it always crashes if you drag feeds around, and let your mouse hover over another feed so that it loads the contents of the feed into the right panes. But it's always able to recover from the exceptions. I'll have to e-mail the author... Hey, and it doesn't leave crap bogus referrers! [Keith's Weblog]10:15:50 AM trackback [] Articulate [] |
My comments to Robert on his weblog about his post below: Robert - I have not seen the book from Mickey Williams. Is it a Web Application book? Where did you come up with the 100,000 figure? What kinds of skills do you believe these new style "programmers" will need. I am currently one of the many unemployed Web Application developers trying to pull myself up by my bootstraps to get back into the workforce again. I am trying to stay in the IT field because I really enjoy it but the lack of available jobs is really a problem. Source: The Scobleizer Weblog; 4/4/2003; 8:47:18 AM I'm gonna be quieter than usual cause I'm working through some programming books and trying to get to a place where I can have a discussion about first steps of being a programmer. Even though beating up on John Dvorak and being called a Microsoft shill is more fun. One thing that's motivating me: I believe the industry needs 100,000 new programmers a year to fill the programming needs that exist. Unfortunately, these programmers probably won't call themselves programmers. They'll be people building internal weblogs (or, the more politically-correct term "knowledge management systems") and then hooking them up to various things inside their corporations. We're already seeing this happen. I have an RSS Aggregator inside Outlook. Why not have SAP spit out an RSS feed so that all of NEC's employees and managers could track daily sales, backorders, RMAs, and other things? But, who will program that for us? I can't get money to hire programmers. We don't have an internal programming staff that I can use (if we do, they are too busy to pay attention to something like weblogs, which aren't yet on the corporate radar screen). So, I gotta do it myself. I'm not sure it's possible. SAP doesn't really have a nice API/object model that I can get to from .NET. Although they just loaded a new one on my system, so maybe it does now. I sure don't have the skills to parse SAP's data, and put it into RSS files. Not yet, anyway. But, that's my goal. Be able to learn enough to take data out of one app, put it into RSS format, and spit it over to my Web server that's running on my desktop. I'll let you know how it goes. As far as being Microsoft's shill? Heh, I can think of worse things to shill. Microsoft makes a product (actually several) that 200 million people use (and based on my customer research, many of them use Microsoft products for eight to 12 hours a day -- I know I use Windows 14 hours a day, and Outlook and IE at least nine of those). If defending a company that's made that much change to the world earns me a label of "shill" then I'll wear that label proudly. [The Scobleizer Weblog]9:49:28 AM trackback [] Articulate [] |
Source: Marc's Voice; 4/4/2003; 8:47:31 AM. Matt Webb is in da house. Slices of the ongoing conversation on social software....
Try and ground all of this; try and explain social software to someone who has a background in evolutionary psychology/ dynamics of group decisions, and it's very hard (as discovered a few nights ago). What's the objective? So I'll ramble: There's no single defining feature of social software, no common thread. But some attributes which may or may not be shared: software which uses as data social relationships/properties; software which acts as an intermediary in social activity (conversation, decision making, wearing the same band's tshirt, clapping); software which uses human nature in the design process; software that has moved from providing an environment to providing an environment and tools, or more. . . There's so much to learn! Look at philosophy, human behaviour, psychology, biology: extract commonalities of human nature. How do people work with distance? People prefer big effects to have big causes. How do people respond to pointing, clapping, shouting, unexpected people chipping in? Look at how people work in cities: those are the best examples of things-for-a-purpose with massive, group feedback loops. And how people sit round tables in pubs. "You're looking to reconstruct the whole social world. That's a big job," was the response from the other night. Well yes and no. A cut down version -- but for that we have to know which are the important bits. We need a Fitt's Law for social software. Like: When there are twelve people who mostly haven't met talking in text, the chance of a groupwide flame war is 50%, so the button to respond person-to-person (over IM) needs to be a maximum of twice the cognitive distance as the button to respond to the group. For example. So then: Experimental social software continue (FOAF springs to mind, weblogs too). Derive rules of thumb. People who are good at being theoretical, try and find paradigms. Learn about human nature - the kind of human nature which is important here, emotional response curves maybe - groups dynamics and so on. Model, break down. Put in the implicit design laws into the requirements document, things that aren't usually thought about: people need to be able to share their address books with this application because X, people need to taskswitch to this other app because Y. The purpose of this app is to do Z therefore there needs to be capability to 1, 2 and 3. And not just proximate: is socialising in group software just as important as the Meeting Request button? Use cases, examples, models, falsification, experiment, theory, talking, above all: learning. Yes Matt does ramble on a bit, but you gotta respect somebody who puts so many shades of brown on his site. Everyone is trying to grok this stuff - on their own terms. Me - I'm a tool guy. [Marc's Voice]9:27:12 AM trackback [] Articulate [] |
Source: Marc's Voice; 4/4/2003; 8:47:32 AM More rambling from Matt, but GOOD rambling.... More social software rambling:Social.... More social software rambling:
8:56:35 AM trackback [] Articulate [] |
Source: Keith's Weblog; 4/4/2003; 8:47:36 AM
doesn't work in Mozilla... [Keith's Weblog]8:53:04 AM trackback [] Articulate [] |