Live data from Hacker News

Rules of thumb for a 1x developer

muldoon.cloud

431–440 of 505 posts

Re: Rules of thumb for a 1x developer

#431
post #430
post #389

Earlier quoted context omitted.

Riiiiiiightttttttt, because having well defined data is not useful at all.

You can have well defined data and use Mongo. Those two things are not related. I worked at a place that used Postgres and put an object w/ 11k unique paths in a single JSONB column with no schema or documentation whatsoever.

... and this system was responsible for billing, and many other things....

Re: Rules of thumb for a 1x developer

#432
post #105

This is poorly titled. A '1x developer' is by definition an average developer. The page is mostly listing basic knowledge that any developer, even a very junior one, should already have. If you aren't aware of the relative strengths and weaknesses of Java, C, and Python, you aren't a 1x developer, you're a trainee. Anyone know of any better articles truly targeted at '1x' developers? (This isn't snark, it's an invita…

In the study that lead to the "10x developers" term. 1x developer was not the average, but the least good (because they still were able finished the task). You can't measure against the "worst" because they aren't able to provide a deliverable.

Thanks, I didn't know that. I don't think that's how the term is used these days though.

Re: Rules of thumb for a 1x developer

#433

Earlier quoted context omitted.

They can ask related questions which might reveal this information. https://news.ycombinator.com/item?id=23031508

Do people really ask about hobbies? In actual professional job interviews? The other questions only lead to answers that involve your personal life if you choose to talk about your personal life. Job interviews are professional negotiation, not chats with friends. Where do you see yourself professionally in 5 years? Why would you mention your family? Asking if you're willing to put in lots of overtime should be a red…

Hobbies? Of course, particularly in entertainment software. It shows if you have a unique perspective that could be advantageous to the creative process.

I would mention my family for any professional prediction because it is a guiding factor; in five years, I see myself continuing to be a product lead and hopefully working with my daughters on an independent project of their own.

I work in entertainment software, in British Columbia; overtime is normal, working 40h a week or less is not. The BC NDP stripped tech workers of their basic employment rights, around two decades ago; among those rights removed was any right to overtime compensation.

I can't work in the USA _easily_ and I would _prefer_ not to; I have no interest in raising my kids there. But I've worked from home for five years and so I don't see why I should have to relocate. :P

Re: Rules of thumb for a 1x developer

#434
post #398

Earlier quoted context omitted.

Salaries over time are rarely based upon prior experience or knowledge; they are the function of normal annual salary adjustments combined with 5-20% increases when job hopping. Which is, if you perform well, roughly equivalent a 4% annual compound interest. As they say, compound interest is king - companies are just not willing to swallow the fact that the compound interest is in this case working against them. And…

Salary isn't a function of time- it's a function of perceived value and leverage.

The only way your salary won’t go up on a yearly basis is if you’re constantly on the road to being fired. Cost of living increases (2%), as well as small yearly increases to keep you motivated and content (1-2%), are just a fact of life when working for a company.

The only part that’s tied to your perceived value and leverage are bonuses or new job salaries (and most of the time those are tied to your previous salary). I’m not counting bonuses, and getting over a 20% increase when switching jobs is a startlingly rare event reserved for CEOs and the Guidos of this world.

Also, if you have concrete examples to the opposite, I’d like to hear them. Simply claiming repeatedly that they are merit based does nothing to sway me to your position.

Re: Rules of thumb for a 1x developer

#435
post #363

"Rule 11: Which database technology to choose: Choose SQL when you need to do ad hoc queries and/or you need support for ACID and transactions. Otherwise choose no-SQL" I think it should be the contrary: SQL by default, no-SQL if you have a specific need and know what you are doing.

I feel like the unstated caveat is "there will almost always come a time when you need to do ad hoc queries, and there will almost always come a time when you need transactions or the equivalent." Which translates to "use sql unless you are sure your don't and won't need to do ad hoc queries or transactions." Which... seems correct.

Re: Rules of thumb for a 1x developer

#436
post #40

"To replace out MediaWiki with a Java-based alternative (XWiki) ended up taking a total fo 24 dev-years over 4+ calendar years for the team, not counting the interruptions to pretty much every other team at Amazon as their pages were getting constantly migrated and un-migrated" I would love to hear more about this. I'm guessing that's a cost of at least $4M? How was this approved? How did they allow it to continue fo…

I don't understand why are corporations obsessed with decommissioning wikis. When I was at Red Hat, they tried to decommission local country wiki in favor of their company-wide wiki (Mojo, absolute shit by the way). They tried for about 2 years, then finally somebody said "what the fuck are we doing" and the migration was stopped. I believe the banner "Decommissioning soon" still hangs there.

I've seen a engineering wiki migration done in 3 months at another bigco.

Getting documentation off google docs on the other hand seems impossible from a behavior standpoint :(

Re: Rules of thumb for a 1x developer

#437

Earlier quoted context omitted.

> " It's reassuring to see the push-back against the 10x developer idea, I'm starting to feel less guilty now when I spend my free time NOT on programming. " 10x developers don't spend their free time programming, at least in my observation. They don't need to. > " I want to ask though - the author works at Amazon and considers himself a 1x developer. " A 1x developer would be an average (ok, fine, median) developer,…

> 10x developers don't spend their free time programming, at least in my observation. They don't need to. Ah, I guess I need to read more about what people view as a 10x developer. I didn't mean to imply that a 10x developer spent all of their free time coding. I just meant that with companies, job descriptions, other dev, etc. talking about wanting a 10x developer I feel pressured to spend my free time programming,…

>Doesn't working at a FAANG company imply that you are better than average, considering the status of these companies, their rigorous interview processes, and so on?

No.

Re: Rules of thumb for a 1x developer

#438
post #244

Earlier quoted context omitted.

> They're cheaper, willing to work longer hours So now we've hit the real root of the problem. If you expect significantly more money than competitors in your role- than ageism may not be why it's getting harder to find jobs. It isn't 'ageist' to disagree on the value of prior experience.

Salaries over time are rarely based upon prior experience or knowledge; they are the function of normal annual salary adjustments combined with 5-20% increases when job hopping. Which is, if you perform well, roughly equivalent a 4% annual compound interest. As they say, compound interest is king - companies are just not willing to swallow the fact that the compound interest is in this case working against them. And…

Are you taking inflation into account? A $60K starting salary in 1980 is equivalent to a $190K starting salary today.

Re: Rules of thumb for a 1x developer

#439

> Rule 20: When somebody says Agile, push for Kanban, not Scrum... ...Scrum can easily mean that you’ll get pressured to work extra hours to complete something within that arbitary two-week horizon. This is very true. I've worked for over 12 years in the bay area in different software engineering teams at startups and found that scrum just leads to burnout and developer unhappiness and encourages team members to just…

To be clear: XP and Kanban are different things. XP has prescribed engineering practices, most forcefully that development should be done via pair programming for continuous code review. Kanban prescribes no engineering practices and could be used in lots of non-engineering contexts (e.g., your marketing team could take all of their tasks, put them in a prioritized backlog, then track the progression of those tasks a…

> You have to work a late night the day before sprint release? You were in the room when the team agreed to the body of work that would be committed for delivery in this sprint.

Fuck that. The fact that my estimate does not work out as expected should not be a reason to work late nights just to get it done.

That’s exactly the death march that you were saying Scrum is not.

Re: Rules of thumb for a 1x developer

#440
post #431
post #430

Earlier quoted context omitted.

You can have well defined data and use Mongo. Those two things are not related. I worked at a place that used Postgres and put an object w/ 11k unique paths in a single JSONB column with no schema or documentation whatsoever.

... and this system was responsible for billing, and many other things....

and? That's not PGSQL fault, is the DB architect (or lack of) fault. You definitely can drive the safest car in a ditch, no?
Post reply on HN