- Full Stack Software Engineer at BrickVest, working with Quart (flask like python backend), and React (Typescript), using manual SQL over an ORM
- In 2021 I completed the Full Stack Software Engineer course at Makers Academy, See my final project (React) here, or here (node/express)
- My GitHub CV
- Prior to this I was a photographer at a PropTech startup
- I'm currently working on: learning Docker & Kubernetes to be able to reliably deploy the applciations I can already build
These are the companies that inspired me to become a developer, each found while looking for investment opportunities
I am a shareholder of each of these companies and believe they are the future FAANG company equivalents
β Palantir
Palantir is a one of a kind, bleeding edge data anlytics provider
Initially specialising in clandestine and security solutions for government buyers, they are now broadening into commercial offerings
What problems are they solving | Why they will change the world |
---|---|
|
|
β‘οΈ Tesla
Tesla is leading the world in renewable energy products
What problems are they solving | Why they will change the world |
---|---|
|
|
π¦ Upstart
Upstart will change how the world's financial decisions are made
What problems are they solving | Why they will change the world |
---|---|
|
|
π΅ Google
Google One of, if not the worlds leader in AI innovation
Begining life as an improved search engine, Google now covers an entire ecosystem of cloud products
What problems are they solving | Why they will change the world |
---|---|
|
|
π± Twilio
Twilio makes communications easy
What problems are they solving | Why they will change the world |
---|---|
|
|
Click Here to follow my learning across 12 weeks at Maker's
Week 1: Test driving and debugging
Weekly Challenge | Weekend Challenge |
---|---|
This challenge was the first of my Maker's weekly challenges, coded in pairs with a randomised partner each day. The learning objectives for this week were:
|
This challenge was the first of my Maker's weekend challenge, intended to be done alone to reinforce the week's learning and concepts. The necessary skills covered in this challenge were:
|
Week 2: Object oriented programming
Weekly Challenge | Weekend Challenge |
---|---|
This challenge was the second of my Maker's weekly challenges, coded in pairs with a randomised partner each day. The learning objectives for this week were:
|
This challenge was the second of my Maker's weekend challenge, intended to be done alone to reinforce the week's learning and concepts. This was the first time in Maker's I came across actual difficulty and had to go away to strategise. Upon realising this was essentially a challenge of RSpec doubles and dependency injection I soon figured it out. The necessary skills covered in this challenge were:
|
Week 3: Web applications
Weekly Challenge | Weekend Challenge |
---|---|
This challenge was the third of my Maker's weekly challenges, coded in pairs with a randomised partner each day. The learning objectives for this week were:
|
This challenge was the third of my Maker's weekend challenge, intended to be done alone to reinforce the week's learning and concepts. The necessary skills covered in this challenge were:
|
Week 4: Databases
Weekly Challenge | Weekend Challenge |
---|---|
This challenge was the fourth of my Maker's weekly challenges, coded in pairs with a randomised partner each day. This week is where I would say the difficulty noticeably stepped up, with database interactions being more complex than previous weeks. The learning objectives for this week were:
|
This challenge was the fourth of my Maker's weekly challenges, coded in pairs with a randomised partner each day. The learning objectives for this week were:
|
Week 5: AirBnb
Group engineering project |
---|
This is the first of my Maker's group engineering projects, built in Ruby's Sinatra framework in a team of 4. Throughout this week we worked to user stories and specifications rather than direct challenge instructions for the first time. The ultimate aim was to both build a full stack fully functioning application, but also to do so using AGILE methodology. The learning objectives for this week were:
|
Week 6: Javascript
Weekly Challenge |
---|
This challenge was the return to weekly pair programmed challenges following Airbnb group project week. This week we began programming in JavaScript instead of Ruby, testing our ability to learn a new language. The learning objectives for this week were:
|
Week 7: Single page applications
Weekly Challenge | Weekend Challenge |
---|---|
This challenge was the seventh weekly challenge and the second group based project. We worked in a three to build a single page application that dynamically refreshes content using JS. In this week, while trying to replicate a test matcher, I also managed to (partially accidentally) create a functioning testing framework. The learning objectives for this week were:
|
This challenge was the seventh of my Maker's weekend challenge, intended to be done alone to reinforce the week's learning and concepts. The necessary skills covered in this challenge were:
|
Weeks 8 & 9: Rails engineering project
Weekly Challenge | Weekend Challenge |
---|---|
The second Maker's group engineering project, this time we worked in a group of seven to try to recreate Facebook's functionality.
|
This challenge was the last of my Maker's weekend challenges, to test whether I could use Rails to create a full stack application. The necessary skills covered in this challenge were:
|
Week 10: Individual tech tests
Tech tests |
---|
The aims of this week were to attempt individual tech tests in order to solve popular engineering problems.
|
Weeks 11 & 12: Final Project
The outline |
---|
In our final project, my team decided to build a simple API based app that could search for recipes from your chosen ingredients. This was intentionally kept simple to allow us to focus on the main challenge, using the MERN stack with no previous experience in less than two weeks. We were successful in this and using REACT allowed us to create a dynamic and flowing front end with tight UX and styling. Using MONGO, EXPRESS, and NODE for the back end meant our bookmarks were saved in JSON format, the same as the API returns, allowing reuse of components. |
Server side | Client side |
---|---|
The Server side project was built my members of my team, intended to store user & bookmark data as JSON packages. This also allowed us to move on from using sessions to the far more popular JAVASCRIPT WEB TOKENS for authentication. The learning objectives for this week were:
|
The client REACT application was built by myelf and other members of my team. I mainly worked on the API data requests and the Meal card components, as well as the advertising preview column. The necessary skills covered in this challenge were:
|
Languages | Technologies | Testing Frameworks | Concepts |
---|---|---|---|
|
|
|
|