Emre Sokullu

• MySQL Cluster is not the solution; consider it as a different database and don't forget that it's not very efficient, so ends up costing you much
• Use Memcached
• Your memcache machine should be close to your application/web servers, not the database
  
• Sharding is hard. There are things you can do before sharding. Replicate as much as you need, so that you can split read and write operations. One machine dedicated to write only.
• • Then the most logical thing to do for sharding is horizontal sharding; which means host different tables in different machines. But this is needed only in extreme cases, as you grow like crazy, like grou.ps
  • Before that, you can maximize your write capabilities, you can get a beefy server with 128MB of ram, 4x Hexacore processors. Note that you'll need to use xtradb on such a configuration because regular mysql setup does not scale well to more than 4 cores, instabilities do occur.
  • And even before that, try optimizing your code. 
• You can optimize your queries by enabling logging of the slow queries
  
• For a 16GB of ram, 400 is the maximum number of connections you need to have on the machine.
• If SHOW PROCESSLIST; displays too many Sleeping connections, no problem, don't worry about them.
• You don't recover from table locks with myisam, auto_increment still requires table lock
• Use maatkit tools. mk_audit recommended as a good start
• If you are replicating, you'll need mk_slave_restart at some point, but don't forget that, it's dangerous, can create inconsistencies
• use mk-query-digest to collect information about the incoming mysql queries; then you can optimize them using the EXPLAIN command - tcpdump is a microsecond level alternative for the very same job
  
• take off unused databases and tables
• for a fast updating environment, cronjob mk-query-digest and mk-duplicate-key-checker
• Consider a dual master setup; use mmm (1.x branch is recommended as of this writing) or flipper - good 
• hot backup strategies: lvm_backup, mk-parallel-dump, innobackup,
• do not use set where you can use enum; set is for options that can be chosed more than once
• vmstat 5 5 to see the status of your disk
• even though you don't use myisam, the minimum key_buffer size should be 32MB
• InfoBright is good for analytics tables
• XFS is good as the underlying filesystem of innodb systems.

• Hidayet Dogan, one of the best Turkish PHP programmers I've seen so far (based on his resume and projects) dreams of a Google like office environment, full of gadgets and big LCD displays.
• Eren Yagdiran, whose diverse array of interests can be found on his personal blog, says it's all about money.

Those three things--autonomy, complexity, and a connection between effort and reward--are, most people agree, the three qualities that work has to have if it is to be satisfying.

Hard work is a prison sentence only if it does not have meaning. Once it does, it becomes the kind of thing that makes you grab your wife around the waist and dance a jig

• Autonomy: Our management type can be considered democracy under meritrocratic feudalism. There's a loose hierarchy which gives its nodes the freedom to show their creativity without the boundaries of bureaucracy, and the chance to have your own team if you can prove yourself to your "lord". The hierarchy is not fixed, it's dynamic based on your merits.
  
• Complexity: What we're doing here is literally social operating system. If you think it's just a content management system or something like that (and if you're qualified enough) you're welcome to our office to see what kind of things and what kind of an architecture that we're working. I don't claim it's rocket sciences, but it's pretty close.
  
• Connection between Effort and Reward: GROU.PS is a global venture with chances of being acquired or going IPO. And besides the fixed salary, we are committed to give a generous amount of sweat equity and/or stock options to our employees according to their commitment and role in the team.
  

• As you browse through the pages, the screen flicks, and it temporarily displays randomly located black spots - which results in poor user experience.
• There could be a separate button for Kindle Store
• Buttons seem to be low quality
• Packaging was not as good as I was expecting - my anticipation was a true Apple experience, but it was far from that.
• I miss the multi-touch screen of iPhone, it could make note-taking a breeze - which is, I think, a natural component of our reading experience.
• Poor blog reading machine, because no images, no Flash components - which are crucial parts of blogs.
• Can't delete a book that you've purchased (or there's no easy way)
• Chaging pages is slow, once you lose the page, it's so difficult to find wherever you were at