I Think, therefore I Code is a quick introduction to pseudo code as a tool to help developers find solutions before writing a single line of code

1. I Think,
Therefore I Code
An introduction to pseudocode
Silvia España Gil
01

2. Silvia who?
Did a corporate communications degree.
Changed career at 33.
PUBLICIST
01.
One year ago didn't know anything about
coding. Now I code in Swift
02.
DEVELOPER
I love playing. My first one was lemmings,
on diskette! Currently playing Elden Ring.
03.
GAMER
02

3. What do we
programmers do?
We develop algorithms that allow us to provide
solutions.
Algorithms allow us to define a series of steps that,
when executed, will result in the resolution of a
problem.
They are basically a recipe to follow.
Solve problems
03

4. characteristics
Algorithm
04
They indicate exactly what we
want to do
Precise
They solve a concrete and
defined situation or problem
Specific
Its results will always be the same
Defined
Specify the sequence in which the
steps should occur
Organized
They have a beginning and an
end: the solution
Finites

5. 05

6. 06
Pseudocode
Simple
Texts with non-formal language,
developed with the idea of
solving a problem
Free format
It can be developed with the
amount of detail that we want or
with the stucture that better suit
us
Prequel
It is done before we start writing
our code as a way to organize but
also to make troubleshooting
easier

7. Perks
07
Anticipate possible
errors in the data
flow
Define the steps to
follow in the
development of our
algorithm
Save
development
time

8. 08
These are the guidelines that we need to comply with. These are executed from top to bottom -
almost always -
Normally the statements are verbs in infinitive and will always have the first capital letter: Enter,
Show, Print, Request, Increase etc
Structure: Statements

9. Conditionals and
other structures
09
We can go further by adding other
figures such as conditionals or other
structures.
To do so we should use "if" - "if else",
"for", "switch" as we need.
In these cases it is recommended to use
the same word that we would use in the
language to avoid misunderstandings
Structure:

10. Start and end
10
Pseudocode must, like algorithms, to
have a beginning and an ending.
In the event that we have conditionals,
we should also write down where our
condition ends. So we can easily
understand the extent of them.
This will also make our pseudocode
easier to understand when dealing with
more complex problems
Structure:

11. Demo
11
Language
Simple language,
statements as
infinitive verbs
Finite
Marking the start
and the ending of
the pseudocode
Comments
Useful comments
that may help with
later coding

12. Demo
12
Piecewise code
Second layer
pseudocode for
further detail
Conditionals
Use of conditionals
limited by their own
endings

13. There are no rights or wrongs in the use of pseudocode
and it is a really helpful too for developers of any tier.
If your team uses Pseudocode as an approach to solutions,
ask which guidelines they follow and if there are none
find the style that better suits you.
I like to call my style a layered one.
No rights or wrongs
How would
you do it?
13

14. Feel free to reach me through
Gracias!
14
silviaespanagil
silviaespanagil
silviaespanagil
@fischesil