Laeserin @Laeserin - 5mo
As many of you know, I've been back in IT work, after a decade-long baby break and a 3-year logistics apprenticeship, and I'm starting to feel almost-competent again. This is everything I needed to learn, or relearn, in order to know WTF is going on. nostr:naddr1qvzqqqr4gupzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqqxnzde38ycnydpsx56nxd3ctk2cv7
And then I'd sit them down at a computer, with an IDE open, and ask them to write and execute a program that prints "Hello World" five times. Give them 10 minutes and no googling or AI.
I know that sounds really easy, but I bet some of the candidates wouldn't be able to do it.
Original list was longer, but I like round-numbered lists, so I deleted stuff. Autistic moment! 😂
The entire list sounds pretty easy, actually, but I doubt you'll find anyone doing the job already, who can answer all of those questions competently. Most probably can't even really explain what agile is, but they're making 6-figures to sit around a brown table and bitch about how stupid the programmers are. Source: Every business analyst I encounter IRL that wasn't formerly a test automator, dev, sys admin or similar.
End rant.
If you can find someone who also understands project management, corporate accounting and tax laws, customer service practices, documentation, and marketing... Hire them on the spot.
We had someone apply to be a DBA once, and we handed them a piece of paper and a pencil and asked them to write SQL to connect all of the entries in the table Students with the appropriate entries in the table Grades, and explain to us what would happen, if some students had no grades. And they couldn't do it and got upset and left.
Ha ha! Just realized that you'd probably get some people writing five print statements. Maybe up it to 50. 😂
🤣🤣🤣
Yeah, they all love the regular reviews and increments. Let me check up on y'all shadowy supercoders, and give me something to click. 😂 We had reviews and quick releases BEFORE agile, people. 🤦♀️
mleku ✝Ⓐ☯︎ @mleku - 5mo
in my first session with my young colleague, fresh out of CS at Berkeley he wrote a greeter that asks for a name and then does this hilarious amnesia thing after using it, was funny he annoys me sometimes but he's good
😂
I bet a lot of analyst candidates would be like "What is an IDE?" I'm completely shocked, by the stuff I've experienced, and I'm hearing horror stories from other people, including from major engineering firms. People with IT certifications or even CS degrees who can't manage Hello World... is a thing.
Nobody expects an analyst to be a good programmer, but we should expect them to be able to use the basic tools, write a simple program or some easy SQL statements or a flowchart, write a well-structured bug report or change request, etc. Otherwise, they will literally have no clue what anyone is talking about at the daily and you need to ask yourself what you need them for.
I meant those who are applying to be a BA for a software team. Although, I find it difficult to imagine why anyone would bother getting into IT without even trying to program one time.
I'd probably ask you to write a simple bash script.
i think that the most important baseline skill for anyone working with IT should be: can you search a filesystem for files with a given extension, sort them in descending order and output the parent directory name, and then append a string to each one, and then create an empty file with this name in the current working directory? this requires grep, sort, cut, sed and xargs, an understanding of pipes, ultra basic regex, and i could have done this for you back in 1995 - stuff i learned by using man on a free dialin shell account
oh i forgot it includes the basic use of find as well
and yes of course performing the test you are allowed to use --help and man
Oh, yeah, that sounds good. 👀 And regex would be good for BAs, too. Need that, constantly. And maybe spreadsheets.
As a set of articles joined in a collection, like I'm doing. Writing down a list of everything you want to cover and then slogging through it, when you're bored.
This seems like the best way to write a technical book, because you can replace the individual articles, when they become obsolete. More like a website, than a book, but could be "printed" as an ePub or a PDF.
