Carlos Lemus

442 posts

Carlos Lemus

Carlos Lemus

@carlosaln_dev

Distributed systems expert with a strong background in Cloud/IoT/critical infrastructure. ⚡🌐👾 Staff Engineer @Docker

Indianapolis, IN Katılım Mart 2017
112 Takip Edilen122 Takipçiler
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@mbarneyjr I also think iterating between those two is useful. Elaborate on concept > refine > elaborate it further or branch to new sub-concept > refine > ...
English
0
0
1
17
Michael Barney Jr
Michael Barney Jr@mbarneyjr·
The key though is that second (or Nth) "thoughtful engineering" phase, I can't skip that for anything I actually care about, and especially for anything I deliver to a client. At the end of the day you're still responsible for the things you produce
English
1
0
1
12
Michael Barney Jr
Michael Barney Jr@mbarneyjr·
LLMs have helped the prototype phase both move a lot faster and let me build prototypes with a lot more functionality. After the prototype phase, I understand the domain a bit better, so I can go back and do some more thoughtful engineering and produce a better end product
English
1
0
0
30
Carlos Lemus retweetledi
Farza 🇵🇰🇺🇸
Farza 🇵🇰🇺🇸@FarzaTV·
Just because anyone can build software now doesn't mean software is dead. Anyone can bake bread in their home right now, yet 99% of us still choose to buy it from someone else. Simple products are complex! I will always be happy to pay someone to handle the nuances.
English
280
526
5.9K
584K
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@SyedUmairCodes @fortelabs The reason is likely they're losing customers to Obsidian and the response is to paint their competitor in a bad light rather than providing better data ownership mechanisms which is what many customers want.
English
1
0
1
21
Syed Umair Ali
Syed Umair Ali@SyedUmairCodes·
@fortelabs Seems to me like you're just hating on it for no reason. You don't need to use any plugins (including the built in ones) in order to use the main functionality which is a markdown editor and reader.
English
1
0
1
397
Tiago Forte
Tiago Forte@fortelabs·
I want to debunk the claim that I see a lot around here that Obsidian is "just plain text markdown files" which means "you can take them anywhere and open them with any app" That simply isn't true Yes, maybe the raw text of the notes is markdown, but many other parts cannot be moved elsewhere and opened by other apps: 1. The .obsidian/ directory contains your JSON config with plugins, settings, hotkeys, workspace state, link format, attachment paths – those can't be moved elsewhere 2. Plugin state files – Readwise's path-to-ID map, Templater's settings, Tasks plugin's database, Excalidraw's drawing data – even if plugins can be recreated, these settings cannot 3. .canvas files – JSON, not markdown. They reference notes by path and won't survive a move 4. .base files – JSON-based database/views over your notes. Same path-fragility 5. .excalidraw.md files – markdown wrapper around an Excalidraw JSON blob. Looks like markdown, isn't really 6. The link graph itself – backlinks, graph view, "linked mentions" – all computed from filenames and link references. They survive because the references are in the markdown, but they require Obsidian (or an Obsidian-aware tool) to materialize 7. Plugin-managed folders – Readwise output, Web Clipper output, Daily Notes location, Templates folder. Each is a folder whose contents are owned by an external system tracked in plugin state 8. Sync state – Obsidian Sync, iCloud, Dropbox, Google Drive each maintain their own state about what's where and what's been resolved. Move operations interfere with this state 9. Embedded query results – Dataview queries, Tasks queries, Bases queries. The query is in the markdown; the result is computed live and never persisted So technically you CAN move your files elsewhere, but you'd destroy most of what makes them valuable – the graph, the plugin state, the canvases, the embedded queries, the sync state, and any structural intent encoded in folder placement Which means you're just as locked in to Obsidian as any other "proprietary" app, it's just a hidden lock-in that's obscured by inaccurate marketing Saying "Obsidian is just markdown files" is like saying "your house is just bricks" The bricks are real and moveable – but the architecture, plumbing, and wiring aren't bricks, and those are most of what makes the house function
English
162
23
385
129.5K
Carlos Lemus retweetledi
kepano
kepano@kepano·
@fortelabs The beauty of file over app is you don't have to move your files at all. You can open your Obsidian vault in another file-over-app app. Whatever capabilities that app supports will work. The number of apps that have parity with Obsidian grows every day, and that's a good thing.
English
9
4
367
11.9K
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@mbarneyjr Yeah but tech competence isn't what draws a crowd on this platform anymore 😞
English
0
0
1
15
Carlos Lemus
Carlos Lemus@carlosaln_dev·
Hey chat, find any possible argument for why Markdown files are actually vendor lock in. Don't worry if they're a blatant stretch. Make no mistakes.
Tiago Forte@fortelabs

I want to debunk the claim that I see a lot around here that Obsidian is "just plain text markdown files" which means "you can take them anywhere and open them with any app" That simply isn't true Yes, maybe the raw text of the notes is markdown, but many other parts cannot be moved elsewhere and opened by other apps: 1. The .obsidian/ directory contains your JSON config with plugins, settings, hotkeys, workspace state, link format, attachment paths – those can't be moved elsewhere 2. Plugin state files – Readwise's path-to-ID map, Templater's settings, Tasks plugin's database, Excalidraw's drawing data – even if plugins can be recreated, these settings cannot 3. .canvas files – JSON, not markdown. They reference notes by path and won't survive a move 4. .base files – JSON-based database/views over your notes. Same path-fragility 5. .excalidraw.md files – markdown wrapper around an Excalidraw JSON blob. Looks like markdown, isn't really 6. The link graph itself – backlinks, graph view, "linked mentions" – all computed from filenames and link references. They survive because the references are in the markdown, but they require Obsidian (or an Obsidian-aware tool) to materialize 7. Plugin-managed folders – Readwise output, Web Clipper output, Daily Notes location, Templates folder. Each is a folder whose contents are owned by an external system tracked in plugin state 8. Sync state – Obsidian Sync, iCloud, Dropbox, Google Drive each maintain their own state about what's where and what's been resolved. Move operations interfere with this state 9. Embedded query results – Dataview queries, Tasks queries, Bases queries. The query is in the markdown; the result is computed live and never persisted So technically you CAN move your files elsewhere, but you'd destroy most of what makes them valuable – the graph, the plugin state, the canvases, the embedded queries, the sync state, and any structural intent encoded in folder placement Which means you're just as locked in to Obsidian as any other "proprietary" app, it's just a hidden lock-in that's obscured by inaccurate marketing Saying "Obsidian is just markdown files" is like saying "your house is just bricks" The bricks are real and moveable – but the architecture, plumbing, and wiring aren't bricks, and those are most of what makes the house function

English
0
0
2
76
Michael Ten 🌨🎶🫐🍀
Michael Ten 🌨🎶🫐🍀@iMichaelTen·
@FFmpeg But programming assembly takes thinking. If you are all the best at programming assembly and leading others to program in assembly, then what are y'all?
English
2
0
1
1.6K
I Am Devloper
I Am Devloper@iamdevloper·
what's a good font for someone just getting into fonts
English
24
0
10
10.9K
Carlos Lemus retweetledi
Docker
Docker@Docker·
With @NVIDIAGTC coming up, everyone is talking agents & autonomy. If you’re running coding agents, isolation matters. Docker Sandboxes runs them in microVMs so you can experiment without reshaping your machine. Run agents freely, safely: bit.ly/4unyQph
English
1
3
18
3K
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@mbarneyjr Because they’re not trying to be productive. They’re trying to win socially in the moment. Dropping a full LLM response into a thread serves a few psychological functions: 1. Outsourcing authority People treat the model like a neutral expert. Posting the whole response...
English
1
0
1
18
Michael Barney Jr
Michael Barney Jr@mbarneyjr·
I don't understand how one could copy an entire LLM response, yeet it at someone in a message thread, and expect that to be productive in any way
English
1
0
0
31
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@mbarneyjr Yeah. The fact that type hinting wasn't added until like 3.5 proves your point, and even then it's not required :-)
English
0
0
1
11
Michael Barney Jr
Michael Barney Jr@mbarneyjr·
@carlosaln_dev Yeah it’s possible to get it to use type annotations and write better, but it’s showing how type safety is often an afterthought in python projects as a whole
English
2
0
0
13
Michael Barney Jr
Michael Barney Jr@mbarneyjr·
It seems like virtually no python developers care about type safety, 90% of the python code LLMs generate is not type safe, even if it's working in a project with plenty of type annotations/minimal use of Python's "any" types
English
1
0
0
39
Carlos Lemus retweetledi
Josh Kale
Josh Kale@JoshKale·
The Pentagon just accepted from OpenAI the exact SAME terms they banned Anthropic for… this story is insane: Anthropic: “We won’t let our AI be used for autonomous weapons or mass surveillance.” Pentagon: “Unacceptable. You’re banned.” Trump: “Every federal agency must stop using Anthropic immediately.” OpenAI: “We stand with Anthropic. We share their red lines.” Also OpenAI: submits bid to replace Anthropic Pentagon: accepts OpenAI’s deal with the same exact red lines This actually happened. Today. What an Insane timeline
Sam Altman@sama

Tonight, we reached an agreement with the Department of War to deploy our models in their classified network. In all of our interactions, the DoW displayed a deep respect for safety and a desire to partner to achieve the best possible outcome. AI safety and wide distribution of benefits are the core of our mission. Two of our most important safety principles are prohibitions on domestic mass surveillance and human responsibility for the use of force, including for autonomous weapon systems. The DoW agrees with these principles, reflects them in law and policy, and we put them into our agreement. We also will build technical safeguards to ensure our models behave as they should, which the DoW also wanted. We will deploy FDEs to help with our models and to ensure their safety, we will deploy on cloud networks only. We are asking the DoW to offer these same terms to all AI companies, which in our opinion we think everyone should be willing to accept. We have expressed our strong desire to see things de-escalate away from legal and governmental actions and towards reasonable agreements. We remain committed to serve all of humanity as best we can. The world is a complicated, messy, and sometimes dangerous place.

English
90
288
3K
450.4K
Carlos Lemus retweetledi
Carlos Lemus
Carlos Lemus@carlosaln_dev·
"It's all over" said the 1800s painter, for the camera would allow him to paint custom portraits no more.
English
0
0
0
6
Cloudflare
Cloudflare@Cloudflare·
What's an "old" technology (like LaTeX, IRC, or maybe even assembly language) that you still find fascinating or even use? #CloudflareChat
English
154
13
503
76.6K
Carlos Lemus
Carlos Lemus@carlosaln_dev·
@kepano @kalomaze you're also responding to an anon user who works for a company describing itself as "open superintelligence stack" 😄
English
0
0
1
303
kepano
kepano@kepano·
@kalomaze by your definition slop and tinkering seem like two separate axes an app can be tinkerable while still being human-coded and intentional
English
9
2
361
29K
kalomaze
kalomaze@kalomaze·
an example of software that falls into the genre of poweruserslop: Obsidian
Leon@ericssunLeon

@kalomaze poweruserslop is a funny concept

English
121
125
5.4K
396.1K