You're going to get 50 posts telling you to just use a wiki. That's decent for documentation but hardly the answer you need.
My suggestion is to try something like Plone. Set up document types for inventory and any specialized documentation you may need. You can set up simple workflows for processes if you want to get fancy (e.g. track computer order status). You can easily attach documents like spreadsheets as well.
I think you should look at one decent open source package you can customize a little (in Plone's case with no programming) which would encompass as much as you want to manage in one place.
The industry as a whole may be "healthy" but it's lacking innovation. Most new games are far too similar to their predecessors. There hasn't been a whole new genre introduced for at least a decade (at least none I can think of, correct me if I'm wrong).
I love WWII games and there are often fun new things in each game. But they're still all basic FPS. Sure we can now talk with our comrades in arms, but it's still the same game. I'm not seeing much rapic change in anything except graphics.
I'm as anti-Microsoft as you can get but you're just plain wrong. Check the public research and also the incidence reports within your own company. The vast majority of security failures are social, not technical. Bot net activity is a thorn in the side of security workers but it's not causing the most security breaches.
Restricting access to things you do not own is not treating you like a criminal.
True, but taking my fingerprints and putting them on file at the FBI within the first hour of a new job is criminal treatment. After all the SEC, FBI, and other background checks you still get put on file at the FBI when taking a job at most brokerage firms (at least here in NYC).
It's beyond technical. At many companies you're treated as if they need to always look over your shoulder. Those cameras aren't there for your benefit. They're there to catch you if you do anything wrong.
Every good security expert will tell you the problem is far more social than technical. We can put in all the encryption and layers you want. But we can still call up 8 out of 10 companies and get the operator's computer password over the phone. The point is it'll always be about the user.
Your average sys admin will see encrypted traffic on port 443 and think you're browsing web sites (https).
A better sys admin will notice you're connected to a server with an odd name (myhomeserver.dyndns.org or whatever) but still wouldn't think much of it.
The best sys admin probably won't notice because there's so much traffic going through the proxy on ports 80 and 443 that they won't bother to look at each server's name. They'll mostly trust the proxy filter to block bad host names, but your random server's name won't be on such a list.
The disguntled employee has always been the biggest security threat to any company. The only new thing today is how much easier it is to disrupt security and how often security is breached accidentally. I still see idiots send out passwords in plain text e-mails all the time. Educating employees is just as important as not disenfranchising them and properly securing networks.
Look at what they're not doing and focus on that. That's where the real disruptive technology comes from.
First reaction is... well, duh. Don't do what everyone else does if you want to stand out.
But actually isn't that often not true? The better mouse trap is often disruptive. Portable music players were around for a long time before the iPod. The Apple Newton was out long before the Palm. People were downloading music long before iTunes.
Don't know why I'm focusing on Apple, but those are what came to mind.
And that's total bullshit. OS X is arguably easier to learn for someone who's new to computers altogether, but anyone who has only ever used Windows before, faced with a Mac, is going to have a terribly frustrating time just trying to resize a window ("I click on the left edge and drag, to make it wider, and the window moves instead! What's with that?"), let alone figuring out how on earth the Dock is supposed to work.
Not in my experience. Everyone I've ever seen switch, including myself with 15 years Windows experience, has had no problem at all catching on to the differences. My entire company of software developers switched with no problem and vastly increased productivity. My girlfriend switched with very few questions. Windows/Linux to Mac is the easiest switch possible. Every time I have to use a Windows machine again I turn into all thumbs because it's designed so poorly.
My understanding is that in the EU they've already been found guilty. This is a fine for further non-compliance, which I imagine would have little bearing on other lawsuits. Although I suppose if they're fined some of their competitors can claim they were the ones affected and it may help their lawsuits. I dunno.
I spent years gathering info on Microsoft for a major NY financial firm. It's not an obsession. I was paid. Posting a relevant link to a/. article is never a bad thing.
Still just a slap on the wrist until they actually get Microsoft to end its anti-competitive practices. The day a government actually gets Microsoft to change its corporate conduct is the day I'll applaud.
Wow, do you not even understand what you're reading?
"When you use Microsoft Visual Studio.NET to create ASP.NET Web Forms, code-behind pages are the default method. In addition, Visual Studio.NET automatically performs precompilation for you when you build your solution. Note that code-behind pages that are created in Visual Studio.NET include a special page attribute, Codebehind, which Visual Studio.NET uses."
So if you don't use VS.NET you may know of inline code. I was using VS.NET and nowhere in the documentation or options did I see references to in-line code. So on the one had I may be wrong. But on the other MS isn't documenting well in visual studio.
And did you bother to read the other link? Of course web-related stuff is written in.NET. But the only client apps completely written in.NET are internal to Microsoft. 4 years ago they said Office would be completely rewritten in.NET within 2 years. Never happened. So far all they've done is connect to the framework so people can write scripts and plug-ins to some apps.
You keep drinking the coolaid. Obviously you have a need to justify the fact your own site runs on.NET. It's not the best option but it's one you chose.
Many in the commercial software community call open vs. closed source a religious debate. They argue they're on the pragmatic side. The open source community often tries to portray their side as practical, not idealistic. Framing this in religious tones in not going to help. It only stokes the fires and brings this article's author more readers. I see this as just media sensationalism with some facts thrown in.
On your first point, you're wrong. I've written web apps in asp.net and it requires separate html and code files. The old ASP does not.
Of course web outlook was written in.NET. But no CLIENT applications have been rewritten in.NET as Microsoft promised 4 years ago. If you think the article is a joke then you must not care about facts, because it's not an opinion piece. It's only a summary of facts.
Slashdot Mirror
You're going to get 50 posts telling you to just use a wiki. That's decent for documentation but hardly the answer you need.
My suggestion is to try something like Plone. Set up document types for inventory and any specialized documentation you may need. You can set up simple workflows for processes if you want to get fancy (e.g. track computer order status). You can easily attach documents like spreadsheets as well.
I think you should look at one decent open source package you can customize a little (in Plone's case with no programming) which would encompass as much as you want to manage in one place.
The industry as a whole may be "healthy" but it's lacking innovation. Most new games are far too similar to their predecessors. There hasn't been a whole new genre introduced for at least a decade (at least none I can think of, correct me if I'm wrong).
I love WWII games and there are often fun new things in each game. But they're still all basic FPS. Sure we can now talk with our comrades in arms, but it's still the same game. I'm not seeing much rapic change in anything except graphics.
I'm as anti-Microsoft as you can get but you're just plain wrong. Check the public research and also the incidence reports within your own company. The vast majority of security failures are social, not technical. Bot net activity is a thorn in the side of security workers but it's not causing the most security breaches.
Restricting access to things you do not own is not treating you like a criminal.
True, but taking my fingerprints and putting them on file at the FBI within the first hour of a new job is criminal treatment. After all the SEC, FBI, and other background checks you still get put on file at the FBI when taking a job at most brokerage firms (at least here in NYC).
It's beyond technical. At many companies you're treated as if they need to always look over your shoulder. Those cameras aren't there for your benefit. They're there to catch you if you do anything wrong.
Every good security expert will tell you the problem is far more social than technical. We can put in all the encryption and layers you want. But we can still call up 8 out of 10 companies and get the operator's computer password over the phone. The point is it'll always be about the user.
Your average sys admin will see encrypted traffic on port 443 and think you're browsing web sites (https).
A better sys admin will notice you're connected to a server with an odd name (myhomeserver.dyndns.org or whatever) but still wouldn't think much of it.
The best sys admin probably won't notice because there's so much traffic going through the proxy on ports 80 and 443 that they won't bother to look at each server's name. They'll mostly trust the proxy filter to block bad host names, but your random server's name won't be on such a list.
IM forbidden? Tunnel it through SSH on port 443. Works every time and the company can't spy on what you're IMing.
The disguntled employee has always been the biggest security threat to any company. The only new thing today is how much easier it is to disrupt security and how often security is breached accidentally. I still see idiots send out passwords in plain text e-mails all the time. Educating employees is just as important as not disenfranchising them and properly securing networks.
His point seems to be more about "disruptive" than "new".
Look at what they're not doing and focus on that. That's where the real disruptive technology comes from.
First reaction is... well, duh. Don't do what everyone else does if you want to stand out.
But actually isn't that often not true? The better mouse trap is often disruptive. Portable music players were around for a long time before the iPod. The Apple Newton was out long before the Palm. People were downloading music long before iTunes.
Don't know why I'm focusing on Apple, but those are what came to mind.
And that's total bullshit. OS X is arguably easier to learn for someone who's new to computers altogether, but anyone who has only ever used Windows before, faced with a Mac, is going to have a terribly frustrating time just trying to resize a window ("I click on the left edge and drag, to make it wider, and the window moves instead! What's with that?"), let alone figuring out how on earth the Dock is supposed to work.
Not in my experience. Everyone I've ever seen switch, including myself with 15 years Windows experience, has had no problem at all catching on to the differences. My entire company of software developers switched with no problem and vastly increased productivity. My girlfriend switched with very few questions. Windows/Linux to Mac is the easiest switch possible. Every time I have to use a Windows machine again I turn into all thumbs because it's designed so poorly.
eBay is arguing that infringements should not automatically result in injunctions and shutdowns.
"Yeah, we know we've been found guilty of using something illegally... but that doesn't mean we should be stopped from using it! C'mon!"
My understanding is that in the EU they've already been found guilty. This is a fine for further non-compliance, which I imagine would have little bearing on other lawsuits. Although I suppose if they're fined some of their competitors can claim they were the ones affected and it may help their lawsuits. I dunno.
I spent years gathering info on Microsoft for a major NY financial firm. It's not an obsession. I was paid. Posting a relevant link to a /. article is never a bad thing.
Still just a slap on the wrist until they actually get Microsoft to end its anti-competitive practices. The day a government actually gets Microsoft to change its corporate conduct is the day I'll applaud.
Hacking the xbox doesn't require a mod chip any more? I had no idea! I'm way behind. That's very cool. "No soldering required."
My hacked, Xbox that is.
Thank you for reporting this DMCA violation. Federal marshals will arrive at your premises shortly.
Resistance is futile,
William H. Gates, III
LOL!!! You know less about web standards than Microsoft!
Please enlighten us. What HTML 4 form tag inherently gives us WYSIWYG without javascript?
So instead of Javascript would you prefer ActiveX? Basically you have to pick one.
Just ask Microsoft.
Or an ex-customer like me.
Perception of course matters to many people. But hopefully reality matters to many more people.
Apple, please... just please... do everything you can to keep your customers' computers safe. That's all I ask. Appoint a CSO or don't, I don't care.
You make a very good point. I'd mod you up but you're responding to my own post. :)
Wow, do you not even understand what you're reading?
.NET to create ASP.NET Web Forms, code-behind pages are the default method. In addition, Visual Studio .NET automatically performs precompilation for you when you build your solution. Note that code-behind pages that are created in Visual Studio .NET include a special page attribute, Codebehind, which Visual Studio .NET uses."
.NET. But the only client apps completely written in .NET are internal to Microsoft. 4 years ago they said Office would be completely rewritten in .NET within 2 years. Never happened. So far all they've done is connect to the framework so people can write scripts and plug-ins to some apps.
.NET. It's not the best option but it's one you chose.
"When you use Microsoft Visual Studio
So if you don't use VS.NET you may know of inline code. I was using VS.NET and nowhere in the documentation or options did I see references to in-line code. So on the one had I may be wrong. But on the other MS isn't documenting well in visual studio.
And did you bother to read the other link? Of course web-related stuff is written in
You keep drinking the coolaid. Obviously you have a need to justify the fact your own site runs on
Many in the commercial software community call open vs. closed source a religious debate. They argue they're on the pragmatic side. The open source community often tries to portray their side as practical, not idealistic. Framing this in religious tones in not going to help. It only stokes the fires and brings this article's author more readers. I see this as just media sensationalism with some facts thrown in.
On your first point, you're wrong. I've written web apps in asp.net and it requires separate html and code files. The old ASP does not.
.NET. But no CLIENT applications have been rewritten in .NET as Microsoft promised 4 years ago. If you think the article is a joke then you must not care about facts, because it's not an opinion piece. It's only a summary of facts.
Of course web outlook was written in
Microsoft's .NET - Why you shouldn't use it.