what are we even doing here man
-
what are we even doing here man
@foone [lists MS Word as a skill]
-
@foone Do you have experience in Boolean (data structure)?
@ben False
-
what are we even doing here man
@foone i did do that before yea
-
what are we even doing here man
@foone having not enough experience in Arrays (data structure) i think
-
what are we even doing here man
@foone now the qualifications for this job are pretty stringent, we're gonna need you to have used a keyboard before.
-
what are we even doing here man
if someone doesn't have experience with arrays, then they don't have enough experience with programming to hire them to program for you. they are still on page 9 of the programming book
-
if someone doesn't have experience with arrays, then they don't have enough experience with programming to hire them to program for you. they are still on page 9 of the programming book
Specifically, this one.
The Usborne guide to Better BASIC: a beginners guide to writing programs (1983) -
Specifically, this one.
The Usborne guide to Better BASIC: a beginners guide to writing programs (1983)See? Page 9. Arrays.
-
what are we even doing here man
@foone so that is why I, as a teamlead that followed a webmaster course 25 years ago, gets asked to do senior Drupal dev jobs? I sure know my Arrays from my Booleans.
-
See? Page 9. Arrays.
Usborne released a bunch of their old 80s programming books for free a while back, and they're all just a gem:
-
what are we even doing here man
@foone I'm a little perturbed it reads: "in arrays" and not: "with arrays", to be honest.
-
@foone so that is why I, as a teamlead that followed a webmaster course 25 years ago, gets asked to do senior Drupal dev jobs? I sure know my Arrays from my Booleans.
@Klara yeah apparently that's all you gotta know these days to be a developer
-
@foone Reminds me of when a lawyer accused me of stealing someone else's graphics tech because we both used the same technology of "bilinear filtering." OK my friend you go ahead and bring that up in court be my guest.
-
if someone doesn't have experience with arrays, then they don't have enough experience with programming to hire them to program for you. they are still on page 9 of the programming book
@foone@digipres.club i will take this opportunity to once again tell tale of the time i worked on an embedded device with a firmware written in C, roughly a 150,000-line codebase on a little STM32 chip
the original author of the code base did not, in fact, seem to understand what an array was.
the device communicated to another device bolted to the same machine, using MODBUS. with potentially up to 10,000 MODBUS registers storing data, but realistically only a few actually in use.
the file defining the structure where the data was stored for the registers simply made a struct, with elements starting at "reg0" and incrementing up to "reg10000". the implementation file was just as bad.
this is why the codebase was roughly 150,000 lines. it should have been perhaps 5000.
the code used a small function that did pointer math in order to actually access the register, usually, unless it was referenced directly in code, or sometimes used a macro instead.
none of this was even the worst offense within the codebase. -
Usborne released a bunch of their old 80s programming books for free a while back, and they're all just a gem:
@foone I learnt everything I know from Computer Fun… I still have the book.
-
if someone doesn't have experience with arrays, then they don't have enough experience with programming to hire them to program for you. they are still on page 9 of the programming book
@foone Arrays are when it stars getting fun. I think if someone's starting out and they get excited learning about multi-dimensional arrays, that's a good sign.
-
@foone@digipres.club i will take this opportunity to once again tell tale of the time i worked on an embedded device with a firmware written in C, roughly a 150,000-line codebase on a little STM32 chip
the original author of the code base did not, in fact, seem to understand what an array was.
the device communicated to another device bolted to the same machine, using MODBUS. with potentially up to 10,000 MODBUS registers storing data, but realistically only a few actually in use.
the file defining the structure where the data was stored for the registers simply made a struct, with elements starting at "reg0" and incrementing up to "reg10000". the implementation file was just as bad.
this is why the codebase was roughly 150,000 lines. it should have been perhaps 5000.
the code used a small function that did pointer math in order to actually access the register, usually, unless it was referenced directly in code, or sometimes used a macro instead.
none of this was even the worst offense within the codebase. -
what are we even doing here man
@foone im not a developer, but I can say in good conscience that I do
-
Usborne released a bunch of their old 80s programming books for free a while back, and they're all just a gem:
@foone I've posted this page from Usborne's guide to jargon before and commented that I'd be happy if all programmers were as computer literate as grade school students in the 80s.
-
if someone doesn't have experience with arrays, then they don't have enough experience with programming to hire them to program for you. they are still on page 9 of the programming book
@foone Hey, functional programmers need jobs, too!
-
B bogwitch@social.data.coop shared this topic
