Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
~/T49KYIcHmPLC.es/src
Pedro's little corner on the Internet
- On finding passion in devising developer experiences
- Modular projects, Typescript, and developer experience
- On embracing my chaos
- Javascript experiences upon Ruby values
- Lacking the tools for a healthy work-life balance
- Mitigating 'delete node_modules'
- But they are developers too
- CLIs are products too
- Javascript, ESM, and tools
- Users don't give a shit about your web app's portable binary
- OSS and extrinsic motivators
- Conceptual compression in web frameworks
- Thoughts on Javascript and testing
- Rendering and deployment plumbing
- Thoughts around Javascript bundling in the context of a CLI
- Zero cost abstractions
- Capitalism and Javascript
- My first open-source Svelte component, svelte-scroll-progress-bar
- Platform-dependent CLIs
- On evolving opinions
- Migrated to SvelteKit
- Exploring a world of opportunities with Web3
- A inflamed society
- Adapting to a platform
- Open source vendor-locking
- I want to be rich
- The React chain
- On cutting off some dopamine dependency
- Great solutions for the wrong problems
- Developer platforms and diversity
- Spain, it's not time to be reunited (yet)
- A future note to self about Omniauth
- ./dev
- Seabolt support for M1
- Some Rust thoughts
- Planning open-source work
- Contributors' first experience
- What I learned as a manager
- Propose, prototype, and build
- Back to Jekyll
- Swinging the pendulum back to engineering
- Focused Xcode projects
- On not having focus
- Tuist 2.0 and next
- Building mental models
- ViteJS and Rails
- Learning Rust
- Migrating documentation to Docusaurus
- TailwindCSS or Theme-UI
- Seeking focus
- Community-driven and organization-driven open source
- The role of flexibility in scaling up Xcode projects
- Open source, people, and happiness
- Data-driven open source
- Building Tuist as a platform
- Tuist and JS bundlers
- Owning your workflows
- Focusing on the problems
- Tuist and the Swift Package Manager
- Tackling technical debt in Tuist
- Decision records
- Scaling up an open-source project
- The beauty of a standard command line interface
- Reflecting on 3 years at Shopify
- My first RFC in the React Native project
- Flattery-driven open-source
- Hosting as a service with RedwoodJS
- My tech stack in 2020
- Developer experience and Javascript
- Sparking joy working with Xcode
- Tree-shaking Xcode projects
- Module caching in Xcode projects
- Growing Tuist's community
- The exciting adventure of building a web app
- Generating Typescript code from a GraphQL schema
- What I like from Ruby and Rails
- Modularization in open source projects
- Finding focus
- Pairing sessions to introduce people to Tuist and open-source
- Thinking in terms of problems
- The beauty of not expecting something in return
- A shift towards product development
- Transitive React Native dependencies
- Streamlining app development
- Making progress on Galaxy
- WWDC's FOMO
- Building a Galaxy for your projects
- First thoughts on Sorbet
- Working on new features or tackling technical debt
- Add and remove footer using NSBox
- My first coding video on Youtube
- To build, or not to build
- Cognitive overhead
- Graphed knowledge
- Catching crashes at launch time on Android React Native apps
- Control and innovation
- Anxiety-free working
- Trying out iOS builds from pull requests with Angle
- Keeping it simple
- Diving into Nix
- We need more crafters
- A better signing experience in Xcode
- Learning bash
- From iOS engineer to a T-profiled techie
- Generation of Swift interfaces to access resources
- A standard CLI for Xcode projects
- Evolving Tuist's architecture
- Granada
- Seeking inmutability
- Social anxiety
- Wrapping up 2019
- Signing with Xcode on CI
- Moving Pods to Packages
- Adding bits of reactive programming to Tuist
- Working on a new website for Tuist
- Creating experiences
- I am X
- Module caching with Galaxy
- Static site generators
- Better relative paths
- Project description helpers
- Abstractions
- The things that matter
- Keeping up with dependencies updates
- What's coming to Tuist
- A period of changes
- Project generation
- Adding error tracking to a CLI written in Swift
- Derived Info.plist files
- Running system tasks with Swift and Foundation
- All you need is tools (talk)
- How I feel working on Tuist
- The tale of Xcode projects' complexity
- The urge to be the first
- Speaking at AltConf
- Abstracting Info.plist files
- It's ok
- Genuine opinions on the Internet
- T-shaped engineers
- Xcode updates are fun
- Reliably installing Xcode
- Where does the stress come from?
- What's the value?
- macOS development and being comfortable
- Interacting with Xcode projects in Swift
- Open source and trust
- Automated tests for a Swift CLI tool with Cucumber
- Software and people
- Turning negativism into positivism
- Deep linking into macOS apps
- GitHub as an organization hub
- The motivations behind building Tuist
- But it's powered by Electron
- I do have weaknesses too
- Wrapping up 2018 📦
- All you need is tools 🛠
- What a psychologist helped me realize
- Drawing - Oberbaumbrücke
- GitHub workspaces using email
- Open source mindfulness
- Why am I obsessed with developers being productive using Xcode?
- Stress
- Open Source
- On having focus
- Hallo Ruby, wie geht's?
- Thoughtful usage of technology
- I gave up using Medium
- The hermeticism and rigidity of Xcode and its projects
- Who is controlling whom
- This app could not be installed at this time
- Random thoughts a Friday night in Ottawa
- Wrapping up 2017 📦
- Task automation in Swift with Sake
- Are companies highjacking our brains?
- Linting your Xcode projects with xclint
- Consistent vs convenient
- Modular Xcode projects
- Providing mocks and testing data from your frameworks.
- Conditionally embed your dynamic frameworks
- Little tweak to be more productive writing XCTest tests
- Introducing xcodeproj
- Moving back to Berlin
- My thoughts on using React Native
- information.subscribe(next)
- Composable UIs
- Divide and conquer
- 📦 Wrapping up 2016
- Extensions, dependency injection and frameworks
- Developing tools for developers
- Stepping off the social world
- Be Reactive my friend
- Micro Features Architecture for iOS
- Network Testing - Say hello to Szimpla
- A journey into Frameworks - Le Testing Framework
- Being disconnected in a connected world
- Developer Reflexion: Focus
- Boy Scouts rule with Danger
- Automating iOS review tasks with Danger
- El patrón Comando en Swift
- Marcheta en la vida
- The spare time project journey. Why I started GitDo
- Xcode scripts to rule them all
- Swift Spain Community
- States - The source of truth
- Developing PopcornTime for tvOS
- Building PopcornTime for tvOS
- I struggle learning languages
- Install the last Carthage version on CI services (Travis, Circle, ...)
- Rewriting SugarRecord, 2.0
- Functional is about functions (Swift)
- Implementing a Mutable Collection Property for ReactiveCocoa
- Programación Reactiva en Swift: Parte 1, Introducción
- Paginated API requests using Functional Reactive in Swift
- Why Open Source helps you to become a better developer
- My first Apple Watch impressions
- Full control in your hybrid mobile apps with a local server, 8fit
- Modularize your mobile projects
- Boosting your mobile app with Javascript and some mobile knowledge
- Swift and Objective-C playing together
- Codemotion experience
- VIPER, Looking for the perfect architecture
- Github as your project management tool
- Leaving Redbooth
- Setup your iOS Projects for testing