dd444fgdfg

wow slashdot is still going?!?!

Imagine a timeline from left to right. On the left is where there's the least knowledge about the project, and on the right the most (when the project is done). Estimates are made at the far left, when the developers know the least. So as you move along the timeline and more knowledge is discovered, you need to reset expectations frequently.

but it's such a shame, it's a lovely tool

Ship of Theseus. I new a janitor who used the same broom for his entire 20 year career. All he had to do was replace the head when it wore out, and the handle when it broke.

How did Perl "lose"? It's such a great tool, super powerful and concise. One of the best languages out there, but doesn't seem to have much adoption these days.

I...don't know how to put this, but... I'm kind of a big deal. People know me. I have many leather bound books.

it's clearly a message from aliens, embedded in the data stream to get our intention. Occam's razor and all that...

thanks for resolving this discussion on behalf of the developer community

"feature owner didn't pay for tells owner he didn't pay for it"

here in Australia nobody ever seems to have cash anymore, and it doesn't seem to be an issue. Tap your phone to pay, done.

this is pretty typical stuff these days for a typical well to do SaaS org.

I've seen it work well. It can help facilitate the conversation between a manager and direct report when trying to understand what the gaps are between their current role, and where they want to go next. It also helps keep those discussions aligned across different managers/directs across the organisation.

It also has it's down sides. There's no perfect solution to soft skills.

Depends on what you mean by success. Those who rise through the ranks tend to have a combination of ambition and ability. I've worked with plenty of great devs who didn't have ambition to become a lead/manager never mind a VPoE. And, I've worked with plenty who had the desire to but they didn't have the ability.

everything goes in cycles. one day it will be hip again to have physical buttons for everything, and a bunch of cars will be release with innovative buttons with direct access to the function, no need to use the screen!

2022 - getting the team back together...

It's not a taking anything away from us, to say we're not engineers.

It would be helpful if engineering had a widely accepted succinct definition like the scientific method, but it doesn't.

Building software is its own thing. It requires some engineering discipline. It requires some scientific method. It requires some artistic creativity. It requires operating efficiently within some community.

It also (usually) does not require the rigor of engineering because it's ephemeral, and it doesn't require the proof of science because it's every changing, there is no truth.

It's software, and that's not better or worse than engineering it's just different.

is that true though? CP on Etherium blockchain is a well known problem, and no prosecution jurisdiction is doing anything about it. Who would even have jurisdiction on something so decentralised? Sure you could shut down some nodes, but not all of them. And even then new nodes would pop up vastly more quickly than you can kill them. So prosecutors really are powerless. I think. Am I wrong?

I'm*

that's... delusional at best. The US legal system is massively corrupt, racist, an ill-informed on technology. And this is a very generous view of it.

being agile does not mean "not having a plan", it means having a flexible plan and adapting the plan as things change.

;

i don't disagree. but there are valuable side effects. like engineering technology learned. a place and economy for physicists to "work". The web came from CERN, think of all the things we got from the moonshot. we get a lot from big science projects if not the end goal.

what? are you saying they showcased the best results? that's unheard of.

so are they missing a cover from inventory?

Humans are much more complicated than code.

If you want to be a great manager, you need to be as self-interested in learning about leadership and people as you once were about the tooling and platforms you used to build on.

Here's a few things I learned over several years and many senior leadership positions:

1. be humble. this is the single most important thing in your leadership position.

2. every problem is a leadership problem.

3. you lead people, and you manage process.

the US political system is completely broken, and it's destroying a great country. it's a leadership problem, and needs someone who is capable of detaching and acting in the best interest of the country, not themselves or their party.

they need a complete reboot. rewrite the constitution (it's overdue). rebuild the democratic voting functions (they're a mess and don't work).

time for democracy 2.0

Burial at sea. I'm not even convinced they killed him at the time.

I've always done something similar, but less structured and probably with less intent.

Most of the problems we software developers encounter, we've solved before. So it's usually a case of recognizing the pattern of problems this is, and matching it to one you've solved before, and quickly being able to reference that previous solution. That's 95% of getting it done.

One of my favourite books is about how spiders evolve over a very long time to gain superior intelligence to humans, Children of Time, read it!

I think you have a marketing problem, not a technical one.

People are cross-shopping Clickhouse/TimescaleDB rightly or wrongly, and it's not clear to community when they should use which. What overlaps on the Venn-diagram and what doesn't, and when they do why would I go one way or the other.

You have to do a better job of showing how you're solving customer problems. Benchmarks are next to useless, an unsolvable problem, I wouldn't waste time on it. If customers are succeeding on your platform, you'll succeed.

well, what does pronounced mean? how much time difference is too much?

when I give it more thought, it feels to me that when we say time, we're really say how fast things move relative to other things, and that makes it easier to reason about how different parts of your body are not upset about experiencing time differently