524 karma · joined February 23, 2009
Obviously, this guy proves that it goes far and it applies to a website such as stackoverflow as well. When I came to stackoverflow 1 year ago I had an amazingly streamlined experience. But of course, I had previous experience from using the internet. I expected that
* the site search box to be in the upper right corner, and use the verb "search" or "find" * the login/register links to be in the same upper right corner * most publishing tools have a permalink to be found in relation to posts on the page * 'flag' is likely related to fighting spam, a problem most open forums have * 'tagging' is that which was made popular in this whole web 2.0 craze * "Ask Question" would mean something involving "asking" and "a question" * an up/down arrow, above and under a number would increment or decrement that number * it is beneficial to place a mouse pointer over items to see if there is clarifying mouse-over text, but with little fear I tend to push buttons to see what happens as well
Complaining about ads by guessing they're not effective, or that the careers link is just hidden ads also seem quite malicious. They got to earn money, and having read jeff's/joel's blog entries on the success of ads on stackoverflow I am very sure that they've been trying out different things to see what works.
It is difficult to criticize these remarks without sounding a like a wise-ass. He does have remarks about sensible things, such as the graphical element used for sorting answers, or the background colors of areas that have static and less than important information. But I guess this guy primary mistake was to frame his remarks as "these are things that need to be changed, because im a designer and user experience expert", rather than "these are things that would be interesting to perform A/B-tests on to see if they improve the experience". That is how it came across anyway.
The problem tends to be that you need to tune it, and even as you have tuned it, you can not promise that under special condition it will fall back to a more primitive collector since the optimality it was tuned for doesn't hold anymore.
I would never argue giving up garbage collection entirely because of these failure scenarios. I would much rather look at moving some critical part of the code out to a language with manual allocation, and let it perform the latency-sensitive bits.
Another mid-ground is to have separate isolate processes (heaps really) that can be stop-the-world collected without blocking each other. Erlang makes great use of this to accomplish "soft realtime", among other things.
The interchangeable part (although I have never heard it called that) is more that knowledge should be spread, so you don't end up with domain experts that end up "owning" part of the code.
I just find pistoriusp to be quite agile in that they see themselves as a team, and that they have a todo list of things to finish in some order (backlog in agile terminology).
Since I am being down voted, there must be people that think it is a bad idea to introduce a fixed sprint length and perform time estimates on todo list items. For the conversation, I want to hear those arguments.
In lots of ways its strategies to show that you are interesting. To learn how you can captivate someones brain for a while. How you break through the normal filtering of the world. To understand when something similar is done to you. I even enjoy it when I know it happens to me, so it is a bit of a game.
There are things like body language saying yes, while words are saying no. Or several stories are being told simultaneously, unsuccessful ones being dropped and new one are started, to keep listeners. Or how to show that you are successful without appearing to be bragging.
I do not understand how agile allows for easier micro management as you say. If some team outsider tells our team how to work we tend to invite them as a member to the team for the next sprint, to show us what they mean. That usually sets the discussion in the right direction.
Since the backlog is highly visible, there is much better scrutiny of user stories for customers that have not yet signed a contract. There is also a built in stop of a sprint length before there is a review again of what the team has been ordered to do.
Basically, if the team took something off the backlog, we know who put it there. The team is doing exactly what it should be doing, taking items in priority order. Sales people have been fired at work, developers have not.
I would not go back to not doing this, as it allows focus (sales people fight to get things into the backlog and next sprint, rather than grabbing a developer directly). It discards out of the blue time estimates ("oh, maybe 3 months?"), by rejecting everything longer than the sprint. It also foster better developer-tester communication inside the team, already during development, which kills bugs earlier.
We're currently 3 teams with 5-6 developers and 1-2 testers each, soon to split into 4 teams and 2w sprints. So yeah, bigger company,
Agile killed a previous waterfall model with 2 month spec creation/review, 2-3 month development phase with developers being added and taken away during the time, and 1-2 months of testing, followed by bug fixing by developers that were taken out from other projects started by then.
But what if one had sturdy beams instead of wires that could guide the trolley-poles, and indirectly the driver to stay in-lane. More like a third-rail, that is 4-5m above the road.
These trucks and buses could then have a weaker combustion engine to use off electricity, but perform the majority of the trip, on the freeway, on electricity.
I understand that not all countries have a near mix of 50% hydro and 50% nuclear electric power to make this decrease pollution.
It is not that difficult to believe, since they have the right to eavesdrop that traffic, so their fingers are in that cookie jar already.
Imagine if we had designed internet to be resistant against governments as well, instead of only nuclear bombs.
Otherwise I am pretty sure that there will be a lot of "great" android apps to be ironic about as well.
For a small list like this I would use a fold function and accumulate up savings account amounts, all in one pass, all functional.
That will include a whole lot of empty caches. But it will be representative as well then.
The worst offenders to the speed of my site is that I have both google adsense and google analytics on it. I find it ironic.
From what I understand the time is sampled from visitors, and includes the time from the page request until the page is fully rendered.
I'd love to know what people do that get their times well below sub-second.
Okay, I thought that misinterpretation was initially funny. A picture says a 1000 words, but which they are depends on the viewer.
I have a site with (in february) 37663 pageviews reported by google adsense, but 49581 pageviews reported by google analytics. If the mismatch there is from adblockers, then I must be an outlier. I hope it is that google didnt have ads to match and displayed some public information message instead.
I'm not bitter or anything though. I block ads myself, mostly because I'm too afraid of accidentally clicking ads on a site of my own, and the punishment that can lead to.
The location where files are stored is where tags are a bit awkward. The folders are clear there. It's easy with folders to copy a picture from an SD card to my hard drive. From hd to a network mount.
The alternative would be to have magical tags, so everything you gave the 'hd' tag to, it would be stored on your hd.
In fact, the whole concept of adding a storage device to the system is strange with tags. Mount a 1Tb network share and automatic indexing starts? A standardized format for storing tag-information? What about computers that just change files directly without updating the tags? What about incompatible formats?
I wonder if applications could do a better job at tagging up files they create compared to the approach (in apple spotlight) to have search engine plugins that can find tags based on file content (mp3 id data, jpeg exif data,...).
If applications were more tag-aware, they could at least allow you to browse your files by tags instead of by folders.