Rollercoaster - broken wrist! | Ride | Strava
(209) Finale Ligure - Rollercoaster - Full Run - YouTube - video
W3W: ///skylark.winemaking.doddle
Just a brain dump on what stuff I have been thinking about. Most likely to do with technology, music or bikes...
Rollercoaster - broken wrist! | Ride | Strava
(209) Finale Ligure - Rollercoaster - Full Run - YouTube - video
W3W: ///skylark.winemaking.doddle
P = C / (1 - M) = 50 / (1 - 0.3) = 50 / 0.7 = 71.43
M = (P - C) / P = (50 - 71.43) / 71.43 = 0.3
Or lastly:
C = P * (1 - M) = 71.43 * (1 - 0.3) = 71.443 * 0.7
= 50
Crafty way to create a temporary table (view) with some rows in it:
CREATE VIEW Xyz AS
SELECT 'A' AS id
UNION ALL
SELECT 'B' AS id
UNION ALL
SELECT 'C' AS id
UNION ALL
SELECT 'D' AS id;
Creates a table:
Xyz |
id |
A |
B |
C |
D |
Maybe I am just looking at a bad example project that does not use the tool correclty? But I can't help but think: what does this tool do for my build environment that a decent build document and a set of human friendly tools (an IDE?) don't.
Can I more easily set up new team members with a productive build environment? Is it faster than copying a Virtual PC image and clicking "start"?
But (B) just introduces more maintenance? Worse still it makes maintenance harder while developers pick through unnecessary "proxy" and "interface classes".
Why not simply write an app that uses a subset of (A) directly?
To me it smacks of a work avoidance technique. Rather than think about how to address a customers problems, or stick your neck out and make a bet on a library... it's easier to write an abstraction layer, which will allegedly "make it easier" to write the business app one day in the future.