Another post mentions it, but Confluence may be a good fit. It is a Wiki, but geared towards the needs of an enterprise. Compared to other wikis, Confluence has better permission control and has better facilities for organizing articles. We have deployed several Conflence instances for clients, and all are happy.
We have a small, internal Mediawiki installation for documenting things like this. I have found that more people actually document things this way.
I also like an online tool for tracking software versions. I have a page that lists all of the F/OSS software that we have installed, along with the installed version number, the latest version number, and the URL to the distribution page. Once a week I have an intern go through and update the latest version numbers. I get notified about changes, and then I we can make the decision about whether to install the new version.
I think you are talking about two different things. Personally, I would prefer to be managed by someone who admits that they don't understand all of the details, but instead trusts the team and does a good job of helping them work together to reach the project's goals. It's one thing to understand the long term goals and have an overview of the technology involved, and another thing to stick your nose in because you have some cursory knowledge.
I think it boils down to the difference between a project manager and a technical lead. A project manager should really focus on the logistics, but keep the technical specs in mind. A tech lead is responsible for the details, and works within the guidelines that the project manager sets up.
I think it goes beyond even the nuts and bolts of a programming. A good CompSci/CompEng program teaches the critical thinking skills necessary to be a good programmer. It is not enough to know how to do something; you really need to know why you are doing something and why that thing works.
For example, I don't think there were any programming assignments in the senior/grad data structures course I took. That's the easy part. Knowing why the algorithms worked the way they did and being albe to really reason about an algorithm turned out to be far more benefical in the long run.
The only problem with this is that Eolas has freely admitted that they are not going to go after any other browser, only IE. As Mozilla, et. al gain popularity and market share, the possibility exists that we'll have a further fracturing of an already splintered HTML/Javascript implementation across browsers.
The simplest way to implement the workaround just moves some HTML code into an external Javascript file that uses document.write() instead. You would have to go out of your way to make this incompatible with other browsers. The better solutions that are already available take this a step further to add feature detection and alternate content. IMHO, users are going to get a better experience as a result of this.
You can delegate the actual details to a library. If something changes, then you only have to update the library code for a sitewide fix or even a single fix for all sites a developer is responsible for.
Depending on the implementation, you can use replacement techniques to have a single element in the DOM for what you want. Typical HTML-only solutions for Flash use nested elements. With a DOM solution for Flash, you can place an image in the HTML page by default and replace it with the proper element for the Flash piece.
Depending on you develop you site, you could easilly replace one object type with anther object type (say, replace Flash with SVG) by just altering one place in the Javascript rather than updating all the places the object is used.
I am a big fan of simple, static websites but when fancy objects are needed, mucking with the DOM client side can be handy. If content negotiation was reliable, then doing everything server side would be best, but unfortunately it's not.
I tested out the patch for a while (KB912945), and while you are correct, the impact will be noticed by a lot of people. The problem is that a lot of the flyover Flash ads on websites are a lot bigger than they actually appear. The activate area is the actual size of the Flash piece, not just what is viewable. I saw lot of instances where the activate area prevented legit clicks on normal anchors. Not really devistating, but pretty annoying.
The basic fix is that you don't use an object directly in the HTML. You either add it through document.write() or through the DOM. In other words, the fix is rather trivial, and in the long run makes the page more maintainable.
There is a lot of truth to this. A few years ago, I joined a project team after development had been underway for a while. Most of the people had no embedded experience, and I had to spend a lot of time redoing things that would have been OK on a general purpose system, but were nightmares under an RTOS. There a lot of programming fields where speciality and experience matter, and embedded systems is one of them.
I would pick the OS based on whichever has the best device driver support for everything in your product. Device driver development can chew up a lot of time. You would be better off spending resource time on the application layer of the product.
It would also be nice if ISPs would set up their own pools (and advertise them) so clients wouldn't have to go off network, and then if end-users would would set up their own pool for their networks. Not every machine that needs accurate time has to be at stratum-2 or stratum-3, especially workstations. The NTP Pool website makes it look like it is a good idea if every machine on a network syncs to the NTP Pool, instead of setting up internal servers, which is how NTP is really designed to work.
Accurate time is important when you are sharing resources with other computers. One example is running a build on an NFS share. If the file timestamps are wrong, then make may do unnecessary compiles, or skip files. Other protocols, like rsync, use timestamps to try to figure out whether updates are needed.
A proper NTP implemetation for a computer gathers information from several clock sources. The NTP protocol also has provisions to determine whether a clock is accurate or not based on the responses from other clocks. IIRC, this is called a "false ticker" in the spec.
I forget the exact term, but some cities set up business advantage zones where the sales taxes is reduced. I believe they clear this with the state, and it is an effort to revitilize run down areas.
I didn't read every link in the summary, but in the article about the receiver setup, the copper tubing you saw in the picture wan't the waveguide. The picture was a waveguide cavity filter. The box shaped thing was the waveguide, and the screws are for tuning the filter (waveguides filters are really neat). The "tubes" at each end are standard semi-rigid RF cables with SMA connectors, and not something you find at Home Deopt.
A DDC is a fairly common term in digicomm. Typically, it comprises a digitial modulator (an NCOM), a decimation circuit, and sometimes other baseband filtering. Usually, an FFT isn't involved. A bunch of companies make DDC ICs. You can Google and find the datasheets for more details.
Single-letter names under ".com," ".net" and ".org" were set aside in 1993... Six single-letter names already claimed at the time _ "q.com," "x.com, "z.com," "i.net," "q.net," and "x.org" _ were allowed to keep their names for the time being.
Programming languages aren't based on formal logic
Imperative languages aren't based on formal logic. Functional programming languages, logic programming languages, and other declarative languages are deeply rooted in formal logic. While some tasks are more difficult in these languages, being able to reason about a program is really beneficial in a lot of situations.
What is the difference between students reading the paper, doing the crossword, or sleeping during class (ie, what went on when I was in school) versus Internet use during class? Both scenarios just represent students not paying attention. In general, students who don't pay attention get lower grades.
Slashdot Mirror
Another post mentions it, but Confluence may be a good fit. It is a Wiki, but geared towards the needs of an enterprise. Compared to other wikis, Confluence has better permission control and has better facilities for organizing articles. We have deployed several Conflence instances for clients, and all are happy.
We have a small, internal Mediawiki installation for documenting things like this. I have found that more people actually document things this way.
I also like an online tool for tracking software versions. I have a page that lists all of the F/OSS software that we have installed, along with the installed version number, the latest version number, and the URL to the distribution page. Once a week I have an intern go through and update the latest version numbers. I get notified about changes, and then I we can make the decision about whether to install the new version.
I think you are talking about two different things. Personally, I would prefer to be managed by someone who admits that they don't understand all of the details, but instead trusts the team and does a good job of helping them work together to reach the project's goals. It's one thing to understand the long term goals and have an overview of the technology involved, and another thing to stick your nose in because you have some cursory knowledge.
I think it boils down to the difference between a project manager and a technical lead. A project manager should really focus on the logistics, but keep the technical specs in mind. A tech lead is responsible for the details, and works within the guidelines that the project manager sets up.
I think it goes beyond even the nuts and bolts of a programming. A good CompSci/CompEng program teaches the critical thinking skills necessary to be a good programmer. It is not enough to know how to do something; you really need to know why you are doing something and why that thing works.
For example, I don't think there were any programming assignments in the senior/grad data structures course I took. That's the easy part. Knowing why the algorithms worked the way they did and being albe to really reason about an algorithm turned out to be far more benefical in the long run.
It was originally published in 1988, though there have been other editions.
You can do analog optical communications at RF frequencies. It has several advantages, but can be cost prohibitive. Google should dig something up.
The only problem with this is that Eolas has freely admitted that they are not going to go after any other browser, only IE. As Mozilla, et. al gain popularity and market share, the possibility exists that we'll have a further fracturing of an already splintered HTML/Javascript implementation across browsers.
The simplest way to implement the workaround just moves some HTML code into an external Javascript file that uses document.write() instead. You would have to go out of your way to make this incompatible with other browsers. The better solutions that are already available take this a step further to add feature detection and alternate content. IMHO, users are going to get a better experience as a result of this.
Off the top of my head...
You can delegate the actual details to a library. If something changes, then you only have to update the library code for a sitewide fix or even a single fix for all sites a developer is responsible for.
Depending on the implementation, you can use replacement techniques to have a single element in the DOM for what you want. Typical HTML-only solutions for Flash use nested elements. With a DOM solution for Flash, you can place an image in the HTML page by default and replace it with the proper element for the Flash piece.
Depending on you develop you site, you could easilly replace one object type with anther object type (say, replace Flash with SVG) by just altering one place in the Javascript rather than updating all the places the object is used.
I am a big fan of simple, static websites but when fancy objects are needed, mucking with the DOM client side can be handy. If content negotiation was reliable, then doing everything server side would be best, but unfortunately it's not.
I tested out the patch for a while (KB912945), and while you are correct, the impact will be noticed by a lot of people. The problem is that a lot of the flyover Flash ads on websites are a lot bigger than they actually appear. The activate area is the actual size of the Flash piece, not just what is viewable. I saw lot of instances where the activate area prevented legit clicks on normal anchors. Not really devistating, but pretty annoying.
The basic fix is that you don't use an object directly in the HTML. You either add it through document.write() or through the DOM. In other words, the fix is rather trivial, and in the long run makes the page more maintainable.
There is a lot of truth to this. A few years ago, I joined a project team after development had been underway for a while. Most of the people had no embedded experience, and I had to spend a lot of time redoing things that would have been OK on a general purpose system, but were nightmares under an RTOS. There a lot of programming fields where speciality and experience matter, and embedded systems is one of them.
I would pick the OS based on whichever has the best device driver support for everything in your product. Device driver development can chew up a lot of time. You would be better off spending resource time on the application layer of the product.
Oops, my bad. You are right. I think that I need to work on my reading comprehension...
It is the lamba term
expressed with combinators. Unlamba is basically an implementation of combinatory logic, but combinators are usually written in capitals.
It would also be nice if ISPs would set up their own pools (and advertise them) so clients wouldn't have to go off network, and then if end-users would would set up their own pool for their networks. Not every machine that needs accurate time has to be at stratum-2 or stratum-3, especially workstations. The NTP Pool website makes it look like it is a good idea if every machine on a network syncs to the NTP Pool, instead of setting up internal servers, which is how NTP is really designed to work.
Accurate time is important when you are sharing resources with other computers. One example is running a build on an NFS share. If the file timestamps are wrong, then make may do unnecessary compiles, or skip files. Other protocols, like rsync, use timestamps to try to figure out whether updates are needed.
A proper NTP implemetation for a computer gathers information from several clock sources. The NTP protocol also has provisions to determine whether a clock is accurate or not based on the responses from other clocks. IIRC, this is called a "false ticker" in the spec.
I forget the exact term, but some cities set up business advantage zones where the sales taxes is reduced. I believe they clear this with the state, and it is an effort to revitilize run down areas.
I didn't read every link in the summary, but in the article about the receiver setup, the copper tubing you saw in the picture wan't the waveguide. The picture was a waveguide cavity filter. The box shaped thing was the waveguide, and the screws are for tuning the filter (waveguides filters are really neat). The "tubes" at each end are standard semi-rigid RF cables with SMA connectors, and not something you find at Home Deopt.
A DDC is a fairly common term in digicomm. Typically, it comprises a digitial modulator (an NCOM), a decimation circuit, and sometimes other baseband filtering. Usually, an FFT isn't involved. A bunch of companies make DDC ICs. You can Google and find the datasheets for more details.
FTFA:
Single-letter names under ".com," ".net" and ".org" were set aside in 1993 ... Six single-letter names already claimed at the time _ "q.com," "x.com, "z.com," "i.net," "q.net," and "x.org" _ were allowed to keep their names for the time being.
Programming languages aren't based on formal logic
Imperative languages aren't based on formal logic. Functional programming languages, logic programming languages, and other declarative languages are deeply rooted in formal logic. While some tasks are more difficult in these languages, being able to reason about a program is really beneficial in a lot of situations.
What is the difference between students reading the paper, doing the crossword, or sleeping during class (ie, what went on when I was in school) versus Internet use during class? Both scenarios just represent students not paying attention. In general, students who don't pay attention get lower grades.
Linus did come up with some whacky versions numbers at various points in the kernel history. In mid 1992 there was 0.95c+
But it also eliminates the joy of making fun of coworkers who gets lost in a raised floor, or closing them in when they go on a hunt for something...