Bash For Loop Array: Iterate Through Array Values
#!/bin/bash
# declare an array called array and define 3 vales
array=( one two three )
for i in "${array[@]}"
do
echo "$i"
done
#!/bin/bash
# declare an array called array and define 3 vales
array=( one two three )
for i in "${array[@]}"
do
echo "$i"
done
Hablemos de los contables. Cuando llegaron las hojas de cálculo, pese a la revolución que supuso para la contabilidad, los contables no desaparecieron. Al contrario: aumentó la cantidad de gente que hacía tareas contables. Lo que sí cambió fue la satisfacción de esas personas toda vez que el software se quedó con la parte interesante del trabajo interesante (análisis) y los humanos con lo repetitivo (introducir datos en un formulario).
La IA ya programa por nosotros. El placer de crear desde cero seguirá existiendo, pero ocupará menos espacio. El rol del humano va a pivotar hacia la revisión de software producido por la máquina, afinar prompts e integrar sistemas (quizá las tareas de devops y soporte sean una suerte de último foso de defensa para roles técnicos). ¿Les va a gustar? Probablemente no, probablemente desprecien esa labor tanto como desprecian actualizar tickets en Jira, porque la magia del rol que han hecho durante décadas, la resolución de problemas, el reto intelectual, va a ser resuelta por la máquina. La parte intelectualmente reconfortante se la queda la máquina, justo como le pasó a los contables.
OUTLINE:
(00:00) – Introduction
(00:58) – Sponsors, Comments, and Reflections
(08:48) – Programming – early days
(26:13) – JavaScript
(36:32) – Google Chrome and DOJ
(44:19) – Ruby programming language
(51:30) – Beautiful code
(1:09:31) – Metaprogramming
(1:12:52) – Dynamic typing
(1:20:10) – Scaling
(1:33:03) – Future of programming
(1:50:34) – Future of AI
(1:56:29) – Vibe coding
(2:05:01) – Rails manifesto: Principles of a great programming language
(2:29:27) – Why managers are useless
(2:38:48) – Small teams
(2:44:55) – Jeff Bezos
(3:00:13) – Why meetings are toxic
(3:07:58) – Case against retirement
(3:15:15) – Hard work
(3:20:53) – Why we left the cloud
(3:24:04) – AWS
(3:33:22) – Owning your own servers
(3:39:35) – Elon Musk
(3:49:17) – Apple
(4:01:03) – Tim Sweeney
(4:12:37) – Fatherhood
(4:38:19) – Racing
(5:05:23) – Cars
(5:10:41) – Programming setup
(5:25:51) – Programming language for beginners
(5:39:09) – Open source
(5:48:01) – WordPress drama
(5:59:18) – Money and happiness
(6:08:11) – Hope
One reason programmers dislike meetings so much is that they’re on a different type of schedule from other people. Meetings cost them more.
There are two types of schedule, which I’ll call the manager’s schedule and the maker’s schedule.
1. Avoid var Keyword: A Relic of the Past
Before ES6, the var keyword was the primary way to declare variables. However, it had some quirks and limitations that often led to unexpected results and made debugging more challenging.
In modern JavaScript, we generally avoid using var and instead opt for let and const, which offer more predictable and block-scoped behavior, making your code easier to understand and maintain.
2. let: Variables That Can Change
Use the let keyword to declare variables whose values you might need to change later in your code.
3. const: Constants for Unchanging Values:
If you have a value that shouldn’t change throughout your program, use the const keyword.
A good rule of thumb is to use const by default and only switch to let if you know you’ll need to reassign the variable’s value later.
The ultimate goal of every software developer should be to write reliable code. Nothing else matters if the code is buggy and unreliable. And what is the best way to write code that is reliable? Simplicity. Simplicity is the opposite of complexity. Therefore our first and foremost responsibility as software developers should be to reduce code complexity.
I’m not criticizing Alan Kay’s OOP — he is a genius. I wish OOP was implemented the way he designed it. I’m criticizing the modern Java/C# approach to OOP.
Many dislike speed limits on the roads, but they’re essential to help prevent people from crashing to death. Similarly, a good programming framework should provide mechanisms that prevent us from doing stupid things.
Yes, Functional Programming has a strong mathematical foundation and takes its roots in lambda calculus. However, most of its ideas emerged as a response to the weaknesses in the more mainstream programming languages. Functions are the core abstraction of Functional Programming. When used properly, functions provide a level of code modularity and reusability never seen in OOP. It even features design patterns that address the issues of nullability and provides a superior way of error handling.
I think that it is not right that OOP is considered the de-facto standard for code organization by many people, including those in very senior technical positions. It is also unacceptable that many mainstream languages don’t offer any other alternatives to code organization other than OOP.
Perhaps you have wondered how predictable machines like computers can generate randomness. In reality, most random numbers used in computer programs are pseudo-random, which means they are generated in a predictable fashion using a mathematical formula. This is fine for many purposes, but it may not be random in the way you expect if you’re used to dice rolls and lottery drawings.
RANDOM.ORG offers true random numbers to anyone on the Internet. The randomness comes from atmospheric noise, which for many purposes is better than the pseudo-random number algorithms typically used in computer programs. People use RANDOM.ORG for holding drawings, lotteries and sweepstakes, to drive online games, for scientific applications and for art and music.
Stories from people on their coding journey.
Specify the type of commit:
feat: The new feature you’re adding to a particular application
fix: A bug fix
style: Feature and updates related to styling
refactor: Refactoring a specific section of the codebase
test: Everything related to testing
docs: Everything related to documentation
chore: Regular code maintenance.[ You can also use emojis to represent commit types]
Separate the subject from the body with a blank line
Your commit message should not contain any whitespace errors
Remove unnecessary punctuation marks
Do not end the subject line with a period
Capitalize the subject line and each paragraph
Use the imperative mood in the subject line
Use the body to explain what changes you have made and why you made them.
Do not assume the reviewer understands what the original problem was, ensure you add it.
Do not think your code is self-explanatory
Follow the commit convention defined by your team
We inspire women to fall in love with programming.
Django Girls organize free Python and Django workshops, create open sourced online tutorials and curate amazing first experiences with technology.
Django Girls is a non-profit organization and a community that empowers and helps women to organize free, one-day programming workshops by providing tools, resources and support. We are a volunteer run organization with hundreds of people contributing to bring more amazing women into the world of technology. We are making technology more approachable by creating resources designed with empathy.
During each of our events, 30-60 women build their first web application using HTML, CSS, Python and Django.
The Blockly library adds an editor to your app that represents coding concepts as interlocking blocks. It outputs syntactically correct code in the programming language of your choice. Custom blocks may be created to connect to your own application.
MIT App Inventor is an intuitive, visual programming environment that allows everyone – even children – to build fully functional apps for smartphones and tablets.
First of all, don’t use var. There are a few differences between var, let and const and the most important one to me is that let and const remove the error-prone behavior with variable hoisting.
Creemos que al final seréis capaces de utilizar R para cargar datos, arreglarlos, hacer gráficos y tablas, e informes en Rmarkdown.
Intentaremos que el curso sea fundamentalmente práctico, perso se necesita un mínimo de conocimiento sobre el funcionamiento de determinadas cosas y también hay que conocer un poco la jerga que se utiliza en la comunidad R.
En lugar de presentar todos los pormenores de R de manera lineal, se irán presentando distintos aspectos de R conforme se vayan necesitando; es decir, no vamos a presentar R como un lenguaje de programación sino como una herramienta para hacer análisis estadísticos.
Syntastic is a syntax checking plugin for Vim created by Martin Grenfell. It runs files through external syntax checkers and displays any resulting errors to the user. This can be done on demand, or automatically as files are saved. If syntax errors are detected, the user is notified and is happy because they didn’t have to compile their code or execute their script to find them.