Nafrondel @Nafrondel@octodon.social

@Vanessa Ikr. It's like the "Holy fluff, Google translate unexpectedly invented a language! Machines are evil o_o" thing last year.
Idk if it helps, but the tank thing as I learned was that they were using a very basic in memory machine vision learning (not ANNs), and taught it friendlies on runways, and enemies on sand. Because the tanks were minor artefacts, it couldn't tell friend from foe in the field. Just airbases from sand. So it was never put near a tank, and wasn't a mystery.

@Wintermute21 Asking questions is what juniors are there for. One of the defining characteristics is being able to perform tasks with close supervision and direction - not being expected to make decisions.
If they're too cheap to hire someone at a higher level, and too lazy to give you enough design etc. to not need to ask questions, then that's on them and not on you!

@Wintermute21Oh jeez. That is not how to run any business.
The only time a junior should be asked for estimates is in an agile planning meeting. And they should have an entire team helping them out.
And if you're struggling to keep up, that means they haven't explained and defined the task correctly. You shouldn't be expected to have the skills to get the requirements out of them either.

@Vanessa Oh gosh. Everyone has to do that at some point u.u
For serious - ANNs have been around far too long for them to be a mystery.

I'm starting to appreciate Spring.
It makes liberal use of reflection and black magic. And that is terrifying.

@Wintermute21 I get them feels. When I started out, my "mentor"'s go to phrases were "Just do it. It's easy!" and "Why are you doing that? It's impossible!". Which was never helpful.
What's your background been and experience like so far?

@Wintermute21 Yeah... They seem to have been used to either old school command line only, or unmanaged projects.
Or they're Unix coders and refuse to use anything other than VIM because masochist.

@Wintermute21 For a bit of insight - the interview process at my workplace includes them sitting the applicant in front of a laptop loaded up with a project. The project has some bugs. The applicant has to find and fix the bugs. Buuuut most have never used the IDE (despite it being the current standard for Java) or used a build tool like Maven, and end up staring at the screen and freaking out.

@Wintermute21 (Sorry to throw so much homework at you ;~) )

@Wintermute21 I'd love to say it'll be easy... but it's a sharp learning curve.
It's also worth at least writing one thing in each major IDE if you can.
But if it helps - everyone in your position is feeling lost too! So if you can find your way before an interview, you stand a great chance.

@Wintermute21 :D
Paying bills is always helpful.
Even if you don't contribute to an open project in any meaningful way, just having practical experience of using tools like Jira and Github /git; reading existing code; and building it using gradle / maven / ant will put you head and shoulders over almost any other Jr. applicant.
One alternative would be to sign up to github and use it to implement some of the book's examples and kill two birds with one stone!

@Wintermute21 What level are you looking at?
If you already know and understand the basic algorithms you're likely to hit up against, you won't need it except to remind yourself.
If you don't already know them, then the role may be above your level.
The best thing to do in reality may be to join some open source projects and see if you can tackle some bugs and add some smaller new functionality.
Understanding the full life cycle is far more valuable than a list of algorithms.

@vfrmedia @TQ Not sure about the rationality... ;) But for serious - as long as you're not scared of Vim and Bash, all should be good. There are some good step by step guides out there too which give the major commands you're likely to want.
For beginners, Github does most of the hard work, such as setting up new branches and giving you the commands you need to get started.

@TQ (Sorry to butt in)
Yes, git is a good idea. I think github's free to use for open projects?
Just note that it's a sharp learning curve! But worth it. I'm currently using it for a Node.js project.
It integrates well with things like Jira, as you can have a separate branch for each task/bug/story.

A toot by any other name would be a tweet.

@aedison Comedy hero at work 💖

Just logged in on a desktop for the first time.
Holy scrollbars Batman.

@avrydison How to Pokémon

@DaveHiggins Oops. Forgot to say "rich" there.
So on to the next point - according to the Torys, earning £70k is barely enough to live on now that houses cost hundreds of Ks. Therefore should be taxed even less.