Monday, April 30, 2007

Nine Inch Nails: Year Zero Reviewed

 

010507_bureau_morality_400

 

Trent Reznor is certainly up to some interesting political messages here... and he's certainly sparking a debate. I think this is great to see.

Best-selling industrial rock band Nine Inch Nails' latest album, Year Zero, delves into new ground. For the first time, the group's front man and primary writer, Trent Reznor, focuses mainly on politics. He seems to be jumping headfirst into a game of politics with the resistance party.

However, he does so not just with the album's music, but also numerous accompanying multimedia-- Reznor has thrown a private concert, scattered random tracks in random locations, made websites, all above and beyond the album itself. And it’s all about his message of resistance. Reznor covers nearly all the bases: The war on terror, the military industrial complex, the death of America from the loss of liberty, and the resultant New World Order. Reznor even had a flag made to represent the NWO.

The video to the album's first single, Survivalism, shows, in all its Orwellian glory, cameras in black and white strategically located around town displaying people in the bathroom, watching TV, having sex, preparing to vandalize a wall with graffiti, and finally, there’s Nine Inch Nails performing the song in a dingy room. There are CCTV cameras everywhere now, not just in public places. What should be private is public and worse, the people either don't realize they are being watched or have become accustomed to living without privacy.

I'm definitely going to check this album out.


http://www.jonesreport.com/articles/010507_year_zero.html

Sunday, April 29, 2007

Optimize OpenOffice's Memory Use and Speed

Some good tips here on configuring OpenOffice's memory footprint and startup speed.

  • Turn off the JRE
  • Undo
    • Number of steps = 20 (or fewer--most of us don't use that many)
  • Graphics cache
    • Use for OpenOffice.org = 128 MB
    • Memory per object = 20 MB
    • Remove from memory after = 00:10 hh:mm
  • Cache for inserted objects
    • Number of objects = 20 (or try fewer)

 


http://openoffice.blogs.com/openoffice/memory/index.html

Pic of the Earth -- Through Saturns Rings

 

saturn_cas_400

 

Spectacular pic -- you can actually see the disc of the Earth through Saturn's rings. Taken by Cassini.


http://earthobservatory.nasa.gov/Newsroom/NewImages/images.php3?img_id=17524

Tuesday, April 24, 2007

Top 5 Brain Foods

1. Wild Salmon
2. Cacao Beans
3. Matcha (Tencha-grade green tea powder)
4. Acai berries & Blueberries
5. Coffee beans

http://www.brainready.com/blog/thetop5brainhealthfoods.html

Homestarrunner Date Night

 

ussflirtini

 

Marzipan goes on a date with the cheat. 'Nuff said. 


http://homestarrunner.com/datenite.html

Deliver on Promises, Not Deadlines

Good advice about the brand called you:

What I have learned is that your business reputation relates more to the promises you make and keep than what is required of you by others. If all you think about is the deadline (they issue it to you), then you are entirely reaction and must rely on motivation to honor it. If you are the deadline chooser, then the promises flow from that. There are good deadlines (well calibrated) and bad deadlines (random acts of business.) Many deadlines are arbitrary, plucked out of the sky for you. Some are soft deadlines, others are hard. Some deadlines are dotted, which means they come from on high. The point is that your promise is your promise. In a project, manage your promises like executions. If a deadline is doable, promise the output on time. If the project has a deadline that can't or shouldn't be in place, counter with a promise that is aligned with reality. Turn the dialogue from subjective deadlines into projects needs and practical reality.

When you follow up after a meeting, send an email that recaps the promises that you made. Schedule those promises into your calendar. If you come up to a promise in your calendar you cannot keep, immediately reset external expectations. Try to align the promise with their deadline, but don't let bad deadlines impact your reputation -- push back.

This is a new form of leadership that can drive accountability into an organization. In a post mortem of a blown project/product, it is far too easy for us to sit back and say, "that deadline was impossible, not my fault". On the other side they are saying that you don't keep your promises.

Make your promise your professional brand. Own it and defend its integrity. You already know that your brand is the experience that you promise, now make the promise the key instrument in your business life. Let deadlines be deadlines, but just be your promise.

 


http://sanderssays.typepad.com/sanders_says/2007/04/keep_promise_da.html

The OSS Developer's Dillemma

 

If Riehle's analysis is correct - and while his thinking is logical, he offers no hard proof of the economic effects he describes - then what we're seeing playing out among coders is what I'll term the Programmer's Dilemma. Because skills in open source programming are increasingly necessary to enhance the potential career prospects of individual programmers, individual programmers have strong motivations to join in - and as more programmers join in, the incentive for each individual programmer to participate becomes ever stronger. At the same time, the total amount of money that goes to programmers falls as open source is adopted by more companies. Individual programmers, in other words, have selfish motives to engage in collectively destructive behavior.

Baloney.

As a developer, and one that uses and contributes to open source, I think some key points have been missed.

1. Seth nailed one of them -- it's not a closed system. If you think in terms of proprietary stacks and jobs for a given company, then sure. But the world is a big place. Big companies aren't innovating any more. Name something truly mind-blowing that has come out of Microsoft, IBM, SAP, or Oracle. It's not happening. If we developers let the market be stifled by corporate short-term thinking and mismanagement, the market as a whole will die off.

2. Joy. Good developers don't write good code because they have to, they write good code because they want to. It's like an artistic thing: corporate life hampers the interesting innovative stuff you want to work on, so when you go home you write interesting code and release it to the open source community. Simply for the joy of it.

3. Community. Many (not all) good developers are slightly introverted. Contributing to a community of like-minded people across the world gives a great sense of belonging that you simply don't get in a corporate environment.

4. Continuity. You can work on the same OSS projects for years. Jobs are short term. Working for free sucks. But many (good) developers are either contractors or skip companies every 1-3 years. They go to where the interesting work and good pay is. This is a direct result of offshoring. Companies are getting back what they've been dishing out. So what if developers get paid less at IBM because they aren't building as many proprietary solutions any more -- go work for someone that will value you.

5. Gives you a sense of purpose. Not all of us are driven completely by money -- something that economists don't get. There are other levers, including contributing to the development of third world nations. Look at Ubuntu. It was created specifically to address the needs of Africans that can't afford proprietary software.

6. Street cred. Nothing gives you more cred and notoriety (and into interviews) than contributing something genuinely elegant or innovative back to a bunch of people that can appreciate it.

7. Control. You get to decide on what to create, not some suit that doesn't get it.

8. Meritocracy. Your work is judged on it's own worth, not how you look, your accent, or what school you come from. Geeks love meritocracies.

9. Freedom. You own open source. Requiring proprietery 'ware means that it owns you.


http://www.roughtype.com/archives/2007/04/open_source_and.php

Popular Posts

Like us on Facebook