9
atheist
3y

Skills required for the job I'm interviewing for:
C++, sql, cuda
Skills I have:
C++

I think it's going fairly well so far.

Comments
  • 3
    You could probably learn the rest on the job, as long as you're upfront about your experience
  • 4
    Cuda is just c++ with fancy for loops and an ORM can go a long way!

    You've got this!
  • 1
    Sql is its own world, but the model is very intuitive so you should be able to pick it up fairly quickly to a decent level.
  • 2
    Cuda? Should be easy to pick up the basics; the rest you can learn on the job. It’s basically C++ with some libraries and defs and things.

    But SQL? Ezpz.

    Quick lesson:
    SELECT *
    FROM table1 AS t1
    LEFT JOIN table2 AS t2
    ON t1.column = t2.column
    WHERE t1.idk = 12
    AND t2.idc = 13
    LIMIT 10
    ORDER BY t1.id;

    That’s decently complex and should be pretty intuitive just from reading it. The sql keywords are in caps here, and split into separate lines for ease of reading. They don’t have to be, but it makes the syntax more obvious. Keywords in caps is also a pretty common convention, though the multi line is mine. I normally vertically align them, too :)

    Anyway: Table1 and table2 are tables with t1 and t2 as aliases (shorter names used only in the query). This query joins table1 and table2, meaning it or pulls data from both tables at once for all rows where the column “column” is identical in both tables, then it pulls all columns from this, then filters the results and only keeps the rows where “idk” on table1 is 12 and “idc” on table2 is 13, then sorts the table by the “id” column from table1, and finally only returns the first 10 rows.

    The internals of what the DB does when executing this query include reading both table schemas (their column names and types), creating a temporary table from both of these, performing two full table scans, a full pass over the temporary table to sort it, and a partial scan to retrieve its first 10 rows.

    … why did i write all of this?
    Must be the alcohol.
    Go read a tutorial!
  • 1
    If you understand how databases work, SQL is really easy to understand. And if you don't know how databases work, its easy to learn too. Good luck!
Add Comment