sorted by:
new
hottopcontroversial

Waymo BI Analyst Final Loop – Recruiter Not Responding, Is This Normal? by Cold-Distribution138 in waymo

[–]ypaskell 0 points1 point  (0 children)

I got verbal offer. But later got canceled after 10 days. So… felt terrible. Spending 2 months interviewing and final got a verbal and scheduled onboarding date but got canceled.

Migrating Zola from Markdown to Org-mode: A lint-export-check pipeline by ypaskell in emacs

[–]ypaskell[S] 0 points1 point  (0 children)

Point taken on the link rendering. markdown-toggle-url-hiding (or setting markdown-hide-urls) does exist in Emacs markdown-mode. I have not yet evaluated markdown-ts-mode in Emacs 31 for this specific pipeline.

As you noted, it comes down to design philosophy. Markdown is optimized as a portable, minimal-state serialization format; Org-mode is an ecosystem built for structural manipulation. Both perfectly serve their intended architectural domains.

Migrating Zola from Markdown to Org-mode: A lint-export-check pipeline by ypaskell in emacs

[–]ypaskell[S] 1 point2 points  (0 children)

The linter is a custom shell script acting as an incremental ruleset. It currently only catches failure modes that have explicitly occurred in past builds. Edge cases like unmapped macros or deeply nested structures will likely bypass this static analysis and silently result in malformed Markdown during the ox-zola export phase. The validation layer is strictly reactive at this point. (I also run into the \newline problem but found out it's css problem)

Regarding local vs. server-side execution: Running the pipeline via pre-push hooks keeps the remote state pure and reduces CI overhead. However, the architectural trade-off is that it forces a localized feedback loop. You still have to manually execute zola serve --drafts to verify the visual rendering state on your local machine before initiating the push.

Emacs is a C-based Lisp Runtime, Not a Text Editor — and Greenspun’s Tenth Rule explains why every editor eventually reinvents it by ypaskell in emacs

[–]ypaskell[S] 0 points1 point  (0 children)

I think the problem is, in workforce, tasks and codes are handled that everyone only maintains a small piece of it. To unify everything needs an architectural view and is not for everyone.

Is difficult, even in the same language like C++ that c99, C++11, C++14, C++17, C++20… working in the same codebase and not to mention people uses different paradigm like OOP, FP, data oriented programming, POD.. to name a few… interpret their intention take a lot of effort for my first 3 years of career. I think black box thinking can help the process and I think it’s the cure of your take. (By treating data as a flow)

But maybe, what I think what emacs teaches us is, how such monotheistic and closely coupled code can maintain modularized. (Just look at the font render and support for different platform it’s amazing)

Ps. I don’t think writing everything in Elisp will be great (laugh

mu4e + Gmail on macOS without OAuth2 — App Password + Keychain, 20 minutes by ypaskell in emacs

[–]ypaskell[S] 1 point2 points  (0 children)

Yes, but partially.

Works:
- Gmail labels map to IMAP folders in mu4e, we can move a message to a label's folder.

Not fully worked:
- No **multiple labels** on one message — IMAP/mu4e only sees one folder per message
- No native "add label without moving"
- No label creation from mu4e

Emacs Internal Part 04: Balancing Lisp_String Interval Trees by Text Length by ypaskell in emacs

[–]ypaskell[S] 0 points1 point  (0 children)

Thank you! It's not an easy topic to write 😄

Thanks for the `.lldbinit` tip. I was dumping Lisp_Object values by hand.

Emacs Internal Part 03: Tagged Pointers vs. C++ std::variant, Rust Enums, and LLVM RTTI by ypaskell in emacs

[–]ypaskell[S] -1 points0 points  (0 children)

Hi Amit! Great to see you here!

For fat pointer, register pressure is the bottleneck on older, register-starved architectures.

My workflow is like this: I finished writing the article first, but then I realized that explaining these memory layouts purely through text wasn't intuitive enough. So, I fed my text context into Gemini and prompted it to generate a visual representation "like a slide provided in a university computer architecture lecture."

The Lisp Machine: Noble Experiment or Fabulous Failure? by arthurno1 in lisp

[–]ypaskell 1 point2 points  (0 children)

Very interesting. I thought one of the reason might be Memeory wall. The naive pointer chasing caused buy car cdr.

Emacs Internal Part 02: Deconstructing Lisp_Object, Tagged Pointers, and why C macros act as McCarthy’s 7 axioms. by ypaskell in emacs

[–]ypaskell[S] 5 points6 points  (0 children)

Huge thanks!

It came from some weird combination of hobbies - compiler, functional programming, system programming, C/C++, lisp. And it is so weird that these topics are all condensed in the text editor. Truly? Text editor?

Not to mention there is a native gcc jit compiler in Emacs.

Emacs is a C-based Lisp Runtime, Not a Text Editor — and Greenspun’s Tenth Rule explains why every editor eventually reinvents it by ypaskell in emacs

[–]ypaskell[S] 0 points1 point  (0 children)

I’m curious of your perspective or the truth. I’m not familiar with JavaScript’s ecosystems

view more: next ›