61–70 of 92 posts
Type Raleigh or Durham or North Carolina into the region selector and it gives bad or no results, but navigate over NC on the map and there are jobs listed
Yeah, I'm not going to assume Raleigh, NC is more important than all the other Raleighs in the world. But it is bizarre that I can get Fort Raleigh City, NC and not the actual capital of the state. Pretty neat tool, but the region search needs work.
I feel like this is completely backwards. To me this feels like 'I love using this kind of hammer so let me find all the jobs where I can use this hammer I love to use.' I'm actually not interested (at least not primarily interested) in that. I'm more interested in what are you building? What problems are you solving? I'd rather search by that and then see what their tech stack looks like and filter down to the ones…
> Focusing on technology feels like putting the cart before the horse. Every language has its own ecosystem, its own frameworks, its own culture its own set of "best practices". Good luck learning them all.
Earlier quoted context omitted.
If software does not solve problems, what are you getting paid for, exactly? For the weight of the line of code?
What is a plumber paid for? You tell him you'd like a sink installed somewhere and he installs it. He isn't paid more if the sink is used to wash the hands of surgeons operating on orphans or never used it all. He is paid on the basis of, you want a sink and he knows how to install them.
Are we really discussing this?
Earlier quoted context omitted.
If software does not solve problems, what are you getting paid for, exactly? For the weight of the line of code?
You don't get paid for solving the problem, you get paid for transforming the problem using software such that people become dependant on software to "solve" it. Now you can charge them for it. You can also insert software into places where no problems have been yet identified, make them dependant on it and then charge them for it.
Yes, the entire software industry is akin to crack dealers.
Earlier quoted context omitted.
I know a lot about security, but I did not know about owasp10 before today. I knew about all the listed security issues in owasp 10 and how to mitigate them, but not about the list itself. Perhaps look at what candidates actually know instead of $nextCoolList?
Yep, most of those items baked into framework already, plus practices we've heard about in the list, but not need to know the name "owasp".
Earlier quoted context omitted.
What is a plumber paid for? You tell him you'd like a sink installed somewhere and he installs it. He isn't paid more if the sink is used to wash the hands of surgeons operating on orphans or never used it all. He is paid on the basis of, you want a sink and he knows how to install them.
You want the sink because, presumably, not having a sink - or having a broken one, or an ugly one - is a problem for you. Are we really discussing this?
I feel like this is completely backwards. To me this feels like 'I love using this kind of hammer so let me find all the jobs where I can use this hammer I love to use.' I'm actually not interested (at least not primarily interested) in that. I'm more interested in what are you building? What problems are you solving? I'd rather search by that and then see what their tech stack looks like and filter down to the ones…
For me, Python always provides the shortest path to solving problems programmatically. It is the best thing you can use to prove a concept before you build something. Python sits appropriately in the middle of pseudo code and something performant. I get to solve unique problems rapidly. That fits my philosophy. If you are comfortable in using something why not get paid to do that. I am open to learning new things particularly Typescript but I am just comfortable in a Python environment more than a JavaScript or any other environment.
The catch with all that is that I am more fitted for contract roles as opposed to full time jobs. For the employer hiring based on tech introduces too much rigidity. They want contractors and experts for that.
Earlier quoted context omitted.
If software does not solve problems, what are you getting paid for, exactly? For the weight of the line of code?
You don't get paid for solving the problem, you get paid for transforming the problem using software such that people become dependant on software to "solve" it. Now you can charge them for it. You can also insert software into places where no problems have been yet identified, make them dependant on it and then charge them for it.
Earlier quoted context omitted.
You don't get paid for solving the problem, you get paid for transforming the problem using software such that people become dependant on software to "solve" it. Now you can charge them for it. You can also insert software into places where no problems have been yet identified, make them dependant on it and then charge them for it.
This guy knows how business works. If everybody think hard enough, software is not needed in lots of situation. The market is all about forced solution, probably plus some network effect, social value yada yada that keep it alive.
Yea, if you think hard enough, you can have communications sent by horse, instead of by electronic mail.
I feel like this is completely backwards. To me this feels like 'I love using this kind of hammer so let me find all the jobs where I can use this hammer I love to use.' I'm actually not interested (at least not primarily interested) in that. I'm more interested in what are you building? What problems are you solving? I'd rather search by that and then see what their tech stack looks like and filter down to the ones…
> I feel like this is completely backwards. To me this feels like 'I love using this kind of hammer so let me find all the jobs where I can use this hammer I love to use.' I'm actually not interested (at least not primarily interested) in that. I'm more interested in what are you building? What problems are you solving? Same for me. I can learn whatever tech stack you're using (if need be). I want to know about your…