51–60 of 71 posts
Earlier quoted context omitted.
Classic projection. You probably suffer from it. I spell out my weaknesses clearly. And Object Astronauts suck.
the correct term is architecture astronauts, but we get your point.
I highlighted the fact that ignoring OOP is a weakness for @foobar_ and their response was essentially "you force every problem into objects and you suck". Interacting with this person is like carrying an open bag of snakes.
Earlier quoted context omitted.
Keep on projecting. Let me guess, you show up on time and kiss upper managements ass. You believe in patents. As far as I am concerned Hacker News is not for corporate drones like yourself. That's me disparaging you.
I've run my own startups (4), been through startups, ran the corporate race, successfully exited, successfully failed, ran successful projects, ran successful dev teams, ran some projects and dev teams into the ground, and now I'm back to entrepreneurship. I've just assumed this entire time that by comparison to an active entrepreneur you are a corporate drone, but let's stop the name calling. I don't have to believe…
You can improve communication skills by being polite and not accusing others of arrogance while being a hypocritical prick yourself.
After working with ~ 30 odd programmers, I would probably classify myself as a 10x. I think a good chunk of HN'ers are 10x, with imposter syndrome of course. 1. Patience - I have the patience to sit through and fix a bug. Googling it, reading the source ... this is fun for me. 1x programmers give up very often and very soon. They either blame others, feel pity for themselves for not figuring it out or hate the comput…
I'm definitely a 10x programmer, but unfortunately 90% of my time is spent on hackernews, so nothing is gained.
Earlier quoted context omitted.
I've run my own startups (4), been through startups, ran the corporate race, successfully exited, successfully failed, ran successful projects, ran successful dev teams, ran some projects and dev teams into the ground, and now I'm back to entrepreneurship. I've just assumed this entire time that by comparison to an active entrepreneur you are a corporate drone, but let's stop the name calling. I don't have to believe…
I've been a part of the startups(3), (1) was funded and is doing well, (2) failed, worked for wall street, ran and hired successful dev teams (2), trained (5) programmers, taught programming to three programmers (all of them got hired and are doing exceptionally well (1 with 0 tech background)) You can improve communication skills by being polite and not accusing others of arrogance while being a hypocritical prick y…
That's all I can see in your description.
At the end of the day you revealed that you are grossly under qualified with shit programming standards, a huge ego, and an abusive communication style.
And with the way you diagnose people with your projection - it sounds like you need meds.
One interesting twist is that some problems are completely intractable for most programmers. I mean that they cannot produce a working solution no matter how much time or effort they use, or if they do it's so riddled with bugs it's practically useless. Thus it follows that for certain tasks there are "∞x" programmers. Therefore there are absolutely "10x" programmers as well, which fits in with my subjective experien…
I mean that they cannot produce a working solution no matter how much time or effort they use Of course, but they don't represent the middle of the distribution. When people speak of the myth of the "10x programmer", that claim is meaningless if they can hold the reference productivity all the way to the far left of the distribution. Any meaningful claim of "10x programmers" needs to be measured against the mean or m…
Really? I don't think most middle-of-the-road engineers, given certain requirements, could come up with a working solution in any reasonable amount of time. For example if you just told an engineer "Implement a basic server that can execute queries based on this language spec, where you upload tables as immutable tab-separated text files" I'd guess only the top 5% of engineers could get something working in less than a month.
I don't think that executing tasks like this is something that innately only some small x% of engineers can do. For example, almost all engineers will lack at least some of the skills needed to complete any sufficiently large task: best practices for translating a query to a query plan, how to do efficient Ser-De, what data structures to use to implement the data, etc.
But most engineers lack the meta-skills or traits needed to complete the task. For example, would they first look at how basic SQL implementations and toy projects work? Look up some of the theory of RDBMS? Would they know how to write good tests, good class structures that don't require refactoring in 2 weeks as they understand more portions of the problem. Would they try to roll their own query parser or use a standardized tool like antlr?
Earlier quoted context omitted.
I've been a part of the startups(3), (1) was funded and is doing well, (2) failed, worked for wall street, ran and hired successful dev teams (2), trained (5) programmers, taught programming to three programmers (all of them got hired and are doing exceptionally well (1 with 0 tech background)) You can improve communication skills by being polite and not accusing others of arrogance while being a hypocritical prick y…
* you've worked for companies That's all I can see in your description. At the end of the day you revealed that you are grossly under qualified with shit programming standards, a huge ego, and an abusive communication style. And with the way you diagnose people with your projection - it sounds like you need meds.
^ Best way to identify a Narcissist is by their projective identification and overconfidence. In short, calls you an X, but does X all the time ... which gets quite confusing. Must be a nice NLP project in there.
Earlier quoted context omitted.
* you've worked for companies That's all I can see in your description. At the end of the day you revealed that you are grossly under qualified with shit programming standards, a huge ego, and an abusive communication style. And with the way you diagnose people with your projection - it sounds like you need meds.
Keep on projecting. ^ Best way to identify a Narcissist is by their projective identification and overconfidence. In short, calls you an X, but does X all the time ... which gets quite confusing. Must be a nice NLP project in there.
Earlier quoted context omitted.
I've been a part of the startups(3), (1) was funded and is doing well, (2) failed, worked for wall street, ran and hired successful dev teams (2), trained (5) programmers, taught programming to three programmers (all of them got hired and are doing exceptionally well (1 with 0 tech background)) You can improve communication skills by being polite and not accusing others of arrogance while being a hypocritical prick y…
* you've worked for companies That's all I can see in your description. At the end of the day you revealed that you are grossly under qualified with shit programming standards, a huge ego, and an abusive communication style. And with the way you diagnose people with your projection - it sounds like you need meds.
Here are some indicators I've seen from 10x and 100x: The 10x person fits very well in their organization. They are admired by upper-management for their ability to quickly comprehend, estimate, and deliver solutions to problems. They mentor everyone that asks or needs help. They provide 95% test coverage on all code. They show up for work well dressed, clean-cut, and on-time every day. Their code isn't 'brilliant' b…
I remember once being asked during a phone-screen how many lines of code I had written. Ever. Some of those things were on classified systems years ago, there is no way I'm going to remember that or even be able to look that up any more. Why would I ever log "wrote a net-worth of xyz lines of code today" for a personal record? I've never worked for anybody who had that as a metric but apparently I had a chance to now…