Oakland Dollars for Sunday Papers. Montclair Farmer's Market.
... was my response to Julie's oncologist giving us the bad news that she has breast cancer that has spread to her bone marrow. It certainly explains the bleeding, the bruising and the anemia which required multiple transfusions.
No treatment plan yet (tests, and more tests..), but it looks like my future will involve lots of WFH where H == hospital. I'm going to do whatever I can to improve the 1-2 year survival time odds.
I'm interested in hearing from you if:
- You have dealt with Kaiser's Cancer care and treatment. tips please!
- You have 2nd opinion referrals.
- You have a Caregiver story -- how did it impact you and your career?
Thanks again to everyone that's offered support and flexibility. Googlers are the best, most supportive people in the whole world. Proud to work for this company and with you all.
I don't have my #firstgoogleremail - but I do have the email that started the ball rolling towards my eventual employment. Seven weeks later I started at Google.
*Date*: 8/7/10
*Subject*: Interesting moves
_I'm intrigued the recent social moves coming out of Google and wonder if there's some part for me in all of this, either from the inside or from the outside._
_Truth be told, I'm not getting my "change the internet for the better" satisfaction at the moment even with the independent time I spend on Opensocial/Shindig/OAuth._
_Would you like to have a short chat in the next week or two?_
*Thirteen Ways To Save Orkut* February 2004
_With its integrated personal, social, and business functions, Orkut has an opportunity to outstrip it competitors—but only if its creators make smart choices that support the genuine needs of real people._
http://www.digital-web.com/articles/thirteen_ways_to_save_orkut/
*You might be a Googler if...*
You start writing a postmortem when you arrive at the ER.
So. Many. _Areas for Improvement_
#protip if you're going to need dental/medical treatment do it in an area where lots of old rich people live. #medicaltourism
Note: All is well now, we extended our stay and Julie is recovering.
A long, well written retrospective by the former Salon _Ask the Pilot_ columnist Patrick Smith.
h/t Rohit Khare
Some feedback on Collections after actually using them for realzies:
- The aspect ratio of the cover image is really hard to deal with. You can't crop regular images easily and you can't letterbox easily.
- I'd like to make a collection as 'Draft' so I can get it looking nice before I send it out to the world.
- I'd love to see a 'People mentioned this collection' in the sidebar. [and other aggregates, like places, hashtags, maybe a word cloud?]
- I wish I could back-date things. Or at least allow for manual ordering.
- What about Pinned/Hero Post for a Collection?
- Will public collections have non-obfuscated URLs?
- Do we filter these oddball urls for naughty words?
*Ursquake* March 2010
@113057531893316771155 states
_The social web is revolutionizing the world, and this is our chance to create what will be the most useful and most used set of socially connected products in the world, with the best user controls on privacy and data portability. We have an incredibly strong starting position. It’s rare that we’re being given an opportunity to have such a big impact in such a short time, so lets seize it!_
Not sure where to get feedback for this so tossing into the ether...
I've been getting many PM interviews for Technical Hat; I wonder what others think of this line of questioning?
- We have a SMB with 1000 devices and 20 servers
- These machines generate log files (1st question, does candidate know what a log file is?)
- Your product needs to meet the needs of the following users
- Sysadmins need to be able to diagnose problems, do postmortems.
- Auditors need to enforce rules on system usage
- A security team wants to detect intrusions, malware etc.
I then ask the candidate to ask clarifying questions and try to get them to give me any/all of the following through progressive probing:
- Min viable features of the product
- Do they suggest graphs? notifications? email alerts?
- What about user provisioning? Admin features?
- What kind of UI? Web? Mobile? Command line?
- Search?
- A high level technical design showing how the we get from Logs -> UI
- Push vs pull?
- Where/when does parsing happen?
- Technical
- How do you store the data? How do you transform it? Batch?
- What database? How many QPS?
- Redundancy? Failover?
- On site / off site?
- Insights
- Does the candidate understand privacy/security concerns? (Mention wipeout, retention for the auditor use case)
So far I've gotten some decent responses, but most fall into the run reports on files and store those.
For the good candidates we are able to progress to phase II where we design for a multinational fortune 500 scenario.
So WDYT? Good question?
PMs? How do you think you'd do on my question?
Enjoying all the historical info I'm finding on oaklandwiki.org
Found my way there after researching the Sacramento Northern Railway...
It's so fast and smooth you might think you're using a native App.
Originally shared by Danielle Buckley
Today we’re excited to announce the new and improved Google+ experience for mobile web. We focused on making everything faster, more beautiful, and more intuitive. To check out all the new updates, visit plus.google.com on your phone or tablet’s browser.
As always, we’d love to hear what you think!
Was discussing potential for location-based sharing and remembered this gem. Despite all the sucky things happening I'm still excited about what's possible in the future.
Setting up a Personal Weather Station was easier than I thought and pretty fun. I can now stare at graphs at work and at home.
http://www.wunderground.com/personal-weather-station/dashboard?ID=KCAOAKLA79
My first dev job in 1991 required that I do at least 4h of phone support and 4h of walk-in support a week. Feeling user pain and answering the same dumb questions over and over made me a better developer and also led to a bunch of innovation:
- Mainframe Mail Woes? Develop SLIP/PopMail, give away on floppy
- Xmodem problems? Add hqx attachment support.
- Need access to Apple's techinfo CD? Get it via Gopher.
- Indepth howtos? Publish newsletters like you see below.
You don't have to answer the phone to help people today. You can engage externally on mailing lists, on G+ and more. Just remember to follow the guidelines in http://go/u2u
A fascinating listen from my morning drive. I imagine I'll now notice the ambient sound more after being made aware of this.
About a year ago I did a one-day seminar called _Managing Through Change_. It was actually pretty good and helped me understand how the human brain treats stressful transitions.
Sadly the course isn't offered, but there is some pretty decent self-instruction available here:
https://grow.googleplex.com/opportunity/site/navigatechange/
https://login.corp.google.com/request?s=grow.googleplex.com:443/uberproxy/&d=https://grow.google...
After today I think I should get this..
domain name appears to be available too..
Hi Paul,
Long time no see! Hope all is well with you. Have been trying to reach someone in engineering at Google to see if there might be interest in acquiring my company. Would be cool to catch up sometime, please let me know what you think!
Here's some more info regarding our company / technology:
....
XXXXX is fully bootstrapped, we have no debt and no additional shareholders (just the two of us). The company was recently incorporated, so a transaction would be straightforward. We are both versatile generalists in our respective fields with lots of experience innovating hands-on as well as managing teams. And we’d love an opportunity to demo our tech with anyone who’s interested!
Someday ...
Originally shared by Singularity Utopia
It is possible to do #responsivewebdesign with a G+ badge? I want the badge large for big screens so I set the width to 450 but it doesn't resize to fit like all my other elements, here in the image you can see the badge when zoomed-in is off the screen. Can you allow (make happen, implement) a 100% width instead of 450?
Here it is live: http://singularity-2045.org/
Replacing static HashSet<String> with Java 7 string switch?
Has anyone investigated whether Java 7 switch is more memory efficient than HashSet<String> or ImmutableSet<String>? I think it might be. Read on....
I ask because HashSet is one of the more bloated java collection classes. It uses 32 bytes for each used entry + an array for the capacity. For example the follow
ing HashSet uses 128 bytes (2*32 + 16 * 4):
private static final HashSet<String> FOO = new HashSet<>();
foo.add("a")
shpub note --category=googplus --syndication=https://plus.google.com/107786897865850743842/posts/VPYQiMunRRY --published="Mon Dec 29 12:22:44 PM PST 2014" --name="" - <<EOF
Replacing static HashSet<String> with Java 7 string switch?
Has anyone investigated whether Java 7 switch is more memory efficient than HashSet<String> or ImmutableSet<String>? I think it might be. Read on....
I ask because HashSet is one of the more bloated java collection classes. It uses 32 bytes for each used entry + an array for the capacity. For example the follow
ing HashSet uses 128 bytes (2*32 + 16 * 4):
private static final HashSet<String> FOO = new HashSet<>();
foo.add("a")
foo.add("b");
boolean isFoo(String s) { return FOO.contains(s);}
We can replace that with:
boolean isFoo(String s) {
switch (s) {
case "a":
case "b":
return true;
default:
return false;
}
}
Java 7 transforms this code into something like this:
switch (s.hashCode()) {
case -1234:
return s.equals("a");
case -55999:
return s.equals("b");
default:
return false;
}
Which maps to a tableswitch or lookupswitch. Squinting it appears that you'd need the following for each entry:
tableswitch:
per-entry: hashcode + result value (8 bytes)
equals test: 4 opcodes (16 bytes)
So it would appear that you have 24bytes/entry.
Performance would be limited by the JVM/Dalvik/Art implementation of tableswitch which can be O(n)
Also obligatory reference to:
http://blog.jamesdbloom.com/JavaCodeToByteCode_PartOne.html
The Current's Christmas music was kind of a downer...
A little rain and the whole transportation system seizes up. Plus there's this from SFGate
h/t John Hjelmstad
Was pondering how James Kirk would share on a social network and remembered that he always said Captain's Log, Stardate... -- but then I found this.
Kevin Sorbo and "the source codes" in Silicon Valley, CA.
Farewell.
After a 4 month battle against cancer we made that hard yet logical decision to end the fight. Tommy didn't visit Google often, but he always enjoyed the attention, laying in the grass, and walking the trails nearby.
Thanks to everyone that put up with my last minute cancellations for vet visits and the extra time I spent tending to his needs in his final months.
[A]lmost all (92%) of the catastrophic system failures are the result of incorrect handling of non-fatal errors explicitly signaled in software.
Check out the postmortems linked in the references.
Heads up webmasters -- please consider updating your javascript snippets.
Originally shared by Ilya Grigorik
All Google+ widgets have been updated to use the script[async + defer] pattern! E.g. +1 button docs: http://bit.ly/YHoj96
What's the benefit? Loading widgets via script[async+defer] does not block the document parser (see [1]), and allows the preload scanner to discover the script resource and initiate an earlier fetch (see [2]). Net outcome, both your page and the widget load faster! Have a G+ widget on your page? Check out the docs for guidance on how to update your snippets.
Kudos to the G+ team for taking the lead on this! Hope to see more widget providers adopt the same pattern.
[1] https://developers.google.com/web/fundamentals/performance/critical-rendering-path/adding-interactiv...
[2] https://www.igvita.com/2014/05/20/script-injected-async-scripts-considered-harmful/
The next time you ignore a few deadline exceededs ask yourself: Where are the people affected on the participation curve. Often they're the ones with thousands of blocked people, tons of posts and +1s and *your most valuable users*. Call 'em whales if you like, but do not ignore them.
Reported the dumped tires. You can vote it up if you want.
I hope you can update Mark with authorship changes the same way you treat Search Engine Land.... He's going to lose some major credibility.
Originally shared by Mark Traphagen
Interview with Me About Google Authorship
Andre Alpar of OMReport.de interviewed me last June at SMX Advanced in Seattle about Google Authorship and the changes we had seen from the beginning of the year up to that point.
Please note that this interview was conducted before Google removed all author photos from regular search, but Authorship still works, and I believe the principles I discuss here are still valid.
John Hjelmstad / Jonathan Beri - same deal as sign in button... let's incorporate it...
Originally shared by Gerwin Sturm
As you might have noticed I invested quite some time in Polymer recently. What I like about web components is that they make a lot of things a lot easier, except...
Normally adding a +1 button (or any other Google+ plugin) to a website is just about the easiest thing you can do.
1. Take the code snippet from the docs, e.g. https://developers.google.com/+/web/+1button/
2. Paste it in your code at the appropriate place.
3. Done.
Unfortunately the gapi JS library doesn't like to work with the Shadow DOM. Even if you pass in a direct reference to an element inside of your element it won't work.
The (https://github.com/GoogleWebComponents/google-hangout-button/) works around this issue by adding an element to the light DOM, telling gapi to render the button there, then snatching the element and sending it to the shadow realm dom.
Since there are a lot more widgets to choose from, I took this idea and started by creating a generic element that takes `type` and `data` as attributes to render the appropriate plugin, using the same idea as the hangout-button.
So for the default +1 button you could just use
Or for a profile badge you would use
<google-plugin type='person' data='{"href": "https://plus.google.com/+GerwinSturm"}'>
From there I started to create specific elements, that have the relevant attributes for each plugin.
For now there are only two but others are easy to add:
(the profile attribute will be used to build the href attribute needed by the profile widget)
The plugins still aren't really happy inside of the shadow dom, displaying some errors in the console, and not all interaction seems to be working correctly.
I have some other ideas I will test to improve this, but maybe the gapi team will eventually support Shadow DOM properly ;)
For now these elements work better than not working at all :)
Source code: https://github.com/Scarygami/google-plugins
Docs: http://scarygami.github.io/google-plugins/components/google-plugins/
Demo: http://scarygami.github.io/google-plugins/components/google-plugins/demo.html
A gem of a performance.
I've found that a search for {BANDNAME} {YEAR} live where year is early on yields some amazing finds. That's how I found this superb performance.
Read this behind the scenes article about Project Boswell with Brett Lider and Joseph Smarr who toiled long and hard to deliver an awesome feature.
This article also showcases how sometimes you have to throw away the first few concepts before you get it right. Happy that I had a small part at the beginning of the project and props to the many folks that invested time and effort to get this out the door.
Originally shared by Tim O'Reilly
Fundraiser for Libby Schaaf for Mayor of Oakland at the BlueSprout industrial co working space. Oakland is a Maker city. Libby will be a Maker - friendly mayor. But she is most of all a doer who will help city government to work for its citizens!
This crazy "gothic" house near my home in Oakland can be yours for $869k.
Bonus: it's an Ingress portal. Not sure if that'll be in the disclosures...
Photo tour here: