I'm a software engineer with a passion for building distributed systems. My journey started philosophy of mind at Princeton and UCLA ๐, and now, I'm deep into the world of code! I specialize event-driven design, cloud development, and CI/CD pipelines. Whether it's Java, TypeScript, or Python, I speak the language of technology. My expertise extends to AWS infrastructure and DevOps tools like Kafka, NodeJS, Docker, and Kubernetes.
๐ Skills
- Languages: Go, TypeScript, Python, Java
- Frameworks: Angular, React, Gin, Beego, Express, Spring
- Infrastructure: AWS, Kafka, NodeJS, Docker, Kubernetes, Grafana
- Databases: MongoDB, DynamoDB, Redis, SQL
- Dev Tools: Linux, Git, Maven/Gradle, Jenkins
I've worked at Chase, Amazon, and am currently @Tinder. I focus on backend development - think pipelines, APIs, and so forth. You can checkout out my LinkedIn profile for more details
My github contains a smattering of repos ranging from ULCA computer science assignments written in C and C++ to fully-fledged web applications combining Angular, Java, and Hibernate. My public repos are a record of my growth and evidence of my technical abilities - feel free to browse! ๐
Technical Interests I work with traditional sofwware engineering technologies and design patterns at my day job. I'm interested in working with more niche fields like AI and blockchain. I'm also a freelancer, so if you need help building a website, integrating LLMs, or anything else related to software engineering or web development, feel free to reach out to me! ๐ค
I'm glad you asked ๐ . The best way of explaining it is that philosophers attempt to specify and debug a conceptual system. Say someone makes an argument. Philosophers test the argumetn with input (thought experiments, scenarios, etc.) and verify the outputs the truth of the statements resulting from 'running' the argument using the inputs. Philosophers then analyze the argument, teasing out the central components, the implications, and the pitfalls of the arguemnt.
It's actually a lot like asking about the data structures, execution flows, and performance bottlenecks of an application! You're trying to 'feel out' the contours of a system. A big part of this work is developing logical fluency. This is actually how I found my way to programming and software development: I had to learn about logical structure, syntax, variables, quantifiers, assignment, and all the rest ๐งฉ just to get a Masters in Philosophy!
Feel free to reach out! Let's connect and create something amazing together. ๐
- Email: [email protected]
- LinkedIn: Christopher Cross