> The tools of marketers (data mining, consumer behavior analysis, surveys, market testing, etc) aren't just a veneer to be applied at the completion of a development project.
I strongly agree with this! If you're working towards a product (and not just a hobby project) then these are crucial requirements. If they can be found out before writing any code, then they should be, since it will save time in the long run.
For me it's also the kind of thing that can lead to costly changes after the fact, which is prone to rub developers up the wrong way. It seems like the principle of phase containment might apply - if you found it early in the development cycle, then it would have been easier to fix.
There are lots of startup founders who do feel a bit sleazy, or like they're just faking it until they make it. You don't give that impression at all!
As others have said below, I think you should push your product a bit. It might not be perfect, but if you can talk it up a bit whilst accepting valid feedback, then you're more likely to come off as dedicated and earnest. People can then trust that the product is likely to head in the right direction under your care.
Strongly agreed! It doesn't just seem unfair, it is unfair.
I also think that there's much more celebration of "overcoming" disability or illness, rather than the much more sustainable (and difficult!) practice of changing your work patterns and lifestyle to live within your daily allotment of spoons.
Even if it does boil down to that, there might still be value in ranking the savings per service you buy in. Except for a core product, it is almost always going to be the case that buying in is cheaper than building it. However, having limited resources, it's valuable to work out what tools could give you the best value for money, and which others are a more marginal call (given the uncertainty about support work etc.)
It does seem obviously to be a spectrum. I only realised that I have some degree of aphantasia when I read an article on it.
I think there's also an element of things being "faint" in your mind's eye. For example, there's a McDonald's and horse racetrack that I drive by every day on my way to work. I can sort of visualise some constituent parts, but there are no details and there's no overall picture.
I also don't know how much of the visualisation is just me recalling (in abstract) what is there, since I am very familiar with it.
This just sounds like a bad/inappropriate use of a tool. I wouldn't think that a team of people working on unconnected items should have any meetings at all, let alone a daily stand-up.
As others have said, when you're working on a team where there is significant interplay or varied, related experience, they're really useful. We work on an OS and have members of the team who happen to have experience using infra and tooling. There's no way you would necessarily know this without saying "Oh, I was struggling with this bit of stats collection infra" and somebody else says "Yeah, I worked on that on x project, y years ago. Let's chat after stand-up."
There are obviously other ways to seed this kind of thing, but brief stand-ups seem a good way of doing it.
The other thing that we tend to do is just say "Oh, I did x that doesn't really relate to the project yesterday, but that's not very interesting" and leave it at that.
That's great to hear to be honest. It sounds like you're one of the self-made grafter types. :) My parents' background is similar - they both put themselves through university as adult learners having a pretty poor time of it at the end of high school (for various reasons).
My dad is potentially a good, albeit anecdotal, example of this. He's one of those people who's had every semi-skilled job under the sun, mainly to make sure that he could provide for his family. Eventually, he paid his way through university and chartership and now he does what he enjoys and he's a very well-regarded psychologist. But the thing is that he could have had all that for his whole life, instead of having to struggle his way up there, if he'd lucked into the right background to begin with.
The other thing that we on HN have to consider is that we're generally able to work very well in analytical and numerate disciplines compared to the average of the population. As another anecdotal example, my sister has a (mild) learning difficulty, but it really does just mean that her prospects are much more limited compared to mine. She has a great life, but it's very unlikely that she'll ever be a high-earner. It's most certainly not for lack of will or graft though, just the lottery of life.
For my lot, I'm just glad I happen to have the skills that people want to pay money for. I recognise that I worked hard to get here, but I also acknowledge that luck played a substantial part in everything and I'm grateful for that.
Oh, I certainly don't mean that a good university place guarantees you a top job. My company targets top universities, so it naturally has to reject a bunch of people who just aren't the right fit. However, it is certainly the case that you can usually infer the other way around (i.e. that people with top jobs tend to have good degrees from well-respected universities).
For many graduate software roles over here, recruiting targets people studying "any numerate discipline". These people don't have any professional software dev experience or a CS background, so wouldn't be able to demonstrate those skills from the start. However, the decent degree from a good university is a proxy for the appropriate skillsets required.
The problem remains that there are people with all the skills who just can't get their foot in the door because their background just didn't give them a reasonable opportunity to do so.
In the UK at least, the people who've managed to bootstrap themselves to success through hard work and good decision making are the overwhelming minority.
The causal chain seems to roughly be: Top jobs tend to belong to those who attended top universities. => Top universities are attended by those who went to private schools. => Those who went to private school are either from wealthy families or attending on scholarship due largely to the fortune of genetics and/or an educated family. I certainly benefited from that (school scholarship => Oxbridge => good tech job), but I don't know that I could have if fortune hadn't smiled on me.
I agree that even with all those benefits, you can still fail if you make poor choices. However, I don't think the vast majority of people with worse circumstances can just choose their way out of it. It's not to say that it's impossible - my grandma has a rags to riches story that's only slightly marred by her similarly ethically dubious sales techniques...
Even using the carpentry analogy, I suspect the point is to avoid ruining something on which a lot of time was spent. The material cost of most raw materials isn't very high, but ruining something you've already spent hours crafting is extremely costly.
The other thing to bear in mind is that there is always more work to be done than time to do it. You have to factor in opportunity cost. As many other commenters have said, ultimately it's a balance which depends on your company's particular situation.
Yes, though some other commenters have pointed out caveats (e.g. do they really have a free choice?).
IANA moral philosopher, but I think the gender of the baby being a primary consideration in abortion also makes this a more complicated issue. I feel this is more akin to the ethical dilemma of whether to abort foetuses with non-fatal disabilities.
I don't think HN can necessarily be to blame. It might just be one of those "you're getting older, so think things were different when you were young" things, but I certainly feel I have a shorter attention span and have to try really hard to pay attention for extended periods. I don't know what to blame, but suspect that the attention economy is part of it. It could also be that I'm both a programmer and a gamer, so my brain now expects to be stimulated a lot of the time.
Also, just in case it's one of those words that you've been mixing up (rather than a typo), I thought you might appreciate knowing that it's "empathize with", rather than "emphasize with". I had that for the longest time with not knowing that the spoken and written versions of "awry" are the same word...
I recall someone saying that holiday periods actually had better reliability for their services, because fewer people were pushing breaking changes...
I do wonder if it's that the usual maintainers of particular bits and pieces are on vacation and so others are having to step in and they're less familiar or spread too thin.
I'd generally agree with this (bumped up against more gcc, libc and kernel bugs than I'd have liked), but I find that my code has even more bugs than that. :)
N.B. My understanding of this stuff is pretty vague, but here's a quick summary of the arguments I've heard on the matter:
I think the grievances might be to do with the amount of money paid into a pension pot versus the size of that pot. At least in the UK, many companies offered generous final-salary pensions, which (as the name suggests) are based on your income and index-linked. These have been basically phased out now, since they're too expensive (i.e. I think they generally cost more to fund than the person originally paid in + any accumulated investment returns). However, for those people who paid into such a scheme, there's no recourse for the scheme providers but to subsidise these expensive pensions with the rest of the communal pot. This means that they necessarily must offer less generous pensions to those who are currently paying in and will draw a pension in future.
I think there are also some arguments in the UK that oil wealth was used for short-term subsidies (e.g. tax cuts), rather than put into a long-term investment fund, like Norway. The people who benefited from that are the people who were alive at the time, and the eventual beneficiaries of their wills.
I don't know how accurate this all is, so would welcome a more informed perspective too.
I strongly agree with this! If you're working towards a product (and not just a hobby project) then these are crucial requirements. If they can be found out before writing any code, then they should be, since it will save time in the long run.
For me it's also the kind of thing that can lead to costly changes after the fact, which is prone to rub developers up the wrong way. It seems like the principle of phase containment might apply - if you found it early in the development cycle, then it would have been easier to fix.