This page pegs my CPU. Flagged for that reason.
Show HN: Coding Career Handbook
91–100 of 140 posts
Re: Show HN: Coding Career Handbook
#92Earlier quoted context omitted.
Corporations won't stop outsourcing because of reason, but they will stop outsourcing because of feelings. I like to hammer down on issues with contractors by basically minimizing the issue: "who cares if our customers couldn't access our product for 3 hours due to an outage? we're saving so much money by outsourcing!". It's a simple way to get people on your side because noone would like to agree that 3 hours of out…
But in my experience I have never seen cases where you really save money. The outsourced dev charges less, yes, but the outsourcing company needs to make money. But let's say what was 10 an hour, now it is 5. In my experience is that what used to take 1 hour, now it takes 2 or even 3. In the end, hardly any savings.
> I have never seen cases where you really save money
Of course you can't save money. The guy proposing the outsourcing is either getting kickbacks or will get a massive bonus from 'cost reduction'.
I like to kick the wind out of their sails by loving their proposal and reminding them that payroll changes don't count towards bonuses and they'll have to be up early to manage their new team. Suddenly, it's a bad idea.
Re: Show HN: Coding Career Handbook
#93Earlier quoted context omitted.
Because that is what sells now. Write a book for Packt on X you are learning as you go => Leading expert in X and charge 100USD/hour Write a bunch of blog spam on X, a lot of it wrong => Leading expert in X and charge 100USD/hour Create a bunch of projects that have more bugs than Swiss cheese has holes => Leading expert in X and charge 100USD/hour There is a story today here that says GitHub is the Instagram of prog…
So if we accept this as baseline reality then what do we do?
For Github projects, we could have an organization that would conduct project audit and certification on owner's expense. As an owner of a few open-source projects, I'm a little tired of hearing such insinuations as in the post above (although there is certainly a grain of truth in it -- we live in the Age of Bullshit, after all), so I would gladly cash out $1000 for getting a "quality approved" stamp from a widely trusted entity.
Re: Show HN: Coding Career Handbook
#94Earlier quoted context omitted.
Swyx is legit. The speed at which he established himself as an authority in the React/Javascript world is hella impressive And he’s fresh enough that his advice isn’t enbittered and grizzled yet.
I am not downvoting you, but (if GP is accurate) 2 years of professional experience is nothing, and to be an authority is laughable. To say he established himself as a developer marketer, ok, but damn, really? 2 Years? When I started to work 2 years was junior level developer, and now they are authorities?? I quickly checked his writings. I am not trying to put him down, they are ok, but completely different than wha…
You forget the whole React field is like 5 years old.
And this book is aimed at beginners, not folks like us with decades in the field.
Re: Show HN: Coding Career Handbook
#95> The Coding will always be the easiest part of a Coding Career I'm a little triggered by this headline. I understand what it means, and I agree there's some truth to it. It can be good advice when given to developers who haven't yet figured out that their job is not exclusively to write code. But in my company (which is a big non-tech corporate) I've noticed that a similar phrase often gets used by non-technical peo…
To be honest, the technical problems are the easy thing in most companies since they just need a simple CRUD app and anything you do will be magic to most people regardless. The politics are the difficult part of most work in this industry. Everyone has an agenda (which is not a bad thing) and serving multiple agendas will make your technical problems even worse.
Depends where you work, if it's a dinky ecommerce site with no scalability issues, then coding is not a problem. But if it's a real product company with AI/ML engineering problems, then coding definitely is.
Re: Show HN: Coding Career Handbook
#96Please don't take this the wrong way; I am genuinely curious. As far as I can tell, you've been a professional developer for approximately 2 years. What qualifies you to instruct people how to manage their dev career, let alone charge $40+ for the advice?
> What qualifies you to instruct people how to manage their dev career
Well, absolutely nothing, and it's a shame to see people (I have to imagine mostly college interns and fresh grads who already fancy themselves as "mid-level" developers) waste money on this nonsense.
Unfortunately this is what happens when you see job advertisements requiring "Senior Developers" and specifying 5 years of total work experience. In no other industry can you be a 27 year old and be anything other than junior-to-mid. I say this as someone who was a senior developer in my late 20's, and you don't know anything in your late 20's.
But I suppose if you're a senior developer after a couple years, what's to say you can't advise people on their careers when you haven't even made it through a Presidential election?
Re: Show HN: Coding Career Handbook
#97Earlier quoted context omitted.
Because that is what sells now. Write a book for Packt on X you are learning as you go => Leading expert in X and charge 100USD/hour Write a bunch of blog spam on X, a lot of it wrong => Leading expert in X and charge 100USD/hour Create a bunch of projects that have more bugs than Swiss cheese has holes => Leading expert in X and charge 100USD/hour There is a story today here that says GitHub is the Instagram of prog…
So if we accept this as baseline reality then what do we do?
Refuse to accept it, and call out the charlatans that do it?
Re: Show HN: Coding Career Handbook
#98Earlier quoted context omitted.
Because that is what sells now. Write a book for Packt on X you are learning as you go => Leading expert in X and charge 100USD/hour Write a bunch of blog spam on X, a lot of it wrong => Leading expert in X and charge 100USD/hour Create a bunch of projects that have more bugs than Swiss cheese has holes => Leading expert in X and charge 100USD/hour There is a story today here that says GitHub is the Instagram of prog…
So if we accept this as baseline reality then what do we do?
Honestly I don't know.
There is so much cargo culting nowadays in software development (agile, GitHub, white board interviews, hacker rank, tdd, add, ci, cd, redux, etc etc) and so many new people (I worked in 3 different React projects in the last 2 years with 3 different teams. Only one required something as complex as Redux (and most likely Flux or other simpler state libraries would do). You know what? All of them had redux. It is what they learned in the latest blog post by ReactHipsterMainMain.com so that is what you see.
If you are 25/28 years old and a start up CTO (?!?) and you spent your 20s in university and doing open source code and putting shit in GitHub, you value that and try to hire for that. Thus, this is well known and bootcamps and the likes teach people to put every little shit in GitHub to show they are 'passionate' about software development and has done a lot of projects.
Even the take home projects. From experience, most companies have the same variation of the project. For iOS this is usually show a screen with data from an API, tap something and show details, also from an API. You can find millions of these small projects all over GitHub. But somehow they still ask for them. A few years ago I was so tired of this that I created a generic project and then a script that would take a JSON file and would generate the Swift Models, as well as API calls->transform to Model, and I would just need to create 2-3 functions to configure each cell depending on the data. I haven't seen any junior developers do something like this in their jobs. There are more and more classes, view controllers, components, stores etc. The abstraction thinking just isn't there yet. But they act like they know everything and have all the answers because of GitHub stars or whatever they are called.
I am all over the place with this reply, I am sorry. Just after years and years of seeing this, more and more I don't think soft development is for me if it is just to become the Instagram of the geeks.
Re: Show HN: Coding Career Handbook
#99Earlier quoted context omitted.
I am not downvoting you, but (if GP is accurate) 2 years of professional experience is nothing, and to be an authority is laughable. To say he established himself as a developer marketer, ok, but damn, really? 2 Years? When I started to work 2 years was junior level developer, and now they are authorities?? I quickly checked his writings. I am not trying to put him down, they are ok, but completely different than wha…
You forget the whole React field is like 5 years old. And this book is aimed at beginners, not folks like us with decades in the field.
Well, actually 7 years old so there is that.
But it doesn't matter if it is react or iOS or prolog. If you think about it, a CS degree, that covers a lot of topics, is minimum 3/4 years. And when you get out of uni you are considered an intern/junior. But now, bootcamps/web tutorials, people think that ater 2 years they become an authority on something.
I deal with these people everyday. They know 'react' inside out, but anything higher level (how to organize the freaking code) or how to use any kind of CS algo to solve a problem that isn't in the O(n^n) space because it is 'simple' is beyond them. Which is fine, is something that takes time to learn and know how to use. It took me years.
But 'I'm a senior developer' types with 2 years of experience is ridiculous, and we should call them what they are, liars. (not the GP, again, don't know him, talking in general)
(I don't think a CS degree is needed to be a software developer)
Re: Show HN: Coding Career Handbook
#100Earlier quoted context omitted.
You forget the whole React field is like 5 years old. And this book is aimed at beginners, not folks like us with decades in the field.
Well, actually 7 years old so there is that. But it doesn't matter if it is react or iOS or prolog. If you think about it, a CS degree, that covers a lot of topics, is minimum 3/4 years. And when you get out of uni you are considered an intern/junior. But now, bootcamps/web tutorials, people think that ater 2 years they become an authority on something. I deal with these people everyday. They know 'react' inside out,…
Ok so why would any of that matter? He’s giving you advice on how to get a senior title fast, not on react or CS or engineering at all. Just the fast title acquisition.
Who’s better for that advice? Someone who did it in 2 years or someone who took 10?