Slashdot Mirror


User: randomthought

randomthought's activity in the archive.

Stories
0
Comments
5
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 5

  1. UT dishonest about source of attack on UT Austin Hit By Massive Security Breach · · Score: 3, Interesting
    I stumbled on a UT site yesterday that had a number of exposed social security numbers, after reading an article in Wired about open Web enabled databases. The UT site now appears to be down, but you can see the Google cached version here

    A click on the travel.fp3 file listed a couple hundred SSNs. It was completely wide open.

    UT made it sound like a deliberate attack, but it looks to me more like administrative incompetence (and cya).

  2. Self promotion on Linux -- Without Unix · · Score: 1
    A language is a bridge between the human way of coding a program and the computer way. I assert that Pliant is the best way now available, because it addresses the bridging goal with the highest level of flexibility

    The Pliant author certainly isn't shy about proclaiming its originality. If someone has to remind you that something is "the best" or novel it generally isn't.

  3. Nobel laureates reviewing business proposals? on Super Computing 2000 · · Score: 1
    I think that VC feeling hit me when Steve Wallach said something to the effect that they hire Nobel Laureates to come in and review your proposal. That coupled to 850 million dollars ready to invest made me realize that these guys mean business.

    These guys may mean business, but I'm glad that they aren't doing business with my money. Just because someone is a top notch physicist, for instance, doesn't mean that they know anything about good software or hardware design.

    Looks to me like these VCs are using this as a marketing ploy. Look at our business! Approved by a Nobel Laureate! Make Money Fast!

  4. Re:The book covers this on Refactoring: Improving the Design of Existing Code · · Score: 1
    I can't say I find his argument convincing. Problem is, you don't see any results for a long time. It might save time when some new feature is added, or some maintenance work done, but this most likely will be a year or two down the road. In the meantime, if you are a secretly refactoring you just seem slow.

    Also, you won't achieve much if you are the only one doing it. If you're part of a 5 person team, and only your 20% of the code is refactored, you're not going to accomplish much.

    My pessimistic view is that this just requires too long a view -- especially when most companies are only looking ahead a few months.

  5. Good idea, but what about politics... on Refactoring: Improving the Design of Existing Code · · Score: 2
    I think refactoring is a Good Thing. The problem, though, is with the politics of implementing it in an organization. Since the benefits are long term, it can be difficult to convince people to devote resources to it. Most places I've worked at, programmers who quickly churn out massive amounts of barely functional, but glitzy, prototype code are regarded by management types as geniuses, while those who argue for reengineering code are considered obstacles.

    Perhaps the book addresses this (I haven't read it). Anyone actually work anywhere where management signed on to refactoring?