A Venezuelan Journey

Lessons Learned Working at Large Corporations as Tech Lead

Fri, 05 Dec 2025 22:47:45 -0300

The Good

One thing I liked about working at large companies is that what you do really has a big impact— whether good or bad, it affects real users. You have to make sure you deliver the best product you can. It’s your time to shine and show how you can help customers have less friction when using the company’s goods and services.

Sure, this comes with other great things like meeting new people, building teams, and getting to know smart people—all paddling in the same direction.

There are also perks like insurance benefits and small food bonuses on top of your salary.

I must also say that you often get to work at financial sector buildings with the company logo at the top. Yes! You feel kinda proud having reached that level. It gives you some kind of social currency status at the same time.

You start going to meetings where you can catch a glimpse of the CEO or CTO and think, “One day I’ll be there”—what a lie!…

The Bad

Not all, but most big companies—precisely because they’re so big—usually don’t have a clear internal path or process. It’s like the wild west at times, but you get used to pushing ahead.

No one is there to help you. It’s like everyone is in a 10K race every single day, trying to meet impossible deadlines to reach that milestone.

You start understanding that going out for lunch isn’t so smart after all. Then you understand why people stay and eat at their desks at work.

At the same time, when you get home, you feel like your soul has been drained from all those impossible tasks that need to be done before yesterday.

You start learning about something called “office politics,” and you learn it the hard way. Because you’re there alone. Like getting blamed for something over email when the person nicely agreed via chat but stabs you in the back over email. Or people who want to move up the ladder and try to do it by stepping on your shoulders with knives in your back. You end up not trusting anyone.

The Ugly

I don’t know about other people’s experiences, but mine was complete hell. Many times I ended up seeing the sunrise, working because I needed to finish something where the deadline wasn’t well planned—and the people below suffer the consequences.

Feeling sick and still needing to go to work, or even vomiting, and your boss saying it’s normal and please go back to work. Going to the dentist and getting asked to hurry up so you can get back to work. And the cherry on top of the banana split: getting contacted by HR and asked why you didn’t go to the End of Year company celebration. And answering that you were working long shifts and weekends. And their answer is just “Ok. Thanks.”

Conclusion

Always remember not to trust anyone—they are work colleagues, no more than that.
Set boundaries. If they’re asking you to work late or weekends for the company’s benefit and there’s no compensation for it, don’t do it.
Your boss only uses you like a tool. There is no such thing as “family.”
Document evidence of bad behavior. Usually companies delete chats and emails monthly or every two weeks. Use your phone to save evidence of bad practices.
Do the best you can without burning yourself out.
Sometimes companies are great, but sometimes people are the problem.
Don’t worry about being fired—you don’t control that. Worry about what you can control.
Big companies are great to learn and learn fast, then move out. It’s a real meat grinder that will drain your soul and energy.
Choose health over money. It’s not worth the money when you get sick and have to spend it all getting your health back.
Don’t outshine your boss.
Make your boss look smart with your knowledge—you’ll become important.
Always, always! leave and confirm important information over email, never over chat, talk etc. people will use this against you, if you do not have proof of it.

Tragicomedia un desarrollador promedio

Sun, 18 May 2025 18:09:11 -0400

Aclaratoria

En contraposición, todo depende de quién sea el desarrollador y de la persona que escribe este blog: alguien que soñaba con ser ingeniero petrolero… pero terminó de secretaria. No es la verdad, aunque se le parece. El propósito es exponer situaciones que tienen mucho y nada que ver con lo biográfico, pero que nacen de la vida cotidiana; al final, todo es una caricaturización pensada en voz alta.

Intercalando un diálogo interior libre de culpas y formalismos, se percibe un pequeño aire de disfrute: un goce sabroso en cada situación que compartiré.

Inteligencia Artificial y el ser humano

Hoy constatamos que la modernidad ha traído consigo la multidisciplinariedad y otros giros conceptuales de excelente gusto. Ha quedado claro que no se trata de pasar la vida en una carrera apoteósica para ser el mejor, sino de resetear los parámetros. Esta vertiginosa carrera llamada inteligencia artificial nos invita a detonar cada chispa intelectual en el momento preciso, nada que ver con esos códigos monótonos copiados de Stack Overflow o Foros del Web (se me cayó la cédula), sin la más mínima certeza de si llegarían a tiempo.

Así, de forma elocuente y sin rodeos, la IA se presenta auténtica y siempre capaz de sorprendernos. Hace años me dijeron una frase que llevaba esperando repetir: «bien instruido». No significa que sea perfecta.

Como seres pensantes, andamos como pollos sin cabeza buscando la próxima gran idea y, entonces, descubrimos que esa frase de oro escrita hace milenios por algunos sabios —«que la vida del hombre es un proceso de búsqueda infinito»— nosotros, los postmodernos, la hemos vulgarizado.

¿Vulgarizado? Porque vivimos un proceso de búsqueda sin fin, pero de tonterías: el mejor IDE, el teclado ergonómico, el monitor curvo.

Dando por hecho que lo que necesitamos es un chatbot; como peluqueras que se peinan unas a otras por falta de clientela, o palomas en las plazas que creen haberse saciado con cualquier migaja.

¿Cuál será la verdadera interfaz IA? ¿La definitiva, la que usemos a diario? ¡Quién sabe! Imagino algo heroico, al estilo Blade Runner con un toque Apple Fan Boy al que estamos acostumbrados. Todo para pedir una pizza un sábado por la noche, cuando no queremos cocinar. Lo imagino como ese problemilla de tener la tarjeta en el teléfono y que no pase por falta de saldo, y que la IA responda al estilo Clint Eastwood: «breve como amor de cortesana».

Superarnos a nosotros mismos es absurdo. Caemos en el delirio de pensar que una IA puede sugestionar en un instante, brindándonos recomendaciones que orbitan en nuestra mente sin que nos demos cuenta.

Este fenómeno humano genera un problema: llegamos sin manual de instrucciones para operar nuestro propio ser. Que nuestra vida no se origine de una iniciativa propia, sino del descarte. Aquí es donde la verdadera IA debería ayudarnos: a encontrar ese propósito vital sin recurrir a un psicólogo de 20 dólares que categoriza todo como si fuera un sectario, etiquetándonos de «psicópata narcisista» si no encajamos.

En mi opinión, la IA no debe limitarse a ser un agente, un chatbot o un generador de código, sino el medio para que cada persona se reencuentre consigo misma: un manual operativo del individuo que, además de arreglarnos la vida, puede beneficiar a los demás. Porque, al buscar nuestro propio bien, invadimos el espacio ajeno y entorpecemos la búsqueda del otro.

Al grano

Ante cualquier situación, no nos preguntemos cómo resolverá la IA, sino qué nos dice nuestro manual operativo. Como quienes acuden a las «traqueas» del hipódromo con la gaceta hípica en el bolsillo trasero, buscamos en sus páginas la elocuencia que nos guía.

El único inconveniente será preguntarse de qué vivirán Paulo Coelho, Deepak Chopra, Muñeca Geigel, Og Mandino o Lair Ribeiro.

¡Que se dediquen a programar!

Write Messge on LCD Screen With i2C using Rust Language and ESP32-C3

Fri, 05 Apr 2024 22:47:45 -0300

Rust stands out as an excellent language, particularly for developing embedded systems. Considering its prowess in this domain, why not embark on a project to create a program that displays messages on an LCD screen? Specifically, we’ll utilize an I2C LCD Screen, along with an ESP32-C3 microcontroller, leveraging Rust’s Standard Library and the Espressif Framework.

Leveraging Rust for Firmware Development In contrast to Arduino, Rust offers distinct advantages by eliminating the need for cumbersome wrappers. With Rust, you dive straight into interacting with hardware at a low level.

Let’s kickstart this endeavor by setting up a template project. To begin, ensure Rust is installed. For detailed installation instructions, visit Rust’s official website." go to https://www.rust-lang.org/

Let’s get our hands dirty

cargo generate --git https://github.com/esp-rs/esp-idf-template.git --name esp32-c3-lcd

Navigate to the ’esp32-c3-lcd’ folder and locate the ‘/src/main.rs’ file.

Now, confirm that you can successfully build the ‘hello world’ program by running the following command:

cargo build

Dependencies

After confirming the successful build of the ‘hello world’ program, it’s time to update our dependencies in the ‘Cargo.toml’ file

[dependencies]
log = { version = "0.4", default-features = false }
esp-idf-svc = { version = "0.48", default-features = false }
ssd1306 = "0.8.4"
embedded-graphics = "0.8.1"

Make it work

Now, let’s update the ‘main.rs’ file with the following code

use embedded_graphics::{mono_font::{MonoTextStyle, ascii::FONT_10X20}, pixelcolor::BinaryColor, text::Text, geometry::Point, Drawable, primitives::{Circle, PrimitiveStyle, Primitive}};
use esp_idf_svc::hal::{peripherals::Peripherals, i2c, units::FromValueType, delay::FreeRtos};
use ssd1306::{Ssd1306, size::DisplaySize72x40, rotation::DisplayRotation, I2CDisplayInterface};
use ssd1306::mode::DisplayConfig;

fn main() {

    esp_idf_svc::sys::link_patches();

    let peripherals = Peripherals::take().unwrap();
    let scl = peripherals.pins.gpio6;
    let sda = peripherals.pins.gpio5;

    let config = i2c::config::Config::new().baudrate(FromValueType::kHz(400).into());
    let _i2c = i2c::I2cDriver::new(peripherals.i2c0, sda, scl, &config).unwrap();
    let interface = I2CDisplayInterface::new(_i2c);

    let mut display = Ssd1306::new(interface, DisplaySize72x40, DisplayRotation::Rotate0).into_buffered_graphics_mode();

    display.init().expect("Screen Error");
    let style = MonoTextStyle::new(&FONT_10X20, BinaryColor::On);

    loop {
        // Hello World Text
        println!("Showing hola");
        Text::new("HOLA", Point::new(0, 17), style).draw(&mut display).unwrap();
        display.flush().unwrap();
        display.clear_buffer();
        FreeRtos::delay_ms(2000);

        println!("Showting mundo");
        Text::new("MUNDO", Point::new(0, 17), style).draw(&mut display).unwrap();
        display.flush().unwrap();
        display.clear_buffer();
        FreeRtos::delay_ms(2000);

        // Create Circle
        println!("Showing circle");
        Circle::new(Point::new(36,20), 15).into_styled(PrimitiveStyle::with_stroke(BinaryColor::On, 1)).draw(&mut display).unwrap();
        Circle::new(Point::new(28,18), 3).into_styled(PrimitiveStyle::with_stroke(BinaryColor::On, 1)).draw(&mut display).unwrap();
         Circle::new(Point::new(25, 38), 3).into_styled(PrimitiveStyle::with_stroke(BinaryColor::On, 1)).draw(&mut display).unwrap();

        display.flush().unwrap();
        display.clear_buffer();
        FreeRtos::delay_ms(2000);

    }
}

Upon inspection, you’ll notice that we’ve created a text and a circle. It’s important to configure your baud rate, as well as your SCL and SDA GPIO pin peripherals to ensure proper functionality.

Execute!

Now, execute the following commands:

cargo build && cargo flash && cargo flash monitor

Books I'm Reading for 2024

Mon, 05 Feb 2024 22:47:45 -0300

Here’s the text with a bit more flavor I’ve got a stack of books I’m committed to diving into

Efficient Linux at the Command Line’ by Daniel J. Barret

Talks about how to excel your skills when using the terminal

link: https://a.co/d/3ROEBBL

The Rust Programming Language’ by Steve Klabnik & Carol Nichols

Shows different ways to work with rust language from medium to advance

link: https://a.co/d/crc7wGG

David Rockefeller Memoirs’ by an Author I can’t wait to discover

Shows David’s life from point of view, and shows his family evolution

link: https://a.co/d/1Ciz0QF

Mañana en la Batalla Piensa en Mí’ by the talented Javier Marias

It’s a nice funny story of two random people meeting and when they are about to have sex the girl dies in front of him; and he doesn’t know what to do.

link: https://a.co/d/dOPJfHY

Seeing like a State’ by the insightful James C. Scott

Shows a way governments when doing their best to enhance people’s lifes, they make it worse sometimes.

link: https://a.co/d/5dHIrC3

Conclusions

It’s quite a diverse collection, carefully curated to enrich my knowledge and enhance my reading experience. If I come across any exciting new titles, you can bet I’ll update this post with them.

Working at Large Company in Latin America as TL

Fri, 24 Nov 2023 12:55:36 -0300

OnBoarding

Like any other company there is a onboarding path you must follow. this can be; configuring your VPN, Credential setup, etc..

After this. you dont really start coding, about a week later; after you meet your peers. at first is really interesting. and the reason of this is due to the fact that you only know the tip of the iceberg.

after this you start getting basic tasks, and doing some shadow work with other collegue or supervisor. this is just to get you hands on making your first baby steps inside the company.

after you have’ learned to walk. you start getting more tasks and the flow starts going faster. and you know that the garden is not as greener as you expected it to be on the interview for the role.

Day to day

Here is when you start seeing all improvements you can make from your side to the company. due to the fact you are not intoxicaded with the culture and whereabouts of the company.

You become more of a nice solving problem machine, and this is well accepted by your peers and your supervisor. untill you start asking the right questions about. “Can we implement this?”, “Is possible to apply some of this ideas in the short term?” and some times the answer is yes, and most of the time is a big “nope”

then you start to realize that to build up your team and set everything, so your developers can get done their work. They need to have everything ready to roll. and the issue here is due to the fragmentation of responsabilities; things get reallly slow. And I mean really slow. sometimes. moving code from developers machine to a simple sandbox can be so tedious due to authorization and corporate hirarchy that many people must go in sync with the task. Like we would be doing some kind of musical where everyone is dancing on a choreography.

And this is just for the development stage at early stages of the development procress of the project.

Friends and Family

You start having a nice time with your work collegues, some of them will be removed from the project due to performance, others will be simply laid off; So don’t attach to much to people, because you don’t know when they’ll go away. Remember you are there because your work it’s worth something for what you deliver. this myth of the family is a total lie. just do your work, be nice and “always be prepared to leave”.

Rush hour

When things get tough you need to excel your way of solving problems, since you need to keep focus on so many things at the same time, its key to take notes. even the minor thing can become important in the future. I recommend to use Obsidian or Hugo CMS to store your ideas and make them searchable. remember you should trust your notes, and not your memory.

On the hirarchy ladder you are in a position of a leader with no authority, you cannot do so many things and still you need to deliver, so persuation is key on this role. Others will push you up to do so as quick as possible. because your bosses boss needs to gain some policital token. So he will ask you to work late, do extra hours (sometimes no extra pay) and do other’s people work and sometimes do the work of more than 2 people.

Becarefull and reconsider this. Because this could mean your health in the success of a company that could laid you off at any time; without a “Thank for your effort”.

Paper Developer

Yeap, you become a developer on paper, because you wont spend much of your time developing code, but you still need to keep track of all the internal code decitions and check on pull requests often. as well in urgen times code without any context on things you didn’t code on the first hand. and very quick!. Not to mention that if one of your developers goes on vacation; good luck with that!. you’ve just wont the lottery. because it’s time to do the work of 2 people.

Hello meetings

Sometimes you get meetings to solve issues or incomplete conversation subjects that were not solved. that could simply be a Email or small message over Microsoft Teams. You will have sometimes to decide weather you attend one meeting or another. and spend long hours of talking and presenting your updates and at the same time be eyes on your work and other’s peoples work. fast!!!!

Working Tools

you could be lucky to get the latest tech, nice macbook pro m2, not my case. but you have to start using boring tools and unusefull tools that are not related to your personal tools such as github, gitlab, kubernetes, linux. you would be lucky to have documentation. if not then you must take my advice on ** Rust Hour ** and not allowed to install tools that are not licensed such as docker desktop, because for companies it’s another story. Microsoft Outlook to check inmense amounts of emails stack together with no common order. and still keep your mental sanity.

Conclussions

Enjoy your journey of this nice way of becomming a Technical Lead at a big company. It comes with small wins. lots of politics, extra hours, lots of meetings. Being a Technical Lead it’s kind of a middle brother. you always get what’s left from your older brother.