I'm bewildered as to why a CEO would have any opinion on version control at all. Or why you'd ask a CEO whether you could use one. It's like a builder asking a construction company CEO if he can hold a hammer lower in his hand and that CEO forbidding it. Can someone explain?
A good friend of mine worked for a small company whose CEO also tried hard to convince him that introducing version control was wrong.
Of course, this same CEO also didn't see any problem with the fact that the password field in the login form was never checked against the database, because who would know someone else's login name?
I'm not exactly at a fortune 500. I'm one of two developers at my company and it would be hilarious to me if my CEO (who seems like a nice enough guy) even knew what version control was.
Small company, maybe a dozen people total, only tech-adjacent, not a strictly tech company. The CEO (which, for a company this size, probably also meant owner and perhaps sole board member) and maybe a fee other people at most had built the site in question.
The dev says himself that he is a junior, and it is very likely that the CEO of a tech firm has more than junior-level experience in technical matters. Even if he doesn't, it is still fine for a junior to ask his superiors for advice.
- Hey Joe CEO, which version control do you think I should use?
- None, that's an order!
It was a small (tech-adjacent, not strictly tech) company, and if memory serves right the owner built some of the site in question himself. I dont know that my friend reported directly to anyone inbetween, at least not when it came to technical matters anyway.
Listen. If not using version control is a problem for you, you're already more hirable than a lot of developers I've seen. Learning is always important but don't use that to procrastinate.
You don't have to go straight to the best job in the world. Just find something better (and do your homework to verify) and take it.
I'm in a small city, where not much work is available. I need to pad my resume a little more to make the work I do more attractive, but the reality is that LAMP devs aren't in high demand near me. I apply to several jobs daily, but not much is around. I'd appreciate pointers on how to improve my prospects, but the last place I interviewed was a seedy adult entertainment company, and I wouldn't have taken an offer if they begged, simply for personal reasons.
You said you're 18, you're young and hopefully don't have kids, so apply in other cities as well.
Yeah it's scary. But if the job is good enough, and the pay is good enough, then you've got to figure out why your bullshit reason for staying where you are outweighs both your mental health and your career prospects.
God, at 18—or hell, at 22—showing the fuck up and not seeming entirely incompetent is a big deal. Show up, be engaged, do both consistently, and anyone who's not a total piece of crap will be all over giving you more responsibility and mentoring you up to bigger and better things. Total pieces of crap may still be interested, but it'll be in exploiting you (as in current situation). Oh, and ask questions. No one expects you to know diddly-squat, so ask away. Ask about stuff that's not part of your job description at all. People will tell you all kinds of stuff, and, incredibly, the whole exchange will make them like you more.
Phenomenally small amounts of give-a-shit go a long way for youngsters. It's basically their superpower, if they're willing and able to use it.
I know a bunch of remote-hiring places and if nothing else I'd be happy to help you figure out what to learn (and, probably, how to approach it) to GTFO. Email is in my profile.
Leave the city. It doesn’t end well if you stay... unless you can get remote work (even then it’s risky), but you definitely have to leave the company ASAP
> I need to pad my resume a little more to make the work I do more attractive
A word of caution: One of my objectives as an interviewer is to drill into a candiate's resume to see if they actually did what they said they did. Its OK to talk up your accomplishments. But don't claim expertise in language X or technology Y unless you are prepared to answer some questions about it.
I interviewed a guy who's masters work was in the field I did my doctoral work in. I think I'm the only one in the company who knows anything about the particular topic, and considering that the role was far removed from that topic, it was a very unlikely coincidence. However, when discussing his research, he mostly missed the mark. It wasn't enough to sink his application as at the masters level I wouldn't expect him to know it nearly as well as I do, and he was ultimately hired. But, you never know who you're talking to.
But this conversation has been about them saying they need to learn more before they can get a new job, and me replying that they shouldn't use that as an excuse to procrastinate. Thus the `need to pad my resume` comment.
Magento shops are always looking for LAMP devs. A national recruiter told me they place PHP devs at the big Magento shops without the job ever existing.... There must be a Magento agency in your city?
I've been there. Run.