$20K. My choice. Large enough to get back from wherever in the world I am that has gone to hell and small enough to manage if it goes bad in some other way (like in TFA).
This is entirely correct. I have a corporate Amex. The card is mine. My debt, my responsibility.
All that is different is that it is conveniently integrated into the company's expense reporting system, so rather than fiddling with receipts, I can just click on the charges and they get dropped into my expense claim with all the necessary details transferred.
I think I should go to a different thread where I can be less accurate.
I have a book called "Purely Functional Data Structures". Half the book is talking about all the things you can't do and why. I don't recommend it unless that's a topic that interested you. If it is, the title is spot on..
Functional HDLs are where you can write purely functional code all day, The fit to instantiated silicon is perfect. There are no side effects in logic gates.
Most of my code is designing chips. Chip design is a lot less forgiving, errors are permanent. Applying a chip design style verification and validation approach to software development is my personal top tip to the world of software development.
Yes. My assertion is that the debugger you need is not better than the ones that are available everywhere.
Instrumented code will assist locating a problem in both a unit and production environment context. The worst bugs are compositional and debuggers really don't help there because the units all work correctly. Instrumented code will help you realize you were stupid when you thought you could put things together that way.
My code constantly reminds me that I'm too stupid to write code.
You could think of it that way. But I may have designed that device and I'm telling you, an instruction copied the character into a register in the hardware, causing a change of the hardware state, or given the nature of the times, a pcie bus master sucked it from a cache line.
>Be my guest. Personally, I think snails are disgusting.
Overcome your food phobia. Snails taste delicious. Garlic and butter are the traditional cooking medium but I had them cooked in a bacon gravy at Morel's restaurant in Vegas and they were superb.
Instrumented code. Unit testing. Live testing. Rapid build - test turnaround.
If you're looking for a better debugger, you're doing it wrong. You need to instrument your code with the features to make it testable from within the running code base.
You don't build datacenters that way - fully populated.
Upgrading buildings is hard. Adding racks is a pain. Adding things into racks is relatively painless.
So you build a building that could hold and cool 5 zettabytes if you needed it to. Half fill it with racks. Populate those racks consistent with your current compute and storage needs. Add compute, storage and racks as your needs increase.
Typically these buildings remain half full, because computers and disks get better faster than people understand. So you swap out old machines for 8x faster machines and disks for 8x bigger disks and never crack into the extra racks.
Yes. The alternative is that I do a lot of work to solve the problem. I have plenty of work to be getting on with, squeezing better crypto into your processors. Coding GUI applications is simply not my bag.
What Visio does that is useful to me is allow you to edit the table of vectors for a shape, but put functions in the coordinates. So you can for example, easily add an arrowhead to a wide bus arrow that maintains its shape, angle and aspect ratio while the arrow can be stretched and skewed.
There are lots of other things, but this is the single massively useful feature that keeps me using it.
Since no one else does algorithmic smartshapes, I am led to wonder whether patents are part of the reason for them not being used in other . But Visio first came out in 1992, so that's 21 years ago. So get coding people.
Yes. You can print to PDF, but then you have a PDF. It isn't editable. So you need to hang onto both the 'compiled' PDF and the visio file. Then there is no command line build for the Visio->PDF. So re-typesetting the latex then requires a manual Visio step if you change the pictures.
Slashdot Mirror
$20K. My choice. Large enough to get back from wherever in the world I am that has gone to hell and small enough to manage if it goes bad in some other way (like in TFA).
This is entirely correct. I have a corporate Amex. The card is mine. My debt, my responsibility.
All that is different is that it is conveniently integrated into the company's expense reporting system, so rather than fiddling with receipts, I can just click on the charges and they get dropped into my expense claim with all the necessary details transferred.
>Who the hell drives from Boston to Atlanta?
Tamerlan and Dzhokhar Tsarnaev probably had plans to do that a few days ago.
It was probably the 'healthy whole grains' that gave her the cavities. The flouride just masks the effect a bit. That and a K2 deficiency.
Don't tell everyone the scheme. Sheesh!
Now Yahoo will be stuck giving information to the US government on US dissidents.
I want your policies to be constant. Plank Constants.
I think I should go to a different thread where I can be less accurate.
I have a book called "Purely Functional Data Structures". Half the book is talking about all the things you can't do and why. I don't recommend it unless that's a topic that interested you. If it is, the title is spot on..
Functional HDLs are where you can write purely functional code all day, The fit to instantiated silicon is perfect. There are no side effects in logic gates.
>unexpected separation of the booster's umbilical cable
I hate it when that happens.
I agree completely. I was just nit picking the idea of writing 'purely functional code'. In the real world, purely functional code doesn't happen.
Most of my code is designing chips. Chip design is a lot less forgiving, errors are permanent. Applying a chip design style verification and validation approach to software development is my personal top tip to the world of software development.
Companies big and small provide employee-only web interfaces to perform administrative tasks. These web sites are uniformly awful.
Yes. My assertion is that the debugger you need is not better than the ones that are available everywhere.
Instrumented code will assist locating a problem in both a unit and production environment context. The worst bugs are compositional and debuggers really don't help there because the units all work correctly. Instrumented code will help you realize you were stupid when you thought you could put things together that way.
My code constantly reminds me that I'm too stupid to write code.
You could think of it that way. But I may have designed that device and I'm telling you, an instruction copied the character into a register in the hardware, causing a change of the hardware state, or given the nature of the times, a pcie bus master sucked it from a cache line.
'monad' is the politically correct term for 'side effect'.
>Be my guest. Personally, I think snails are disgusting.
Overcome your food phobia. Snails taste delicious.
Garlic and butter are the traditional cooking medium but I had them cooked in a bacon gravy at Morel's restaurant in Vegas and they were superb.
>What are the better alternatives?
Instrumented code.
Unit testing.
Live testing.
Rapid build - test turnaround.
If you're looking for a better debugger, you're doing it wrong.
You need to instrument your code with the features to make it testable from within the running code base.
You don't build datacenters that way - fully populated.
Upgrading buildings is hard. Adding racks is a pain. Adding things into racks is relatively painless.
So you build a building that could hold and cool 5 zettabytes if you needed it to. Half fill it with racks. Populate those racks consistent with your current compute and storage needs. Add compute, storage and racks as your needs increase.
Typically these buildings remain half full, because computers and disks get better faster than people understand. So you swap out old machines for 8x faster machines and disks for 8x bigger disks and never crack into the extra racks.
>Sure, it's better than most people in Utah make, but by no means "good" pay by any objective metric
It's worst in Utah. That $47-$61k has to stretch to paying for 3-4 wives.
If you're writing purely functional code, you can do that trivially...
But if you're writing purely functional code, you can't have any output, because that would be a 'side effect'.
Functional programming is an unnatural act.
They just need to fit the phone with a dickpointnanometer.
Yes. The alternative is that I do a lot of work to solve the problem. I have plenty of work to be getting on with, squeezing better crypto into your processors. Coding GUI applications is simply not my bag.
The scripts run within the GUI, not the other way around.
It's probably possible, but I'm not in the habit of solving this sort of artificial problem when I have work to do.
What Visio does that is useful to me is allow you to edit the table of vectors for a shape, but put functions in the coordinates. So you can for example, easily add an arrowhead to a wide bus arrow that maintains its shape, angle and aspect ratio while the arrow can be stretched and skewed.
There are lots of other things, but this is the single massively useful feature that keeps me using it.
Since no one else does algorithmic smartshapes, I am led to wonder whether patents are part of the reason for them not being used in other . But Visio first came out in 1992, so that's 21 years ago. So get coding people.
Yes. You can print to PDF, but then you have a PDF. It isn't editable. So you need to hang onto both the 'compiled' PDF and the visio file. Then there is no command line build for the Visio->PDF. So re-typesetting the latex then requires a manual Visio step if you change the pictures.