Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cechner
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
cechner
7y ago
actually, beta is less useful than that! I think it represents the median difference between the two distances, its not a tolerance (at least as far as I can recall after experimenting with tuning this value). As with you, I have found that
2.
▲
by
cechner
7y ago
it should be in seconds - the problem is that the paper assumes that the 'great circle' (straight line) distance between two points should be almost the same as the 'route' distance between those points, with an exponent
3.
▲
by
cechner
7y ago
yep - look up 'Hidden Markov Map Matching through Noise and Sparseness' by Krumm and Newson it calculates the final probability by combining 'emission' probabilities (the probability that a GPS observation was on a parti
4.
▲
by
cechner
8y ago
do you have more modern benchmarks that cover the same ground?
5.
▲
by
cechner
10y ago
what is the point of this headline, other than to decieve? it is not the headline of the article and is not a quote from the text in the article edit: I hope I'm not just being a killjoy here - I actually thought this was going to be s
6.
▲
by
cechner
10y ago
When I first used Parallels years ago I was pretty surprised how close to native it could run Windows (though not 3D graphics intensive apps, as far as I can recall.) I tried running it recently though and the performance was _abysmal_. Jus
7.
▲
by
cechner
10y ago
> Developers do need to pick a set of core technologies, and stick to it or a career can fall apart I bet I hope not for my sake :) Im currently contracting writing C++, but my previous contract was with the ASP.Net stack. Before that I
8.
▲
by
cechner
10y ago
holy moly, I have forgotten more than I realised :( embarrassing
9.
▲
by
cechner
10y ago
nah thats mitsu (as in mitsubishi)
10.
▲
by
cechner
10y ago
(I went to bed so didn't take long to reply before) I am clearly not expressing myself well. I am talking about a situation where some stakeholders are expecting a complete picture of roughly how large the project is and would like to
11.
▲
by
cechner
10y ago
it is totally reasonable for stakeholders to want to track your progress through a project. If you have a good way of doing that then great, you should use that. Scrum people believe that scrum is the simplest way of measuring that. But at
12.
▲
by
cechner
10y ago
(replying here because I guess we've reached the maximum depth) I am here assuming that you want to be able to try to measure your progress through the project (as I mentioned, this is the only thing scrum does for you). Both of you se
13.
▲
by
cechner
10y ago
can we infer that he would like to give his estimates: * while he is actually writing the code (so not up front) * not in a group setting but as an individual, so either one person estimating the whole thing or each person giving different
14.
▲
by
cechner
10y ago
It sounds as though you objecting to being required to give any estimate at all.
15.
▲
by
cechner
10y ago
if its being used to 'get velocity up' instead of measuring velocity then its not being done right. I personally think estimating projects is one of the most difficult things about this industry. Especially if we're talking a
16.
▲
by
cechner
10y ago
If you're objecting to people who treat scrum (or any project management tool) as a one-stop-shop that will cure all ills I agree with you, but nobody here is saying that. If you are objecting to defining the scope as small tasks and m
17.
▲
by
cechner
10y ago
if pressure is ramping up and quality down the sprints arent serving their purpose. One of the few defining characteristics of scrum is that the developers define how much they can achieve, and this estimation is improved over time. If this
18.
▲
by
cechner
10y ago
I agree, it is often not the best approach. But many situations demand a well defined approach to estimation and although the OP tried to preempt this, he didnt provide an alternative
19.
▲
by
cechner
10y ago
oh and I have attended some of those expensive Scrum 1-week courses and saw the darker side of that community - it definitely has a cult following that give it a bad name, but I've been to similar conventions around design patterns, ob
20.
▲
by
cechner
10y ago
Scrum proponents (a label I would tentatively apply to myself) would tell you that 'you're doing it wrong' but unfortunately a point-by-point reply to this article would detract from the general problem here: Scrum is intende
21.
▲
by
cechner
11y ago
curious - I remember when modules were first proposed I thought Apple was heading up the initiative, based on their work with Objective-C. I remember reading slides someone at Apple prepared describing the likely syntax and everything...
22.
▲
by
cechner
11y ago
> The lifetime for a washing machine is 30 years. Your software on that will last 30 years. Using a development method designed to make quickly changing requirements easy is stupid when your code will be "write once, never change&qu
23.
▲
by
cechner
11y ago
you mean firmware updates? What is the problem you are talking about? Plus its a regular problem ensuring that an API is stable. People do it all the time - aren't you wondering why you are the only person arguing this point? Many peop
24.
▲
by
cechner
11y ago
I dont really understand this. "NF_REQ_00: API must not change" Add verification tests to ensure API remains as documented. Every time someone checks in code your tests are run, break if something changes. Every project has functi
25.
▲
by
cechner
11y ago
Ill reply to the root of all your comments, but this comment by you below sums up the problem: > If your software has clear requirements, has a point when it is done, and only requires minimum maintenance after that, you aren’t writing a
26.
▲
by
cechner
11y ago
interesting - I recently heard someone call it a forecast and thought 'man why don't they use that term in scrum?' Nice to know that they actually do (I havent read up on it in some time, probably should)
27.
▲
by
cechner
11y ago
well allow me to put a note here as someone who uses it successfully regularly. Also I explain several times why he doesn't seem to understand it - having non-technical people running his scrums, working overtime and screwing up their
28.
▲
by
cechner
11y ago
edit: I just noticed they said 'sprint commitment', and that they should adhere to it even if it runs overtime. This is probably the most wrong part of the article - you get done what you can, and let it affect your velocity. It i
29.
▲
by
cechner
11y ago
I don't really agree with this - Scrum isn't really easy to do but in many situations it is the simplest approach to take. If you need to monitor your progress in 'real' terms (i.e., whats actually completed) Scrum is pr
30.
▲
by
cechner
11y ago
I probably fit into the camp of people who would 'like' but not 'favourite'. BUT I am not a regular twitter user so perhaps my POV isn't that usual. I think of 'favouriting' something as a kind of bookmark
More ›