lebski88
Joined 19 years ago
Joined 19 years ago
Anyway, my point is that if I didn't live just around the corner, I would never have known it existed. I'd imagine there are similar setups around the country. You do need quite a big space and a runway is presumably helpful, so it probably makes sense for them to be collectively run.
That's a shockingly short amount of time for smoking. For me, after a few weeks I'd say some of the worst cravings had passed. But for a good year or two afterwards they'd occasionally come back, albeit briefly. I quit about 15 years ago, but given the right situation I can still feel it.
I'm quite enjoying the quiet. There's still video or email in an emergency.
* No one was in love with Java. It was fine but we were doing the whole spring style super verbose Java and it felt like a lot of ceremony to get anything done. There had been an experiment with Scala previously but that hadn't taken off.
* We had a service-oriented architecture which meant we could try Clojure out on a few new services and see how it felt.
We ended up going from 2 services to moving the whole org over really quickly. A lot of excitement built up and people didn't want to be left out. At the end of things only 2 people decided they didn't want to learn Clojure.
A few other things we did:
* Bought loads of books and left them lying around
* Started a Clojure club where we booked an hour a week and did some exercises in Clojure
* Had a big meeting where we convinced everyone that Clojure was worth an experiment
* Brought in 3 consultants to do some Clojure training for everyone
* Probably strong armed everyone into watching simple made easy - it helped that lots of people had already seen it live that year
There are a few talks about it floating around although they are very very old now and I'm not sure they're worth the time!
https://whostolebenfrog.github.io/clojure,/deployments,/clou...
One of the main effects of the sugar tax was that so many manufacturers just changed their recipe to avoid having to raise prices. So the option to pay more in the shop isn't even there. Coke and Pepsi are the notable counter examples.
There are a lot of arguments about query hints etc becoming stale and the performance changing as the table grows but I'm less worried about that - it would be a gradual degradation of performance. What worries me is that the table stats cross a threshold at 3am and suddenly the query planner chooses something crazy.
I've also wondered if an approach of trying a bunch of query plans could be fun. Get it to pick the top 10 possibilities and just run them all and record stats on which was fastest. Doubly so if it ever decides to run a seq scan where there is an index. Please. Just try the index! That said yesterday I was definitely at the point where I just wanted to express the exact query plan myself.
Only azure supports Citus as far as I know.
What a strange comment for them to make. Why wouldn't I expect CC to work well with those languages? What languages would I associated it with? Python and Javascript?