Juan

14.7K posts

Juan banner
Juan

Juan

@juangilopez

Machine Learning Engineer and Manager at @FactoredAI

Medellín, Colombia เข้าร่วม Ocak 2014
833 กำลังติดตาม356 ผู้ติดตาม
Juan รีทวีตแล้ว
Will Ahmed
Will Ahmed@willahmed·
You have no experience. You’ve never started a company. You’ve never had a full time job. Nike is going to kill you. You’re a kid. You don’t have technical skills. You shouldn’t build hardware. Apple is going to kill you. You can’t build hardware. You can’t measure heart rate non-invasively. Athletes don’t care about recovery. Under Armour is going to kill you. It won’t be accurate. You don’t listen. You’re an ineffective leader. You can’t recruit great talent. You’re going to have to pay every athlete. You can’t measure sleep non-invasively. It’s too expensive to research. Athletes are a small market. The product costs too much to make. The product costs too much to sell. Your valuation is too high. Consumers aren’t going to want it. Hardware is too hard. You should measure steps. Fitbit is going to kill you. You can’t build a marketing engine. You can’t raise enough money. You need a real CEO. Google is going to kill you. You can’t be a subscription. You can’t build a brand. You can’t do consumer in Boston. Your valuation is too high. You shouldn’t make accessories. You shouldn’t make apparel. Lululemon is going to kill you. You can’t predict Covid. Stay in your niche. You are going to run out of money. You can’t build a health platform. Amazon is going to kill you. You can’t measure blood pressure. You can’t get medical approvals. The market is too small. You don’t understand AI. The market is too competitive. It won’t work internationally. The supply chain is too complicated. You can’t build an AI. You can’t raise enough money. It’s too competitive. Healthcare isn’t going to want it. … Just keep going ✌️
Will Ahmed tweet media
English
1.1K
2.8K
23K
2.4M
Juan รีทวีตแล้ว
Arpit Bhayani
Arpit Bhayani@arpit_bhayani·
I have seen more systems struggling because of wrong code than slower ones. The fact remains, most engineers optimise too early. About 8 years ago, my principal engineer once told me: Performance is almost always the last thing you should be thinking about. As an SDE-2, this did not make sense :) After a few follow-ups, I understood why he meant that. The order that actually matters is this. First, is the code correct? Does it do what it is supposed to do? Second, can someone maintain it six months from now without wanting to quit? Third, is it fast to read and write? Only after all three does performance even enter the conversation. The reason this order exists is simple. A fast, unmaintainable codebase is a liability. A performant-but-wrong system is worse than a slow, correct one. You cannot optimise your way out of a bug. Now, this is not universally true. Databases, high-frequency trading systems, and real-time embedded software are domains where performance is a first-class concern from day one. But those are the exceptions, not the default assumption you should bring to every PR. What is certainly true is that for most codebases, premature optimisation adds complexity, reduces readability, and solves a problem that does not exist yet. So, write correct code first. Then clean it. Then, only if the profiler gives you a reason, make it fast.
English
37
55
842
37.3K
Juan รีทวีตแล้ว
Daniel Hnyk
Daniel Hnyk@hnykda·
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
English
309
2.3K
9.4K
5.7M
Juan
Juan@juangilopez·
La derecha se beneficiaria mas de entender el porque petro y la izquierda gano gran parte del voto popular, en vez de antagonizarlo. Si fueran estrategicos entenderian que hay un sector olvidado que reclama derechos y sienten que su unica opcion es la izquierda.
Español
0
0
1
35
Juan รีทวีตแล้ว
Abhishek Singh
Abhishek Singh@0xlelouch_·
The best software engineers I know all have this in common: • Start coding with big dreams at 21. • Get rejected by companies at 22. • Take the job they could get at 23. • Spend 2 years fixing bugs and writing CRUD APIs. • Feel behind when others post big salaries online. • Try to switch at 26. • Fail interviews at 27. • Realize tutorials were not enough. • Finally learn CS fundamentals, system design, databases, networking, and how real systems break. • Start building better at 29. • Become dangerous at 31. And change their family’s future by 35. With their sharpest years still ahead. Software engineering is not a sprint. It is a long game of skill, patience, and staying in the fight. Keep going.
Unfiltered@quotesdaily100

The most successful people I know all have this in common: • Dream of a business at 21. • Launch and fail at 23. • Go back to a job at 24. • Try again at 26. • Fail again at 28. • Lose money and confidence. • Learn everything that failure taught you. • Build something real at 31. And change your family's future forever at 36. With your best years still ahead. Entrepreneurship is not a race. It is a test of patience. Keep going.

English
64
278
4.6K
478.4K
Juan
Juan@juangilopez·
No entiendo esa obsesion con los principios inamovibles en los políticos, esta bien cambiar de opinion a la luz de nueva evidencia
ÚltimaHoraCaracol@UltimaHoraCR

#ElGranReto2026 | “Yo no hago acuerdos sobre la base de volverme lo que no soy (…) yo no creo en la política que convierte a la gente en lo que está de moda”, dijo la candidata Paloma Valencia sobre las líneas rojas de Juan Daniel Oviedo para ser su fórmula vicepresidencial. Vía @laurad_duarte caracol.com.co

Español
0
0
0
20
Juan
Juan@juangilopez·
Muy contento por juan daniel oviedo
Español
0
0
0
111
Juan รีทวีตแล้ว
Rituraj
Rituraj@RituWithAI·
We often over-index on "Process" and "Best Practices" (Agile, OKRs, complex architectures) and lose sight of the actual product. "Common Sense" in engineering is rare because it requires you to ignore the corporate playbook and just ask: "Does this actually help the user, or are we just shipping complexity to look busy?"
English
0
2
3
2.8K
Juan รีทวีตแล้ว
vx-underground
vx-underground@vxunderground·
One way to differentiate a real nerd from a phony nerd is their appreciation of stuff For example, someone may share an idea, or proof-of-concept, which illustrates something which is unusual A nerd will appreciate it for it's documentation and appreciation that someone has shared this finding A phony nerd will almost immediately, without hesitation, question the applicability of the thing being presented Dawg, not everything has to have a purpose. Sometimes things are fun. Sometimes it's cool to do shit, just do to do shit. Not everything has to be for profit, or progress, or whatever the fuck else. I've done so much useless stupid bullshit just because I thought it was interesting. I've seen nerds share weird ass notes on something they reversed on Windows that basically no one uses or gives a shit about, and I love it and appreciate it. You can just do things bro The unknown is cool and badass. Explore it If it's known and you wanna explore it, do it anyway so you can experience it yourself Just fuckin have fun idfk
English
65
156
1.9K
119.5K
Juan รีทวีตแล้ว
Gergely Orosz
Gergely Orosz@GergelyOrosz·
"Hiring pure backend engineer and expecting them to do non backend stuff IMO is wrong" Sigh. Any capable intern/new grad picks up whatever new technology is needed to get the job done. If you, as an *experienced* engineer, refuse to do so: you're less capable than an intern
AnonGirder@AnonGirder

@dave_reis @GergelyOrosz Not hiring a backend engineer is entirely ok Hiring pure backend engineer and expecting them to do non backend stuff IMO is wrong even in startups. Startups doesn't mean a pure backend engineer should be made to work on things he has no clue about/not interested in.

English
92
78
1.5K
329.4K
Juan
Juan@juangilopez·
I enjoy @dieworkwear content, it's refreshing to see stuff that goes beyond what gets you money or the last tech trend. I never thought that something as mundane as clothing could yield so many interesting reflections around history and culture. Great escape from the routine
derek guy@dieworkwear

Any time I talk about a wealthy person's outfit, someone in the comments is quick to reply: "They're rich, you think they care?" No one has to care about my opinions or clothes, regardless of net worth. But let's talk about the connection between wealth and aesthetics 🧵

English
0
0
1
156
Juan รีทวีตแล้ว
Neo Kim
Neo Kim@systemdesignone·
System Design Interview's Red Flag List. If you’re making these 5 mistakes… we need to talk:
English
5
22
302
54.3K
Juan
Juan@juangilopez·
@carorestrepocan Interesante lectura. Seria muy bueno si puedes compartir tus fuentes, me interesa concer más. Siempre me he pensado que a Bolivar, sin quitarle méritos, lo han tergiversado a conveniencia.
Español
0
0
0
40
Carolina Restrepo Cañavera
Carolina Restrepo Cañavera@carorestrepocan·
En una época en la que muchos insisten en rendir culto al mito, conviene volver a los hechos. Francisco de Paula Santander no fue solo un militar brillante, fue el arquitecto civil de la república. Mientras Bolívar soñaba con coronas vitalicias y centralismos autoritarios, Santander construía instituciones, escribía leyes, formaba jueces y defendía la separación de poderes. Santander no necesitó una espada para gobernar: le bastó la Constitución. Fue él quien consolidó el Estado de Derecho, quien impulsó la educación pública como fundamento de la ciudadanía, y quien entendió que sin legalidad no hay libertad verdadera. Bolívar murió en el exilio, rechazado por Colombia. Santander, en cambio, regresó por el voto, no por la fuerza. Gobernó sin pretender divinizarse. Y cuando se retiró, no dejó himnos ni bustos: dejó escuelas, códigos y un país que empezaba a creer en las leyes, no en los caudillos. Ese es nuestro verdadero libertador: el que nos enseñó que libertad sin ley es solo otra forma de tiranía.
Carolina Restrepo Cañavera tweet media
Español
375
2.1K
6.3K
327.4K
Juan รีทวีตแล้ว
Gergely Orosz
Gergely Orosz@GergelyOrosz·
Linux is the most widespread operating system, globally – but how is it built? Few people are better to answer this than Greg Kroah-Hartman (@gregkh): Greg has been a Linux kernel maintainer for 25 years, and one of the 3 Linux Kernel Foundation Fellows (the other two are Linus Torvalds and Shuah Khan). Greg manages the Linux kernel’s stable releases, and is a maintainer of multiple kernel subsystems. We cover the inner workings of Linux kernel development, exploring everything from how changes get implemented to why its community-driven approach produces such reliable software. Greg shares insights about the kernel's unique trust model and makes a case for why engineers should contribute to open-source projects. Watch or listen: • YouTube: youtu.be/7WbREHtc5sU • Spotify: open.spotify.com/episode/7vrfBK… • Apple: podcasts.apple.com/us/podcast/how… Brought to you buy: • @WorkOS — The modern identity platform for B2B SaaS. workos.com@TrustVanta  — Automate compliance and simplify security with Vanta. vanta.com/pragmatic Check out all of our current sponsor and their offerings: blog.pragmaticengineer.com/podcast-sponso… ---- One of the most surprising things I learned about Linux: although 4,000 developers contribute to the project from 500 companies per year, and has around 800 kernel maintainers, the project is run with email, git... and that's about it! No dedicated project managers, no regular meetings across the group. It's a truly fascinating and unique model (and only applies to the Linux kernel project: not to Linux distributions.) We go into more detail about this topic with Greg in the podcast as well.
YouTube video
YouTube
English
6
81
604
51.3K
Juan รีทวีตแล้ว
Vante🦇
Vante🦇@railedbyvante·
Lil bro think he Batman
English
326
1.1K
13.6K
10M