Already a member? Log in

Sign up with your...

or

Sign Up with your email address

Add Tags

Duplicate Tags

Rename Tags

Share This URL With Others!

Save Link

Sign in

Sign Up with your email address

Sign up

By clicking the button, you agree to the Terms & Conditions.

Forgot Password?

Please enter your username below and press the send button.
A password reset link will be sent to you.

If you are unable to access the email address originally associated with your Delicious account, we recommend creating a new account.

Links 1 through 10 of 3250 Goetz's Bookmarks

"It's [MySQL Query Cache] case­-sensitive, whitespace-­sensitive"; "There's no parsing, optimizing, etc etc"; "Each SELECT has extra overhead"; "Each UPDATE, INSERT, etc has extra overhead"; "If Qcache_lowmem_prunes is increasing and you have lots of free memory, suspect fragmentation"; "avoid fragmentation with the block size: try setting it close to the average result size – (query_cache_size – Qcache_free_memory) / Qcache_queries_in_cache"; "Defragmenting: Use FLUSH QUERY CACHE - It doesn't flush the cache, it compacts it. It locks the whole cache"; "InnoDB works with the query cache – for some value of “works”"; "Optimizations: Don't make it too big or it stalls—256 MB is plenty. Consider disabling it entirely."

Share It With Others!

"In other words, we want to know how many frogs (vulnerabilities) there are in some pond (a software product). One might then ask whether either or both of the capture-recapture and removal-capture techniques might help us answer Schneier’s and Rescorla’s challenge, the challenge of picking a policy direction based on whether vulnerabilities are sparse or dense. Do we want a policy that skips patching in favor of rolling software fast enough to make it a moving target? [5] If we decide to keep patching, are we better off disclosing or keeping the repairs secret?"; " If you take a patch as a marker for a previously undiscovered flaw, then the rate at which patches issue is a removal-capture process. Were that process to maintain a relatively constant hum, then it might imply that software flaws are indeed dense—too dense to diminish with removals."

Share It With Others!

"Leaders know they should engage with employees, especially via digital and social channels. But they don’t [...]"; "[...] the simple act of listening—and letting colleagues know that they are being heard—is the first crucial step to meaningful collaboration."; "As a leader, the key is to start collecting and sharing in order to shape specific outcomes. While it’s true that no one really cares what you had for lunch, they are keenly interested in what you discussed over lunch."; "The tools themselves matter less than the ability of leaders to describe the intent and purpose of the tools."

Share It With Others!

"Being a full stack employee isn’t necessarily easier or harder; it’s different."; "Being full stack is an exercise in shifting between opposite poles. While there’s often less support for individual work and a greater expectation of self-sufficiency (i.e. setting their own hours, using their own devices for work, etc), they’re also expected to collaborate and work in groups effectively."

Share It With Others!

"analyzing even five-star reviews to understand the underlying sentiment and find holes they can fix. Looking for issues in perfect reviews may seem counterintuitive, but doing so has revealed valuable insight into customer feedback."

Share It With Others!

"Pixar story artist Emma Coats has tweeted a series of “story basics” over the past month and a half — guidelines that she learned from her more senior colleagues on how to create appealing stories" - very interesting read for every writer, even if you don't really write stories like Pixar films.

Share It With Others!

German article about an interesting concept: collaborative content creation - one week to create a book together, inspired by Bar Camps and agile software development: "Ein Booksprint ist eine Methode zum gemeinschaftlichen Verfassen von Handbüchern, entwickelt von Tomas Krag und Adam Hyde."; "Eine Gruppe von 5-10 Experten setzt sich in einem Raum zusammen und verfasst gemeinsam ein Buch – online, innerhalb von 2-5 Tagen mithilfe einer Web-Plattform. Die Bücher, die auf diese Weise entstehen, haben qualitativ hochwertige Inhalte und sind sofort am Ende des Sprints in gedruckter Form (Print-on-Demand) und in verschiedenen E-Book-Formaten verfügbar."

Share It With Others!

"The discovery of the collection of koans known as the Rootless Root, apparently preserved for decades in the dry upper air of the Western Mountains, has ignited great controversy in scholarly circles. Are these authentic documents shedding new light on the teaching of the early Unix patriarchs? Or are they clever pastiches from a later age, commanding the authority of semi-mythical figures such as the Patriarchs Thompson, Ritchie and McIlroy for doctrines which evolved closer to our own era?" - Quite funny and interesting, if you're somewhat interested in programming. For the record, Eric S. Raymond is also involved in the Jargon File...

Share It With Others!

"Livehoods — A new way to understand a city
using social media."; "Livehoods offer a new way to conceptualize the dynamics, structure, and character of a city by analyzing the social media its residents generate. By looking at people's checkin patterns at places across the city, we create a mapping of the different dynamic areas that comprise it. Each Livehood tells a different story of the people and places that shape it." - sounds like an interesting project.

Share It With Others!

"This is a directory of reusable tools for the open web community. The content has outgrown the domain name." - Interesting list, probably helpful when you're working on a new project and wonder if some tool could help you with something...

Share It With Others!