 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> (It's not like you can just Google "weird changes to Google search page".)
Did you try it?
--
Darren New, San Diego CA, USA (PST)
Ada - the programming language trying to avoid
you literally shooting yourself in the foot.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> (It's not like you can just Google "weird changes to Google search
>> page".)
>
> Did you try it?
No. Let me go try it now...
...yes, as I expected, it returns nothing of use.
However, performing a manual search of the Official Google Blog (i.e.,
scrolling through the page until you see anything relevant-looking)
gives me this:
http://googleblog.blogspot.com/2010/05/google-design-turned-up-notch.html
http://googleblog.blogspot.com/2010/05/spring-metamorphosis-googles-new-look.html
That covers the update that happened in the last few days. After another
15 minutes or so of manual searching, I found this:
http://googleblog.blogspot.com/2009/12/now-you-see-it-now-you-dont.html
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Orchid XP v8 wrote:
> However, performing a manual search of the Official Google Blog (i.e.,
> scrolling through the page until you see anything relevant-looking)
> gives me this:
>
> http://googleblog.blogspot.com/2010/05/google-design-turned-up-notch.html
> http://googleblog.blogspot.com/2010/05/spring-metamorphosis-googles-new-look.html
>
>
> That covers the update that happened in the last few days. After another
> 15 minutes or so of manual searching, I found this:
>
> http://googleblog.blogspot.com/2009/12/now-you-see-it-now-you-dont.html
Apparently there's a kind of history page:
http://www.google.com/corporate/timeline/
I also found the page for the previous change - when they made the
search bar bigger:
http://googleblog.blogspot.com/2009/09/now-s-u-p-e-r-sized.html
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Invisible escreveu:
> In the last day or so, the Google logo seems to have changed [quite
> apart from the almost daily guest logos], and the search box has got
> larger. I wonder why?
you only *noticed* it the last day or so, but it's been there for quite
a while already (months). At least the big official one rather than one
of the "nationalized" versions for each country...
I thought the change was merely cosmetic but now that you brought it to
attention, I also notice a virtual keyboard for security freaks next to
the search entry. Can't be bad...
--
a game sig: http://tinyurl.com/d3rxz9
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> In fact, reading further, it seems they have several blogs - none of
>> which are related to what I'm looking at...
>
> You're not talking about this are you?
> http://googleblog.blogspot.com/2010/05/spring-metamorphosis-googles-new-look.html
Yes, I eventually found that and several other related posts, by manual
searching (i.e., using my eyeballs to inspect every blog post for the
past X weeks).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I was looking at some slides from a presentation about testing and
> developer productivity. One slide was a photograph of an actual whiteboard
> at Google HQ, listing the things that had reduced productivity on a
> particular day:
Sounds an interesting task, I should suggest people here do that. But one
of the problems here I see is that a lot of people count the "unproductive"
work as productive. For example if they spend a day trying to fix a problem
with an incorrectly designed thing, they count that as a good productive
day's work. They don't realise their job is to design things correctly, and
not to design things incorrectly and then fix them.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
> Sounds an interesting task, I should suggest people here do that. But
> one of the problems here I see is that a lot of people count the
> "unproductive" work as productive.
Heh, gotta love that.
> For example if they spend a day
> trying to fix a problem with an incorrectly designed thing, they count
> that as a good productive day's work. They don't realise their job is
> to design things correctly, and not to design things incorrectly and
> then fix them.
Yeah, that *does* sound like poor engineering practise...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Yeah, that *does* sound like poor engineering practise...
Other favourites are spending a day designing something when someone else
has already done it, designing something from scratch because you don't know
how to use the software well enough to modify and existing design, or
designing something when you know the spec isn't fixed, then when the spec
is fixed saying you don't have enough time to change the design... It's all
fun and games here :-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
> Other favourites are spending a day designing something when someone
> else has already done it
Sounds like either poor communication, or somebody with too much time on
their hands.
> designing something from scratch because you
> don't know how to use the software well enough to modify an existing
> design
That's the kind of thing I'd do.
> or designing something when you know the spec isn't fixed, then
> when the spec is fixed saying you don't have enough time to change the
> design...
I suppose some people might argue that's a necessary evil when the
customer can't make up their mind what they want and yet demand that it
arrives on time. But I don't know.
> It's all fun and games here :-)
And I thought it was only my screwy company that does stuff like this...
Ooo, how about this one: Designing something when you have no spec at
all, and then writing a spec to match the thing you just designed. You
guys ever do that one?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Other favourites are spending a day designing something when someone else
>> has already done it
>
> Sounds like either poor communication, or somebody with too much time on
> their hands.
The former, I blame it on the way the departments are set up in the company,
it's like they are all in competition with each other, so information
doesn't get shared very well. It also doesn't help that everyone thinks
what they are doing is highly confidential and can't even be shared with
another department...
> I suppose some people might argue that's a necessary evil when the
> customer can't make up their mind what they want and yet demand that it
> arrives on time. But I don't know.
Usually we give the customer a design freeze date in order for the first
deliveries to meet their deadline. This is fine until the customer informs
us of a change a week before the freeze, then we have to tell them that
actually we don't have time now to make that change - things get a bit messy
then.
> Ooo, how about this one: Designing something when you have no spec at all,
> and then writing a spec to match the thing you just designed. You guys
> ever do that one?
Not really, you need to have at least a rough idea of the performance
required before starting design work. Of course the detail level of spec
varies from customer to customer, but the basics are always there to start
the design work.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
