I knew what an SRE was and found the article somewhat interesting with a slightly novel (throwaway), more realistic take, on the "why need Salesforce when you can vibe your own Salesforce convo."
But not defining what an SRE is feels like a glaring, almost suffocating, omission.
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build: - web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
What I’ve built:
Recently developed a chatbot MVP for a small business (DJ & lighting rentals) — scraped/cleaned product data, embedded it with HuggingFace + Chroma, and served responses via FastAPI with a streaming API. Integrated React front-end for chat UI. Prior experience building automation/scraping tools and full-stack prototypes.
What I’m looking for: Full-stack or backend-leaning role (internship, entry-level, or startup contract) where I can ship fast, learn in the trenches, and contribute to real product outcomes. Interested in early-stage startups that value initiative and flexibility.
Email:
pfrase4@wgu dot edu
pfras@protonmail dot com
Why would you want to abstract away the underlying database?
Wouldn't it better to already use the target DB to cattch potential issues earlier? Also to avoid creating another layer of indirection, potentially complecting the codebase and reducing performance?
Primarily for libraries and deployment environments that aren't fully in your control which is still pretty common once you get to B2B interactions, SaaS is not something you can easily sell to certain environments. Depending on the assurance you need, you might even need to mock out the database entirely to test certain classes of database errors being recoverable or fail in a consistent state.
Even in SaaS systems, once you get large enough with a large enough test suite you'll be wanting to tier those tests starting with a lowest common denominator (sqlite) that doesn't incur network latency before getting into the serious integration tests.
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build: - web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
I'm a software engineer working to help people build products and deliver value to their customers.
I can help build:
- web applications using modern principles with the latest technologies (Angular, React, TypeScript, Vue, TailwindCSS, HTMX); - services that monitor equipments using telecommunications protocols (SNMP, NETCONF, TR-069); - serverless programs on any business domain to help reduce costs and increase availability (AWS Lambda); - microservices that expose REST APIs for consumption using battle-tested frameworks (SpringBoot, Quarkus); - data processing applications and services that consumes streams of data using common parsing techniques (Rust with Nom); - small CLI apps to help automate common tasks (Rust); - integration of different services using distributed log (Kafka, AWS SNS), WebSocket (with NodeJS) or with simple HTTP requests; - proper documentation for common services using OpenAPI specification and/or frameworks such as Diátaxis (Swagger)
