Curt Doolittle

Source: Original Site Post

  • State Sponsored Hyper-Consumption of Goods, Services, Info, and Virtue Signals

    —“What we like or want may not be good for us.” — Curt Doolittle

    Context of the original quote was that we have used a variety of techniques to generate hyper-consumption and especially conspicuous hyper consumption, and even worse, conspicuous hyper consumption of virtue signals. In other words, we may like hyper consumption but that does not mean it is good for us, any more than hyper-consumption of the pleasure response by drugs is, or hyper-consumption of sedation by alcohol, or hyper-consumption of calming by nicotine, or anything else in any similar spectrum. So, yes, “all things in moderation” for the individual but this isn’t enforceable if the entirety of the political economy is generating hyper-consumption for hyper-taxation, and hyper-redistribution. The state should not engage in the provision of the incentive to hyper-consume. This only benefits the financial sector. Instead, just redistribute liquidity in response to shock and sags directly to the consumer and cause business to fight over it.

  • State Sponsored Hyper-Consumption of Goods, Services, Info, and Virtue Signals

    —“What we like or want may not be good for us.” — Curt Doolittle

    Context of the original quote was that we have used a variety of techniques to generate hyper-consumption and especially conspicuous hyper consumption, and even worse, conspicuous hyper consumption of virtue signals. In other words, we may like hyper consumption but that does not mean it is good for us, any more than hyper-consumption of the pleasure response by drugs is, or hyper-consumption of sedation by alcohol, or hyper-consumption of calming by nicotine, or anything else in any similar spectrum. So, yes, “all things in moderation” for the individual but this isn’t enforceable if the entirety of the political economy is generating hyper-consumption for hyper-taxation, and hyper-redistribution. The state should not engage in the provision of the incentive to hyper-consume. This only benefits the financial sector. Instead, just redistribute liquidity in response to shock and sags directly to the consumer and cause business to fight over it.

  • State Sponsored Hyperconsumption of Goods, Services, Info, and Virtue Signals

    State Sponsored Hyperconsumption of Goods, Services, Info, and Virtue Signals https://t.co/wZ0Sb47dGn

  • State Sponsored Hyperconsumption of Goods, Services, Info, and Virtue Signals

    —“What we like or want may not be good for us.” –Curt Doolittle

    Context of the original quote was that we have used a variety of techniques to generate hyper-consumption and especially conspicuous hyper consumption, and even worse, conspicuous hyper consumption of virtue signals. In other words, we may like hyper consumption but that does not mean it is good for us, any more than hyperconsumption of the pleasure response by drugs is, or hyperconsumption of sedation by alcohol, or hyperconsumption of calming by nicotine, or anything else in any similar spectrum. So, yes, “all things in moderation” for the individual but this isn’t enforceable if the entirety of the political economy is generating hyperconsumption for hyper-taxation, and hyper-redistribution. The state should not engage in the provision of the incentive to hyperconsume. This only benefits the financial sector. Instead, just redistribute liquidity in response to shock and sags directly to the consumer and cause business to fight over it.

  • State Sponsored Hyperconsumption of Goods, Services, Info, and Virtue Signals

    —“What we like or want may not be good for us.” –Curt Doolittle

    Context of the original quote was that we have used a variety of techniques to generate hyper-consumption and especially conspicuous hyper consumption, and even worse, conspicuous hyper consumption of virtue signals. In other words, we may like hyper consumption but that does not mean it is good for us, any more than hyperconsumption of the pleasure response by drugs is, or hyperconsumption of sedation by alcohol, or hyperconsumption of calming by nicotine, or anything else in any similar spectrum. So, yes, “all things in moderation” for the individual but this isn’t enforceable if the entirety of the political economy is generating hyperconsumption for hyper-taxation, and hyper-redistribution. The state should not engage in the provision of the incentive to hyperconsume. This only benefits the financial sector. Instead, just redistribute liquidity in response to shock and sags directly to the consumer and cause business to fight over it.

  • Q: Biggest Programming Mistakes?

    Q: Biggest Programming Mistakes? https://t.co/3vPtRzb9sp

  • Q: Biggest Programming Mistakes?

    Q: Biggest programming mistakes? (from elsewhere) All my big mistakes are the same, and I remember them. I keep working when I’m too tired to keep working: So, I wrote more functionality than I needed to; I forget that I wrote something and wrote it again; I forget that I wrote it over there and wrote it here. I forgot that I did it that way and so did it this way, and now I have to fix one or the other. I made only one architectural mistake with a new product because I rushed with it. The rest are all the same. Tired = stupid. I keep lots of notes, I plan my work, I use diagrams to design it. I usually do databases for rules, then services, then ui designs; Then the class architecture. I pseudocode the work, I write code for readability first; I document as I go; I (mostly) write test then code, the reason I’m slower I think I should be is that I test more than I should, especially UI functionality, and so I revise too much. I refactor a lot. and sometimes I shouldn’t. I should focus on functionality coverage so that I have a better understanding of how different services interact in practice. Most recent mistakes that sit with me is the message bag in Oversing, where I’d replaced one technique with another and then forgot I’d done so until … oops. The other is writing one set of panels one week using one method of data propagation, and coming back the next week and writing another set of panels with a slightly different method of data propagation, when I should have used a different method of data propagation. My general strategy is to make it work, make it work together, make it durable, then make it elegant. I stopped writing code myself because there are people who are faster and better and my core strength is user interface design, business rules, and data structures, and not wiring everything together. And the reason is that with all the visual cues I do better than I do in code editors without them. ie: as I usually complain my weakness is short term memory. I remember almost everything. but that’s not the same as working memory. But in general, tired = stupid. Don’t write code tired. Don’t send emails tired (or angry)

  • Q: Biggest Programming Mistakes?

    Q: Biggest programming mistakes? (from elsewhere) All my big mistakes are the same, and I remember them. I keep working when I’m too tired to keep working: So, I wrote more functionality than I needed to; I forget that I wrote something and wrote it again; I forget that I wrote it over there and wrote it here. I forgot that I did it that way and so did it this way, and now I have to fix one or the other. I made only one architectural mistake with a new product because I rushed with it. The rest are all the same. Tired = stupid. I keep lots of notes, I plan my work, I use diagrams to design it. I usually do databases for rules, then services, then ui designs; Then the class architecture. I pseudocode the work, I write code for readability first; I document as I go; I (mostly) write test then code, the reason I’m slower I think I should be is that I test more than I should, especially UI functionality, and so I revise too much. I refactor a lot. and sometimes I shouldn’t. I should focus on functionality coverage so that I have a better understanding of how different services interact in practice. Most recent mistakes that sit with me is the message bag in Oversing, where I’d replaced one technique with another and then forgot I’d done so until … oops. The other is writing one set of panels one week using one method of data propagation, and coming back the next week and writing another set of panels with a slightly different method of data propagation, when I should have used a different method of data propagation. My general strategy is to make it work, make it work together, make it durable, then make it elegant. I stopped writing code myself because there are people who are faster and better and my core strength is user interface design, business rules, and data structures, and not wiring everything together. And the reason is that with all the visual cues I do better than I do in code editors without them. ie: as I usually complain my weakness is short term memory. I remember almost everything. but that’s not the same as working memory. But in general, tired = stupid. Don’t write code tired. Don’t send emails tired (or angry)

  • “The White Law” (Lex Europae)

    “The White Law” (Lex Europae) https://t.co/z25G1Xndhx

  • Eugenics in P-Law

    Eugenics in P-Law https://t.co/hgJ4HCcsfD