Earlier quoted context omitted.
As an independent contractor for the past two years, It hasn't been much of a grind finding and retaining customers. You have to put some work in, sure, but I don't feel it's particularly onerous. Never had to take someone out to dinner or cold call. People need software development skills and generally like it when you find them. As for never being paid on time - I think the most late it's ever been has been 2 weeks…
> As an independent contractor for the past two years, It hasn't been much of a grind finding and retaining customers....I think the most late it's ever been has been 2 weeks. When it's you who's gettind paid a bit late... it's manageable. When those late payments affect people you have to pay... it's a whole different game. I've been on both sides of this and it's great when it works, and bad when it doesn't. Buildi…
Times are great for programmers now. How does it end?
561–570 of 611 posts
Re: Times are great for programmers now. How does it end?
#562Earlier quoted context omitted.
I have NO university degree and ZERO affiliation with anything remotely FAANG (I'm based in Europe, where relatively few people work for FAANG). There are no globally recognisable names on my CV. I am still the highest paid person I personally know - by a rather high margin, because of my experience as a software engineer. Since I dropped out of university almost 20 years ago, I have been consulting and contracting,…
Good for you. I have experience with all 3 of those technologies and it's nearly impossible to even get an interview.
Re: Times are great for programmers now. How does it end?
#563I feel like we have so much leverage and don't use it at all. We're still attending stand-ups every day with non programmers telling us when we can and cannot refactor. It's nuts to me that a skilled profession - that not many can do - lets themselves get micro-managed like this. If anyone has read Developer Hegemony , I'm fully on board with that general premise - we start operating like lawyers with partnerships, a…
> We're still attending stand-ups every day with non programmers telling us when we can and cannot refactor. I highly disagree with this. For some reason, many devs seem to think they are somehow better than everyone else, that they are the most important part of any team, that no on besides them can have any insight on timelines, or budget, on which features are or aren't important. News flash - all of the above is…
If your workspace has shit smeared on the walls, you don't ask if you can clean it up. You just do it.
Re: Times are great for programmers now. How does it end?
#564As far as I'm concerned, the ride stops when the masses realize how easy the profession actually is. You can take any office worker and train them to an entry level competency in 3-5 months, when they will get a job for at least $75k. They are then in a new career path and will soon make 100k. I find it impossible to convince non devs that being a developer is easy. They can't fathom why we get paid so much if it's e…
I used to think the same. I too find my job to be easy and sometimes feel like we have this secret in the software industry that our work really isn't all that difficult these days, with so many hard problems having already been solved. I say this as a senior SDE in big tech. But, after watching a close friend, who is brilliant—she had gone to a top 30 college undergrad and had top SAT scores—go to a coding bootcamp…
Re: Times are great for programmers now. How does it end?
#565Earlier quoted context omitted.
Starting an agency is the easiest part. Then after that comes the never ending grind to find and retain customers, who will never pay on time, refuse to budget time for frivolities like "testing" and "refactoring" and who will mercilessly shop out the work to as many of your competitors as they can find. Developer agencies have existed for decades and the reason that not everybody is rushing to work for them is becau…
As an independent contractor for the past two years, It hasn't been much of a grind finding and retaining customers. You have to put some work in, sure, but I don't feel it's particularly onerous. Never had to take someone out to dinner or cold call. People need software development skills and generally like it when you find them. As for never being paid on time - I think the most late it's ever been has been 2 weeks…
A few years back I tried forming an LLC with a couple friends, but they both have full-time jobs and they keep getting promoted, so it's never gone anywhere, and we're talking about winding it down. I'd love to try again with someone who is already independent and is ready to try something bigger.
I haven't read Developer Hegemony, but another great book about the dynamics of such a partnership is Managing the Professional Service Firm by David Maister. It's pretty dense, but it's full of great ideas.
I went into freelancing in part to avoid becoming a manager, and I think with the right kind of partnership you could still practice your craft while still helping to lead a small team of people---or maybe even just mostly collaborating with other partners. The Maister book has helpful things to say here about whether your firm focuses on work that is repeatable & leveragable (e.g. making Wordpress sites) vs unique, challenging, and done mostly by partners (which sounds more fun to me).
I'm in Portland, Oregon, if anyone is interested in talking about something like that. :-)
Re: Times are great for programmers now. How does it end?
#566Earlier quoted context omitted.
Good for you. I have experience with all 3 of those technologies and it's nearly impossible to even get an interview.
This is honestly baffling to me, I can't imagine how this can be. I get multiple emails each week from recruiters looking for that exact skill-set, and this is AFTER I've tried extra hard to unsubscribe from all such emails.
https://leetcode.com/problems/reverse-nodes-in-k-group/
Maybe I'm just too stupid.
Re: Times are great for programmers now. How does it end?
#567Earlier quoted context omitted.
I think the key point for me is that once you control for all common human flaws, the developer is still far better suited to make an executive decision regarding a technology concern than anyone else on the team. I recently made the mistake of deferring to the anxieties and fears of non-developers for so long that I almost forgot how we got to where we are today or what my true capabilities are. You know exactly wha…
> I recently made the mistake of deferring to the anxieties and fears of non-developers for so long that I almost forgot how we got to where we are today or what my true capabilities are. Ouch, dude, you didn't have to stab me in the heart. But yeah, 100% same. I am just now, at the age of almost 42, starting to finally crawl out of that. I am ashamed that it took me most of my life and career but oh well. > I think…
Re: Times are great for programmers now. How does it end?
#568Earlier quoted context omitted.
For non-tech people the code should be a black box they shouldn't know the internal details. In terms of refactoring there is no way to give a Cost Benefit analysis as that's too subjective. This should be a maintenance cost that's factored into the project at a high level. So you would say there a X days per year (normally about 20%) of the working days of the year spent on maintenance. Company I'm at has this and i…
> For non-tech people the code should be a black box they shouldn't know the internal details. Ideally, yes, though in practice this usually breaks in various ways, especially when problems occur. E.g. the President of a country probably doesn't need to be a firefighter, but if there's suddenly a massive fire, I assume he'd need to be briefed in far more detail to help call shots around the type of response. > In ter…
In other cases, it is more important to get things right and continual refactoring is the fastest way to find an acceptable architecture to a novel problem.
In either approach, when speed is of essence, a limited scope helps avoid either producing insurmountable technical debt, or an unterminating research rabbit hole, respectively.
Re: Times are great for programmers now. How does it end?
#569I feel like we have so much leverage and don't use it at all. We're still attending stand-ups every day with non programmers telling us when we can and cannot refactor. It's nuts to me that a skilled profession - that not many can do - lets themselves get micro-managed like this. If anyone has read Developer Hegemony , I'm fully on board with that general premise - we start operating like lawyers with partnerships, a…
Re: Times are great for programmers now. How does it end?
#570I feel like we have so much leverage and don't use it at all. We're still attending stand-ups every day with non programmers telling us when we can and cannot refactor. It's nuts to me that a skilled profession - that not many can do - lets themselves get micro-managed like this. If anyone has read Developer Hegemony , I'm fully on board with that general premise - we start operating like lawyers with partnerships, a…
My role is to ensure that the overall project and deliverable is on track. I will ask questions to clarify statements made in standup. I expect questions coming to me about requirements, intent, and timing. If there are problems with external teams, I will do my best to work out that blocker. I don’t dictate how the devs do their work as long as they are able to deliver the features that were agreed on. If that is not going to happen, we can have a discussion about why and what adjustment needs to be made.
If more refactoring needs to be done, we can have that conversation. Talk to me about the cost and benefits of the refactoring and the impact on deliverables. It may be worthwhile accepting a delay in deliverables now. It may also be that those particular deliverables are important enough that the refactoring may need to be deferred even if the ultimate cost is higher. Those kinds of trade-offs cannot be done only by one part of the team but need to be weighed by the whole team.
This kind of open and respectful discussion is part of a well functioning team. If you are not getting that then raise this as a problem in retrospectives because it needs to be addressed.