/tech/ - Technology★

>>951950 (OP)

The name “GNU” is a recursive acronym for “GNU's Not Unix!”; it is pronounced as one syllable with a hard g, like “grew” but with the letter “n” instead of “r”.

This is a recording of Richard Stallman saying “GNU” and another with a short explanation about how GNU was named:

· https://www.gnu.org/audio/gnu-pronunciation.ogg

· https://www.gnu.org/audio/how-gnu-was-named.ogg

>looking for a job

As an independent/freelance or as an employee? Any job will do, or you've got something particular in mind? I used to work in retail and slowly got promoted to IT when they realized I had the skills and it was more convenient for them to handle computer-related issues internally (I began to code frontends for their abominable database system, fix and maintain computers, and teach employees how to use common softwares)

In general, I'd say do anything you could later use to illustrate your skills to your future employer (something practical). Anything that forces you to keep a regular schedule and respect deadlines is also a good pick. When you actually start looking for a job, make sure whoever is going to read your resume understands what your skills can bring on board (in general, most "human resource" managers have no idea what C# means and don't understand how valuable programmers can be to non-tech companies). But again, what are you looking for?

"I decided to spend a year masturbating to anime rather than working on my career"

Tell it like it is OP. Don't make it sound like you did anything DEEP and INSIGHTFUL. You just said fuck it and were lazy.

Spend a year larping as a white house insider, start your own YouTube channel, sell t-shirts.

>>951988

Then you get range-banned, evade your ban because you are smarter than the faggot that I perpetrate, and keep shitposting.

>>951950 (OP)

Realize life is meaningless and move the SEA and start a web business and they just hang by the pool until you die.

>>951984

>Do you think actively contributing/maintaining an open-source project is a good indicator for this?

If you can demonstrate your involvement, then yes. Write a journal, a blog or build your own website and use it as a professional portfolio. Explain what you're working on, why, how, and justify what you're doing.

If you're trying to appeal non-tech companies (administrative/office work), show that you master the tools they need, write scripts or design templates - and again, explain why, how, and justify what you're doing.

You have to stay active. Impose a deadline for each update and stick to it.

Every time someone tells you to be enthusiastic in your cover letter, they forget to add "when applicable"; if you're just going to mop the floor or fulfill some minor task, both you and your future boss are smart enough to know it is nobody's dream. Don't overdo the pandering. However, communicating on your work is a safer and more honest way to show your motivation.

If you have the opportunity to go to formations or seminars, do it. Try to meet people who could be interested in your skills (plenty of unskilled people sit through these things for the social aspect, in hope they meet "someone who knows how"), exchange ideas with others and see what advises they can give you.

>>951950 (OP)

break your conditioning

>>952019

>I think it could provide context to non-tech people/orgs.

Good idea, that's perfect!

>What is your view on certifications/bootcamps?

Honestly, I have no view on bootcamps. Maybe the social aspect is worth it? I don't know.

Regarding certifications, I think they mostly shape your professional path. You can either pick a low-level job (completely unrelated to your skills) and cut yourself the job you actually want (if you are helpful enough in a specific field, it's only a matter of time before someone "important" notices that you can do something nobody else on the team can do, and maybe keeping you in that low-level job is a waste of resources). Or, you could try the direct path and aim for the job you want, in which case a certification will be helpful. But in that case, expect an unforgiving screening (it's not all gloom-and-doom, just prepare yourself accordingly).

I don't think certifications are a must-have for smaller companies or non-tech because it's unlikely they even know what the damn paper is about. Basically, they only want the best return on their money and they're not going to invest in a cat-in-a-bag. If you can convince the HRM that you can provide a better infrastructure or come up with better tools that will allow the company to take more customers, be more efficient, and improve the quality of life of its employees, you'll get the job.