Sergio Gómez sgomez

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Pre-Transformer Models

React Performance

Notes From Steve Kinney's "React Performance" Frontend Masters Course

General

re: optimizations: "Start with a problem first, then solve it. dont go looking for problems."

"measure first before you optimize for performance. And then measure again."

Hyperlinks (a.k.a. HTML-like anchors) in terminal emulators

[ Update 2025-03-24: Commenting is disabled permanently. Previous comments are archived at web.archive.org. ]

Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).

It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.

Please star ⭐️ the gist to help! This is a proposal for a ⚡️ talk at Reactive Conference.

Styling Components in React Toolbox 2

I wrote react-toolbox and presented it almost a year ago in lighning talk at Reactive Conf 2015 in Bratislava. At first it was just a proof of concept of a component library styled with CSS Modules and SASS. Now the project has grown quite a bit, and during this year there has been tons of changes and lessons learned.

Theming and customization is one of the most difficult and interesting problems to solve. For the first version we needed a custom Webpack loader to generate themes and doing simple style overrides was very painful. Today I'm working on a new playground that will allow you try CSS Modules live, and to create React Toolbox themes on the f

Finding infected files with following bash commands

** Command to list all infected files:

grep -lr --include=*.php "eval(base64_decode" /path/to/webroot
grep -lr --include=*.php "eval" .
grep -lr --include=*.php "base64" .

Command to remove malicious code:

grep -lr --include=*.php "eval(base64_decode" /path/to/webroot | xargs sed -i.bak 's/<?php eval(base64_decode[^;]*;/<?php\n/g'

Basic RESTful API with Symfony 2 + FOSRestBundle (JSON format only) + FOSUserBundle + FOSOauthServerBundle

The API we are creating in this gist will follow these rules :

The API only returns JSON responses
All API routes require authentication
Authentication is handled via OAuth2 with password Grant Type only (no need for Authorization pages and such).
API versioning is managed via a subdomain (e.g. v1.api.example.com)

The API will be written in PHP with the Symfony 2 framework. The following SF2 bundles are used :

	/**
	* A polyfill for `ReadableStream.protototype[Symbol.asyncIterator]`,
	* aligning as closely as possible to the specification.
	*
	* @see https://streams.spec.whatwg.org/#rs-asynciterator
	* @see https://developer.mozilla.org/en-US/docs/Web/API/ReadableStream#async_iteration
	*/
	ReadableStream.prototype.values ??= function({ preventCancel = false } = {}) {
	const reader = this.getReader();
	return {

	const parseJSON = () =>
	new TransformStream({
	transform(chunk, controller) {
	controller.enqueue(JSON.parse(chunk));
	}
	});

	const splitStream = splitOn => {
	let buffer = "";
	return new TransformStream({

	Hi,

	I'm afraid I'm not interested in this position right now.

	I would like to know how you're getting my details and what you're storing though. Under my rights from the GDPR, can you please tell me:

	* what personal data you have collected about me?
	* the source of this data?
	* who you've shared it with, and under what basis?
	* how this data is being used?

	To-do list:

	1. Any open issue / PR on SimpleSAMLphp, or any module or helper-repo within the simplesamlphp-namespace
	2. Refactor some classes to comply with PSR-2 (some don't follow camelCaps right now; we ignore them in Psalm)
	3. Remove remainders of deprecated code wherever possible:
	3.1 Ldap old configuration names (authproc-filters)
	3.2 Rename negotiate-module configuration to 1:1 match those of the ldap-module
	3.3 Merge #514 > close #236
	3.4 Replace crappy LDAP-related classes (#397)
	4. Move www-scripts to Controller-classes (also for the externalized modules; see admin-module for an example)