Forum Replies Created

Viewing 15 posts - 256 through 270 (of 1,053 total)

  • RE: Byte Me: Earning in the Grave

    30 years? Wow, IT has its price.

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: A Buggy Release

    I think this also highlights the need for built in 'sanity checks' for all code, especially critical stuff, to take emergency action and notification. The sanity check should have nothing...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Fuzzy Processing

    TheFault (7/7/2016)


    You could have just used pigeons! https://en.wikipedia.org/wiki/Project_Pigeon

    Or this 😛

    https://archive.google.com/pigeonrank/

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Fuzzy Processing

    We really need a lot more research into that area, because strict algorithmic approaches are slow and can be error prone.

    Thousands of species of animals from insects up through birds...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: A Beautiful Google Mind

    Through most of our evolutionary history, the vast majority of humans on the planet primarily had to worry about their next meal. People who had the resources and the wisdom...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Great Developers

    Great developer is a bit vague. Fast? Accurate? Into arcane algorithmics? How about dependable? works with others? not ego driven?

    There are great musicians that are impossible to work with, others...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Bias, the Serial Killer of Diversity

    It's important to keep the horse before the cart.

    In an egalitarian organization diversity will naturally occur, and be healthy. Diversity that's created, however, as a target goal is likely to...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: What's Your Test Plan?

    When you have a lot of third party stuff (as we do) there's a real black box problem. It's hard to even know if you've tested adequately.

    This is one reason...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Solving Tempdb Issues

    The basic issue was that tempdb files were sized unequally, discovered after "months of investigation."

    Frequently when one sees an 'explanation' like this, there's a whole lot that's not...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: What Does a DBA Do?

    It depends largely on the organization. Sometimes we wear a number of database related hats, in some organizations it would be highly siloed.

    Interestingly in our organization we have one largish...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: A nice whistle and flute

    "Don't ever take a fence down until you know why it was put up." - Robert Frost

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Crack that Encrypted Data

    Offsite versioning is definitely a plus.

    But for high profile attacks on high profile targets, there is another targeting approach: silently decrypt files each time they are accessed, re encrypt when...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Crack that Encrypted Data

    An anonymous removal technique could possibly be a disguised vector.

    [One thing that puzzles me (not that I have all the details) about the hospital incident is that patient records were...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: The Math on Automation

    We know that humans are bad at being consistent and reliable, and those are the places we should use computers. Even if the time savings don't directly add up,

    Basically this...

    ...

    -- FORTRAN manual for Xerox Computers --

  • RE: Too much information can be counter-productive

    Many years ago as a teenager I worked at a camera store that carried a large variety of models. In my inexperience and enthusiasm I would attempt to discuss the...

    ...

    -- FORTRAN manual for Xerox Computers --

Viewing 15 posts - 256 through 270 (of 1,053 total)