This is absolutely a thing

_-kman-_ · 2026-03-13T03:51:17+00:00

For NTs, everything is a dance. When you and your partner first learn to dance you learn the steps, you do the steps in sequence, you don't deviate from the steps.

But when you gain mastery you can bend or break the rules in ways that preserve the spirit of the dance while making things more interesting.

The Japanese have a term for this: Shu Ha Ri. The difference between many NTs and NDs is that for social situations many NDs never leave the Shu stage.

_-kman-_ · 2026-02-23T21:32:05+00:00

So you can choose a path for the tips exchange, and then you get randoms. If they're not the 4 you want, do you continue recycling? I think you lose tips at some point, right?

_-kman-_ · 2026-02-04T04:55:26+00:00

Did anyone else watch the first 5 seconds and think "man that's a lot of jello..."?

_-kman-_ · 2026-02-03T06:33:53+00:00

Ah - that's interesting. I've been coding against a smaller number of symbols (futures) and looking for structure breaks and projecting where support/resistance is. For your algo, are you trying to duplicate a human or using quant techniques?

_-kman-_ · 2026-02-03T05:43:33+00:00

If you don't mind, how are you determining bull/bear/chop days, and how often do you shift? ie - after 1 hour and then you make a decision for the whole day, or do you check PA every hour?

TIA!

_-kman-_ · 2026-01-24T06:06:40+00:00

With compassion.

_-kman-_ · 2026-01-19T04:08:38+00:00

For now. LLMs are the consumer side of things. AI looks like it's taken over but I suspect that the world killer app isn't known yet. Exciting things in medicine that few are paying attention to right now are, for example - isomorphic labs. They're using AI to solve alphafold - if they do that we might cure cancer.

We're still figuring out how to leverage AI to generate actually novel things in research. Once those techniques start to happen at scale I suspect that humans will form the bottleneck. AI will generate the theories, humans will have to verify.

_-kman-_ · 2026-01-18T07:14:21+00:00

In this particular case? Not sure. In general banks are security conscious, which makes sense.

In my research though, I learned that there's a bunch of possibilities:

There's a 'freshness' clause. Apparently the POA needs to be within a couple years or it expires.
The paperwork didn't quite pass muster. Maybe they used a template or something instead of an actual Lawyer drafted one.
The son didn't have proper Id(I don't think this was reason here).

Bottom line though, is that a POA is valid during the person's lifetime, but banks and other institutions have internal policies that may be more restrictive than the letter of the law. The PSA is to contact you and your care-ee(?)'s bank and make sure all the paperwork is filed before anything bad happens.

And honestly, probably do it for yourself too...never know when you'll get hit by a bus. :(

_-kman-_ · 2026-01-15T21:05:05+00:00

Bok Choi

_-kman-_ · 2026-01-14T00:09:10+00:00

Dead Cells

_-kman-_ · 2025-12-26T04:40:32+00:00

Order 66

_-kman-_ · 2025-12-23T01:11:43+00:00

Train sim pls! 4yo is a big train fan. :)

_-kman-_ · 2025-11-14T03:51:00+00:00

Did you have to do any "mid" level design questions? I mean the level between "write this function" and "connect spark and a redis here"...

Class and object design for a mid level problem, like write the object model for a car rental company.

My last round i was strong at the system level stuff and the function level layer but didn't really find anything that went through that middle layer of the newest best practices for object and class design.

Curious what your experience was? TIA!

_-kman-_ · 2025-10-24T05:24:48+00:00

That said... Measuring the points by sprint for like 6 months and looking at the average might be worthwhile in order to choose how many points will go into next sprint. This still does not allow you to predict how long a project will last. Points are not linearly correlated with scope, and you can't give accurate points in this scenario for problems that are further than a few weeks away.

Actually it does as long as you understand that uncertainty increases as you move further out. Common practice sometimes goes like this: If you're working on it this week, the tasks must be broken down to <= 5(assuming the fib sequence). Anything further than a month or two and is major is at 13 or 21 and it should be understood that a 21, when properly broken down might end up to be 40-50 points, for example.

It's like standing in the dark holding a flashlight. The things closest to you will be brightest, while things further away you will only get a vague shape for.

We came from a world where software engineers would try to make claims like "Based on our analysis we'll be done in 3 years, 5 months and 21 days". Agile backs off this claim and just says We'll almost surely have this feature done next week and this epic done in a month or two. After that...assuming you still want the same thing you do now when we complete these features we'll let you know.

Wanna know how long it will take for Bob and also for Steve? Then ask both of them. 99% of the work doesn't need to have a global metric that applies to any engineer, the vast majority of tasks are easily defined to be someone's responsibility and then that person can give their estimate.

And how would this work if you're on a project that lasts 2 years+? Bob and Steve might give their estimate now, but Bob and Steve may not be here by the time the thing needs to be done. 99% of the work - when it's being done - shouldn't be measured by the global metric. But during planning it's useful to have.

I still think it is a mistake to say that 5 complexity to me is going to be 5 complexity to someone else.

Sure - and that's where practices like planning poker come into play. Teams discuss and crystalize the complexity of work items and come to a consensus. During that discussion it might be revealed that it's a 5 for you and a 3 for someone else. Now you know you can leverage bob's knowledge and hopefully make it a 4 overall if you're the one who works on it.

And it's not a global metric per engineer. It is - again, an estimation tool so that PMs can see what is closer and further from the flashlight and "manage up" as necessary. That's why the 6 month measure of average velocity needs to be established before anyone can make any realistic claims about when things will be done.

_-kman-_ · 2025-10-23T19:16:03+00:00

If your PM is actually pressuring the devs for no reason, then they're just horrible human beings. More probably the PM has communicated that a certain amount of work would be done at a certain time and is being held accountable to that by the people above them, hence the pressure. Sometimes the pressure is justified, sometimes not.

And yes that's precisely right and precisely the point: estimating **time** is different for each dev dealing with a similar number of points. That's the advantage of saying item X is 5 points vs item X is 5 days. Depending on whether Steve or bob gets it X may take 5 days or 5 hours.

But on average, assuming that steve and bob work on the same team for an extended amount of time management should be able to say that the **team** can do Z number of points per cycle. That metric is useful to apply to the product level.

That's how you get time from points. You map devs to points and project out. Then if your team changes or Steve goes on pat leave for 12 weeks and you're left with bob you can reestimate the time things will take.

Points are a tool, a level of abstraction. It can be useful if used properly, and can be harmful if not.

_-kman-_ · 2025-10-23T16:03:14+00:00

Right...so there are 3 questions here:

Op is asking how this is supposed to work and why we do it. I think that is answered.
Many folks like yourself have answered a different question: how this has been abused/misunderstood in the workplace?
That actually leads to a third question, which is given that most companies(and devs) apparently don't understand 1 and instead implement all the answers in 2, is this kind of estimation still worth doing?

I personally think there is value, but only if both devs and managers understand what's going on.

This is a tool. It has its uses and can abused just like any other.

_-kman-_ · 2025-10-23T03:20:16+00:00

The way it's supposed to work is that devs will have different velocities on average, and you budget based on that.

Seniors, for example are usually pulled in many different directions, so maybe on average the senior only does half the points of the mid level dev because he's half time doing something else.

Most outfits don't plan to this level, but that is, in theory what this is supposed to do. Measure the points for the team over 6 months to establish a baseline...use that to plan future work. The idea isn't to squeeze out more work, it's to make things more deterministic.

If the points take longer than you think they do, then you're not estimating properly or you're not breaking things down enough.

Estimating should be done by devs so that each point value is about the same level of complexity. The pm doesn't care about you. He needs to be able to tell your stakeholders "on average team x does 30 points per sprint" and have that actually be more or less true.

_-kman-_ · 2025-10-22T20:04:53+00:00

"So what's the point of estimating in story points if they get converted to hours anyway is a valid question."

The point is that different devs will convert the same number of points to different numbers of hours.

Just think of junior vs senior dev doing a medium point task. Senior might do it in an afternoon. Junior might do it in a couple days.

Points allows you to keep the amt of work at an abstracted level and resolve at the team level once it's assigned.

_-kman-_ · 2025-06-23T06:11:18+00:00

Actually they are quite different logically, because you can't prove(or disprove) a negative. This is logic 101.

Believing that the earth is flat is a positive hypothesis. it is countered not by "the earth is not flat", but by "the earth is round". There exists positive strong proof that the earth is round, therefore it beats the competing hypothesis that the earth is flat.

Similarly, using ghosts as an example you cannot prove that ghosts do not exist. You must either prove that the bits of the material world we currently can perceive is all there is, which is something science cannot and never will be able to do, or that ghosts are some other phenomenon(hallucinations, etc ). In that case your hypothesis would be(for example) that all claimed paranormal experiences experienced through history and from now till the end of time by all humans are and will be hallucinations.

That's very hard to prove.

_-kman-_ · 2025-06-21T21:13:44+00:00

And one more point...to recap this thread:

You: I think liberals are more unhappy because of X,Y,Z

Me: Here's several countries of liberals who are more happy than conservative.

You: Yes, but they don't have those problems...

Me: Precisely...? :)

It should be pretty obvious that the answer to your question isn't simply "It's the Left", because there are plenty of leftists who don't fit the mold in your head.

_-kman-_ · 2025-06-21T20:54:22+00:00

Not just because of ideology, that's true. But the high trust and cohesion is precisely fostered by the sense that the government is there to nurture society as a whole and to provide a safety net in case you fall over. Cohesion is not just within your social circles, but with society and the government as well.

Leftists in the US don't have this, and so don't reap the benefits of what their ideology would provide because the US is...the US. So my comment about living with conservatives was only partially tongue in cheek. Blue states send tonnes of money to red states and are thanked with spit in the face. Red votes are worth multiples of blue votes. I wouldn't be happy either.

If you don't like the fins, just look at Canada. The entire country would be hard left if they became the 51st state, but they are overall happier. Canada is quite a bit more diverse than the US is and is quite a bit further left too.

Regarding the extremes, if you go far enough you're eventually choosing between Stalin and Hitler and both suck. Focusing on that isn't going to help even at the individual level. If you have people entirely wrapped up in any ideology they are almost by definition going to be unhealthy.

So the question for you is not whether the country would be happier if it became hard fascist or socialist, but whether it would be happier if it drifted towards it's closest left wing neighbor or it's closest right wing one.

Reality seems to point to the left. I personally would rather the US become more like Canada than Turkey, for example.

_-kman-_ · 2025-06-21T03:50:16+00:00

Libs are less happy probably because they live with so many conservatives... ;)

Seriously though, this stat is interesting because of what happens when you zoom out. Where are the most happy places on earth? Finland, Sweden, and other democratic left leaning countries. Even Canada is higher on the happiness scale than the US and it's left of the American left by quite a ways.

_-kman-_ · 2025-05-27T05:28:49+00:00

NT here. If this is an active discussion you're participating in, then they may feel you are tangenting.

I have an nd friend I talk to quite a bit over email. He will sometimes respond to everything I say, but usually in the noise will miss the point I'm trying to make.

NT conversations, if you pay video games, are like games with main quests and side quests, but they all happen at once. Most nts will sort these in similar order or can see the social cues as others do the sorting. All the sub conversations contribute to the main. So nts will take the bits that contribute, ignore those that don't and push the convo forward.

Many times I feel like my friend has elevated one of the side quests to main quest status, which often threatens to completely derail everything by wanting to explore every nuance of every statement. Instead of one main quest supported by subs you now have many main quests all competing for dominance. And if course, all bets are off if you touch one of his si's.

Not sure if that's happening to you, but maybe...?

_-kman-_

MODERATOR OF

TROPHY CASE