Thomas Jaggi reposted
Thomas Jaggi
Thomas Jaggi
@thomasjaggi.bsky.social
https://social.thomasjaggi.ch/@thomas
36 followers90 following23 posts
Thomas Jaggi reposted
Thomas Jaggi reposted
Last day to pre-order @grimalkina.bsky.social's psychology of software teams. Based on the sneaks already think this will be a must have tome for software folk. www.routledge.com/The-Psycholo...
Thomas Jaggi reposted
In @npmx.dev you can now view a package's changelogs currently only package's that use Github to host their releases or changelog.md are supported but support for others are planned
Thomas Jaggi reposted
Replying to @jessdee.bsky.social
He explains why here, if any of you are interested. It is exactly what trans people have been saying the entire time.
Thomas Jaggi reposted
its great seeing npmx as an output for a lot of the data and tools we have inside e18e visibility of these things goes a long way to helping the wider community improve their own projects very nice having a place to output this npmx 🤝 e18e💙
@e18e.dev's module-replacements in VS Code 👀 Powered by `vscode-npmx` — get modern package alternatives right in your editor. Try it out: 👉 marketplace.visualstudio.com/items?itemNa... Would love to hear your thoughts!
Thomas Jaggi reposted
Comedian @karpi.bsky.social explores the possibilities and pitfalls of generative AI. He suggests ways to collaborate with these systems and, through demonstrations of specific model failures, builds heuristics to help us get a feel for the current generation of models 🎟️ frontconference.com/tickets
Thomas Jaggi reposted
@valentinapy.bsky.social examines the spectrum of language model openness, from fully open to closed systems, highlighting what distinguishes truly open models like Apertus or Olmo from open-weights-only alternatives, while addressing the ethical and legal dimensions. 🎟️ frontconference.com/tickets
Thomas Jaggi reposted
Together with @suesmith.lol, we'll explore the developer skills of the future, and work out how we’ll enable people of all experience levels to grow, building strong career pathways that will persist through this wave of automation. 🎟️ frontconference.com/tickets
Thomas Jaggi reposted
Front Conference Zurich is coming up soon! On Friday, February 27, an amazing group of speakers will explore how AI is reshaping the way we work, from creativity and product design to engineering and collaboration 🤩 Our lineup: frontconference.com/schedule 🎟️ Your ticket: frontconference.com/tickets
Thomas Jaggi reposted
i know a lot of the javascript community thinks that people who complain about frontend complexity are just being cynical but it turns out that caking on layer upon layer of abstractions can have real-world consequences
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
Thomas Jaggi reposted
terrific post, to which i'll add a couple of related thoughts. first: a lot of developers, especially juniors, tend to assume that other people's code is better than theirs, and so using a dependency (rather than a snippet) makes their codebase better this is very much not the case
some thoughts about the bloat introduced by edge-case first libraries
Thomas Jaggi reposted
Thomas Jaggi reposted
Node excitement 😉 Congrats to @marcoippolito.dev on today's landmark Node 22.18 release. It is the first LTS release to ship unflagged TypeScript support 🎉 This means Node can run *.ts files. It pairs well with TypeScript's "erasableSyntaxOnly" flag 👍 Many folk contributed 🙏
Type stripping is enabled by default 🔥🔥🔥🔥 You can just run `node file.ts` without `--experimental-strip-types` flag. This is a huge milestone
Thomas Jaggi reposted
Thomas Jaggi reposted
Thomas Jaggi reposted
I'm happy because this change means TypeScript defaults and Node defaults are converging 👍 Node does not support Import Elision which means it's important to enable "verbatimModuleSyntax" vMS means the developer knows if an import statement/binding will be deleted - all via the `type` keyword.
TypeScript excitement 😉 Congrats to @searyanc.dev on landing big updates to the default tsconfig settings used by `tsc --init` 🎉 Defaults matter - and in TS 5.9 they embrace simplicity 💙 🔷 ESM (was CommonJS) 🔷 No down-leveling (was ES2016) 🔷 verbatimModuleSyntax: true github.com/microsoft/Ty...
You are up to date.