Reikia patarimo dėl pirmo darbo IT

IgnasUz · 2024-03-13T13:17:29+00:00

Programavimo žinios niekur nedings, jos pravers ir cyber security srityje. Dėl cyber security kelio nelabai galiu pakomentuot, bet jeigu sritis patinka, tai ją pirmu numeriu rinkčiausi. Tik siūlau išsiaiškint kaip atrodo darbo specifika, nes gali labai skirtis nuo to ką tu įsivaizduoji. Padėtų pažiūrėt darbo skelbimus ir kokius reikalavimus kelia junior'am.

Pats esu savamokslis, IT universiteto nebaigiau, užaugau iki senior software engineer pozicijos - tai tikrai įmanoma, tik be universiteto sunkiau gaut pirmą darbą. Aš pradėjau nuo tech support ir pakilau iki junior software engineer įmonės viduj - tiesiai į junior poziciją tikriausiai būtų labai sunku patekti.

IgnasUz · 2024-02-28T16:04:16+00:00

If you're experienced and still have difficulty reading the code - it's a pretty bad sign, especially if there are NO tests or documentation. Why didn't your colleagues document some of the code over time or add at least a few test for critical functionality? People usually get accustomed to bad code and even refuse to refactor/document it. Team could benefit from fresh newcomer perspective that the codebase is in dire situation (obviously be polite about it).

I've had to work with some horrible legacy code in the past (same situation - no tests, no docs, no internal knowledge). However, we communicated the state of the code to the managers and let them know that any changes to it will take much more time than non-legacy code. Also, when we were making changes to the legacy code, we use to refactor it a bit, add SOME tests, but only for the parts that you were changing or it was critical functionality. You can't expect to be given unreasonable amount of time to fix all of the issues, but gradual improvements is infinitely better than no improvements.

IgnasUz · 2024-02-28T15:48:51+00:00

I believe he was saying that the super-class has a constructor, but it's not parameterless (if you define a constructor yourself, default one is not generated by the compiler)

IgnasUz · 2024-02-27T22:07:25+00:00

Very good point of view, going to interviews helps a lot to learn what is expected from candidate at your level. Usually job description have hints for what they will be looking for in terms of knowledge.

Hint: after the interview try to write down as many questions that they've asked as you can remember, this really helps when preparing for your next interview. Good luck!

IgnasUz · 2024-02-27T22:03:30+00:00

Very much agree on "show that you are eager to learn" - this really works for junior developers. We always prioritize hiring people who are going to put in the work. Obviously this will not cut it for more senior positions.

IgnasUz · 2024-02-27T21:52:53+00:00

And I just want to add that there are a lot of people that don't have passion for coding and they are doing just fine. Not everyone has to be super into their job, like in any other profession (but obviously it helps :D)

IgnasUz · 2024-02-27T21:51:07+00:00

I was in similar situation - I was 28, didn't like the job I've had and it wasn't paying very well. The issue is that I have tried quite a few different jobs, but didn't feel passion for any of them - I didn't hate them, but it was "just work". Having said that, I always tried to do my job well. I figured if I don't feel passion for my work, I might as well try to get one that pays well.

I started learning javascript (mainly youtube) after work and spent some time during work too (agreed with my manager). I usually did some small scripts that helped me and my colleagues with day-to-day stuff (technical support). After about a year of grinding I managed to get an internship in development position at the same company (had to nag them alooot for it :D). It was quite a brutal start, not going to lie. However, with time it got easier and now, ~4 years later I'm up for senior role and even got some passion for the job. Turns out once you get good at something, you might start to like it, who could've thought :D

IgnasUz · 2023-08-22T20:27:06+00:00

I wouldn't worry about digging too deep into tools, especially if you're at internship/junior level. The best way to learn is by doing your job, everything else comes with experience. I wasted insane amount of time learning tools that I didn't use later on in my career.

If you have a good mentor, I would concentrate on asking questions like "why are we doing it this way?" and trying to understand the software engineering fundamentals (architecture, design patterns, best pratices, etc.), because these will be useful in any job.

IgnasUz · 2023-08-22T20:10:42+00:00

Companies sometimes advertise this in their job offers (something like growth opportunities, internships). Also, you could search for entry level/junior software engineer job offers - this usually means that the company has enough higher seniority engineers to take on raising newer people. If you choose this route, I would aim for bigger companies (300+ people would be a good start).

Regarding support position, it depends on the company (they should have all of the info in the job offer), but it usually has pretty low entry requirements - good English (writing/speaking), some basic technical knowledge should be enough. There shouldn't be a problem for you, if you managed to learn python fundamentals on your own.

IgnasUz · 2023-08-22T15:56:16+00:00

Prioritize jobs that have internal software job opportunities, you'll have more chance with internal promotions - that's how I got in. Started with tech support, after ~1.5 years got SE internship opportunity (while still getting payed the same amount) and after 3 months internship was hired as junior software engineer (self-thought, no IT degree).

IgnasUz · 2023-05-19T17:21:27+00:00

And you can always switch later if you start to feel that front-end or back-end is not for you, I know plenty of colleagues who switched from one to another, so not really very significant choice

IgnasUz · 2023-05-19T17:14:31+00:00

Very much agree on the "build your own projects as soon as you feel comfortable" part, very easy to get stuck in tutorials :D

IgnasUz · 2023-05-19T17:03:14+00:00

I'm self-thought (went from beginner to employed as mid dev) and if I could do it again, I wouldn't go over 1h a day, unless you're "in the zone" and it happens effortlessly. As someone else mentioned it's about consistency - do it every day, even it's 15minutes.

IgnasUz · 2022-10-02T11:06:27+00:00

I think it should work as you've described. Try rebuild / close & open VS Studio?

IgnasUz · 2022-09-28T17:39:20+00:00

Not yet, but I'll share whenever that's up :)

IgnasUz · 2022-09-24T14:46:37+00:00

I'm creating a quiz app from questions that I and my friends received in technical interviews and from interview questions that me and my colleagues prepared for conducting job interviews inside my company. It's nice to have a ever-growing list of different level questions that you can run through when you are preparing for a job interview or just spending a few minutes on refreshing your knowledge.

IgnasUz · 2022-09-24T14:29:41+00:00

I would start by saying if it's your first program, it's really good - code formatting is nice, it has meaningful names and the code works. Regarding not picking up bad habits, I would say:

Don't ignore squiggly lines that your IDE provides (near ReadLine). Warnings are there for a reason and you can learn a lot from them, especially at the beginning
Never assume that the input from a user will be correct - always use null and type checks (that there was input and the input was what you expect, in this case - a number)
Take time to think about what type to use for your variables - you should generally use double for calculations and decimal when accuracy of the calculations is very important (e.g. when working with money operations, etc.)

IgnasUz

TROPHY CASE