The only problem with Adblock is that some pages are specifically formatted for an image of a certain size, and cutting them out still leaves an annoying section of white space.
For situations that require those kind of restrictions, it makes sense to have a PC for coding, and a separate PC for Internet browsing.
A former colleague of mine works at a f*cking large investment bank doing security, and they have two PC's on their desks, one for internal connections, and one for external (Internet) connections. Connecting the two is grounds for being fired.
The rendezvous implementation in iTunes is brilliant. Within the office I can listen to my workmates music library, and vice versa.
In this type of office setup, it makes so much more sense to integrate rendezvous into anything that would benefit from collaboration, as your apps can see whoever else is running the app, and provide a dynamic way for finding and communicating with colleagues.
I believe subthaedit (or another mac editor) already uses this to enable people to work on the same document/code/etc at the same time.
I started a blog about the goings on at the office a while back, after disatisfaction with my bosses management style, and somewhat dodgy approach ("you want me to do some work for you? What's in it for me?").
Recently, I've been helping a coworker with getting his personal website up, and have been pointing him to my website as an example. In referring to my website, he later took a look at it one evening, and found the link to my blog about the office, and mentioned it the following day.
Thankfully, he shares my feelings about what's been going on, so I don't have to worry that much. But the risk suddenly hit home. I straight away removed the link to the blog.
As I've been involved in my field for a while, I feel confident in saying to recruiters and employers to google for my name, to find references to what I've worked on in the past. However, in doing so, they'll probably discover my postings about the office. As bloggers tend to be a bit more carefree about their postings online, they'll tend to be more open. However, your attitudes may not sit well with the person reviewing your site, and in charge of saying yes or no to hiring you.
There are also technologies that can sit around the server that can boost speed, dependant on typical pages being served. A proxy can sit in front of a server (or collection of servers), and provide the cached, static data to visitors. Heavy load combined with backend queries would be the hardest to cache this way.
I trained on it in 2001, and it seemed quite cool at the time. What most impressed me was that they had a scriptable network service designed for third-party customisation. Ie, you send "add user blah profile blah" to create new users.
For corporations looking at eliminating the overhead of having to manage both a unix server and the application running on it, an appliance server (like mirapoint) makes sense.
I agree with the right tool for the job sentiment. I'm familiar with Bash, Python, Tcl and Ruby. I initially looked at doing something with Ruby, but the RSS module tutorial was somewhat confusing. I ended up with the beautifully simple feedparser module for Python, and got the job done very quickly.
If I'd been somewhat biased, I could've spent a lot of time banging my head trying to figure out how to use the Ruby version, but instead, in this instance, went to something that I found simpler and quicker to get into.
For years I've been living at my salary level, never putting anything aside for a rainy day. Two things brought about a change in this.
Realising that putting together enough cash for a mortgage deposit doesn't happen overnight.
Having my girlfriend ask me: "after all the money you've earned in the last few years, where has it all gone?"
I have started pulling back from my recurring, weekly (I'm also payed weekly) episodes of retail therapy, and regular purchases of several hundred dollars worth of shit that I don't need. I straight away put away 1/5 of my paycheck into savings each week, pay myself once each week a few hundred dollars "pocket money" for food, entertainment and transport costs, and any money that's left over after bills each week goes into savings as well.
My goal is to have enough to survive for a month or more without work, and if I never need to use it, it goes towards the long term goal of purchasing a house.
FYI, I'm 25 years old at the moment, and envisage purchasing something in the next three years.
Snort itself is vastly superior to any other IDS tool out there.
Snort is a great for capturing events, but one thing it does not do (but it doesn't advertise it either) is event correlation. This is where it can pair up several unique and apparently harmless events to identify an attack.
Event correlation makes analysis of IDS events a lot simpler, because instead of seeing for example, 5000 alerts about ping scans, exploit attempts, etc - it can correlate it down to tell you that 120 systems have been infected with the latest worm.
I remember James talking about the whole Microsoft/Sun collaboration. Apparently there is some confusion over what the legal agreement between the two is.
The main thing I remember him saying was that there are issues in working with MS, in that even if MS lets them have insider info on say their filesystem, they can't release this info to the Samba developers because of NDA's and IP licensing restrictions. So they have to be really careful and get signoff before they can open certain things up.
Another interesting discussion was the whole SWT vs SWING debate. James remained an advocate of Swing, and accused SWT of falling into the same traps that AWT had back in the day. From what he said, it sounded like he was saying that Swing is flexible and powerful enough to do whatever you want, but that was also its downside. An example he used was back when they were auditing Netbeans 3.6 to figure out why it was so slow. Apparently the developers had gone overboard with monitoring events, and a single drag of a window resizer would trigger thousands of events (an "event storm" he called it), which would also in turn spawn a bunch of "stormlets", small event loops (events triggering other events which trigger other events ad nauseum). Apparently this was the cause of the slowness.
One of the people who was asking a question of James asked the audience to raise their hands if they used Eclipse. I would guess that around 90% of the audience raised their hands.
When asked his opinion on the IBM vs SCO court case, his response: "I want some of what they're smoking". He didn't get asked about Sun's IP stance however.
I also have a picture that I took of the cake for the 10th anniversary of Java. It's sitting on my phone at the moment, but I saw some other attendees take snapshots too.
Sorry this is a little haphazard. I didn't really take notes.:)
I've had a few discussions with my friends about the iPod and why it rules (in the wake of the Shuffle announcement). Here is my argument:
It's not about size: Other companies trying to advertise bigger storage will fail, except for geeks with deep pockets and niche requirements.
It's not about features: People do not purchase iPod's because they have every feature under the sun. Instead - Apple is deliberately selective.
It's about simplicity.
With regards to the iPod shuffle - yes there are other Flash mp3 players. But for consumers like my mother, who has issues navigating the file system, she doesn't have to (a) rip a cd and then (b) find where her ripped mp3's are to (c) copy them across to her flash player.
With an iPod, she simply sticks in her device to charge, and music syncs between the iPod and iTunes automatically. If she wants to burn a CD she sticks one into the computer and presses a single button: import. She doesn't need to know anything about which codec to burn a cd with (mp3/aac/wmv), or where on the filesystem they end up, or dragging an dropping. It happens for her automatically.
Simplicity and doing what it does do well - is where the iPod shines. If companies want to eat at the iPod market share, it's not about bombarding the customer with a shitload of features. Instead, make a music player, make it easy to import music (this includes minimising any DRM), and make the device SIMPLE to use. I want to be able to explain how it works to my mum in 60 seconds, and to have her "get it". If you can do that, then you've got a product which has a chance.
Software developers and marketers, learn from Apple. Simplicity is king. Don't cause the customer headaches, and they will come back for more.
My powerbook's HDD has got a problem, and it's going to cost at least $AUD 450 or so to get a replacement 40GB hdd + service.
For the meantime I've been told that I can install OS X onto a firewire drive, and boot off that. Oh well, I'll lose the portability but at least it won't be dead.
However, using Eclipse on a 12" powerbook running at 1024x768 resolution can feel a little constricting, so I too am looking out for a 15" to upgrade to. The fact that they wont be coming out for a little while gives me an opportunity to save up for it.
The only problem with Adblock is that some pages are specifically formatted for an image of a certain size, and cutting them out still leaves an annoying section of white space.
Safari has it in 10.4. :-)
For situations that require those kind of restrictions, it makes sense to have a PC for coding, and a separate PC for Internet browsing.
A former colleague of mine works at a f*cking large investment bank doing security, and they have two PC's on their desks, one for internal connections, and one for external (Internet) connections. Connecting the two is grounds for being fired.
You'll have to host your blog in Norway to state your opinion online!
I'd have just wanted access to my Safari Bookstore account. ;-)
The rendezvous implementation in iTunes is brilliant. Within the office I can listen to my workmates music library, and vice versa.
In this type of office setup, it makes so much more sense to integrate rendezvous into anything that would benefit from collaboration, as your apps can see whoever else is running the app, and provide a dynamic way for finding and communicating with colleagues.
I believe subthaedit (or another mac editor) already uses this to enable people to work on the same document/code/etc at the same time.
The student has surpassed the master!
I started a blog about the goings on at the office a while back, after disatisfaction with my bosses management style, and somewhat dodgy approach ("you want me to do some work for you? What's in it for me?").
Recently, I've been helping a coworker with getting his personal website up, and have been pointing him to my website as an example. In referring to my website, he later took a look at it one evening, and found the link to my blog about the office, and mentioned it the following day.
Thankfully, he shares my feelings about what's been going on, so I don't have to worry that much. But the risk suddenly hit home. I straight away removed the link to the blog.
As I've been involved in my field for a while, I feel confident in saying to recruiters and employers to google for my name, to find references to what I've worked on in the past. However, in doing so, they'll probably discover my postings about the office. As bloggers tend to be a bit more carefree about their postings online, they'll tend to be more open. However, your attitudes may not sit well with the person reviewing your site, and in charge of saying yes or no to hiring you.
I'm more cautious today as a result.
Modules that require compiling on a platform like Solaris which doesn't by default come with a compiler... are annoying.
There are also technologies that can sit around the server that can boost speed, dependant on typical pages being served. A proxy can sit in front of a server (or collection of servers), and provide the cached, static data to visitors. Heavy load combined with backend queries would be the hardest to cache this way.
I trained on it in 2001, and it seemed quite cool at the time. What most impressed me was that they had a scriptable network service designed for third-party customisation. Ie, you send "add user blah profile blah" to create new users.
For corporations looking at eliminating the overhead of having to manage both a unix server and the application running on it, an appliance server (like mirapoint) makes sense.
Dan Bernstein is a proponent of this approach, as can be seen by looking at the approach taken in his programs such as Qmail.
I agree with the right tool for the job sentiment. I'm familiar with Bash, Python, Tcl and Ruby. I initially looked at doing something with Ruby, but the RSS module tutorial was somewhat confusing. I ended up with the beautifully simple feedparser module for Python, and got the job done very quickly.
If I'd been somewhat biased, I could've spent a lot of time banging my head trying to figure out how to use the Ruby version, but instead, in this instance, went to something that I found simpler and quicker to get into.
For years I've been living at my salary level, never putting anything aside for a rainy day. Two things brought about a change in this.
I have started pulling back from my recurring, weekly (I'm also payed weekly) episodes of retail therapy, and regular purchases of several hundred dollars worth of shit that I don't need. I straight away put away 1/5 of my paycheck into savings each week, pay myself once each week a few hundred dollars "pocket money" for food, entertainment and transport costs, and any money that's left over after bills each week goes into savings as well.
My goal is to have enough to survive for a month or more without work, and if I never need to use it, it goes towards the long term goal of purchasing a house.
FYI, I'm 25 years old at the moment, and envisage purchasing something in the next three years.
Pfft. The real trick is that you need to have the fastest alt-tab in the west!
I'm pretty sure I saw this in a Scott Adams book, the Joy of Work at the expense of your coworkers.
Snort is a great for capturing events, but one thing it does not do (but it doesn't advertise it either) is event correlation. This is where it can pair up several unique and apparently harmless events to identify an attack.
Event correlation makes analysis of IDS events a lot simpler, because instead of seeing for example, 5000 alerts about ping scans, exploit attempts, etc - it can correlate it down to tell you that 120 systems have been infected with the latest worm.
I remember James talking about the whole Microsoft/Sun collaboration. Apparently there is some confusion over what the legal agreement between the two is.
:)
The main thing I remember him saying was that there are issues in working with MS, in that even if MS lets them have insider info on say their filesystem, they can't release this info to the Samba developers because of NDA's and IP licensing restrictions. So they have to be really careful and get signoff before they can open certain things up.
Another interesting discussion was the whole SWT vs SWING debate. James remained an advocate of Swing, and accused SWT of falling into the same traps that AWT had back in the day. From what he said, it sounded like he was saying that Swing is flexible and powerful enough to do whatever you want, but that was also its downside. An example he used was back when they were auditing Netbeans 3.6 to figure out why it was so slow. Apparently the developers had gone overboard with monitoring events, and a single drag of a window resizer would trigger thousands of events (an "event storm" he called it), which would also in turn spawn a bunch of "stormlets", small event loops (events triggering other events which trigger other events ad nauseum). Apparently this was the cause of the slowness.
One of the people who was asking a question of James asked the audience to raise their hands if they used Eclipse. I would guess that around 90% of the audience raised their hands.
When asked his opinion on the IBM vs SCO court case, his response: "I want some of what they're smoking". He didn't get asked about Sun's IP stance however.
I also have a picture that I took of the cake for the 10th anniversary of Java. It's sitting on my phone at the moment, but I saw some other attendees take snapshots too.
Sorry this is a little haphazard. I didn't really take notes.
I found out about Rojo by looking at my website logs. Went to take a look at the site and found another "you gotta be cool" (ie invited) to login.
I'm almost tempted to restrict them from accessing my blog until they give me an invite, damnit!
Google has us all fooled!!
It's about simplicity.
With regards to the iPod shuffle - yes there are other Flash mp3 players. But for consumers like my mother, who has issues navigating the file system, she doesn't have to (a) rip a cd and then (b) find where her ripped mp3's are to (c) copy them across to her flash player.
With an iPod, she simply sticks in her device to charge, and music syncs between the iPod and iTunes automatically. If she wants to burn a CD she sticks one into the computer and presses a single button: import. She doesn't need to know anything about which codec to burn a cd with (mp3/aac/wmv), or where on the filesystem they end up, or dragging an dropping. It happens for her automatically.
Simplicity and doing what it does do well - is where the iPod shines. If companies want to eat at the iPod market share, it's not about bombarding the customer with a shitload of features. Instead, make a music player, make it easy to import music (this includes minimising any DRM), and make the device SIMPLE to use. I want to be able to explain how it works to my mum in 60 seconds, and to have her "get it". If you can do that, then you've got a product which has a chance.
Software developers and marketers, learn from Apple. Simplicity is king. Don't cause the customer headaches, and they will come back for more.
My powerbook's HDD has got a problem, and it's going to cost at least $AUD 450 or so to get a replacement 40GB hdd + service.
For the meantime I've been told that I can install OS X onto a firewire drive, and boot off that. Oh well, I'll lose the portability but at least it won't be dead.
However, using Eclipse on a 12" powerbook running at 1024x768 resolution can feel a little constricting, so I too am looking out for a 15" to upgrade to. The fact that they wont be coming out for a little while gives me an opportunity to save up for it.
Yeh I test all my applications under a VMware XP system.
MIB reference for those who can't place it.
What, like Google?