100DaysOfCode
1.0.0
Bem -vindo ao meu #100 Days of Code Log, enquanto eu aceito o desafio de codificar pelo menos uma hora por dia pelos próximos 100 dias! Estou juntando -me ao bravo mundo novo de aprender a codificar, iniciando o bootcamp de desenvolvimento da Web da School of Code Stack. É em tempo integral para os próximos quatro meses, mas também é gratuito. O processo de inscrição foi demorado, mas a Escola de Código aceitou apenas 3% dos 4000 candidatos à minha coorte. Como eu poderia recusar a oportunidade? #CareerChange #WomenIntech
Progresso de hoje : novos seletores de CSS e os praticaram enquanto a programação de pares com CSS Diner
Link (s) para o trabalho : CSS Diner
Pensamentos: Fiz -se durante o meu primeiro dia na escola de código e adorei. O fundador e CEO, Chris Meah, nos disse hoje que um nome mais preciso para a escola de código é "intensidade intensiva em carreira tecnológica de solucionadores de problemas criativos colaborativos". Estou animado para começar minha jornada aprendendo a codificar com todas essas novas pessoas!
Progresso de hoje :
Link (s) para o trabalho : hackear a galáxia
Progresso de hoje :
Progresso de hoje :
Progresso de hoje : passei o dia inteiro programando em #javascript e #problemsolved com meu companheiro de equipe em nossa primeira escola de código Hackathon. Construímos um jogo de rocha, papel e tesoura do zero.
Thoughts: I enjoy this catchy School of Code hackathon tune that gets us all fired up to take on the day - Hackathon Fridays.
Progresso de hoje : hoje aprendi a gastar um repositório no Github. Então eu biforei os repositórios de workshops que fiz durante a semana com meu parceiro de emparelhamento. Não os tínhamos terminado durante a semana, então eu os bifurcei para poder trabalhar com eles de forma independente.
Progresso de hoje : trabalhou em nosso dever de casa para o fim de semana, que foi um repositório do Github, cobrindo todos os tópicos do JavaScript que fomos ensinados em nossa primeira semana na Escola de Código.
Progresso de hoje :
Progresso de hoje :
Pensamentos: estou começando a entender o que um programador faz além de "trabalha com computadores". ?
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Progresso de hoje : exercícios estudados e concluídos em www.w3schools.com sobre os seguintes tópicos em JavaScript: variáveis, tipos de dados, funções, matrizes, comparação e operadores lógicos, para loops e html dom
Link (s) para o trabalho : W3Schools JavaScript Tutorial
Progresso de hoje : começou a trabalhar no workshop da semana 2 da Recap da Escola de Código, que abrange funções, cordas, loops, matrizes, setInterval, ClearInterval e busca.
Progresso de hoje :
Pensamentos: Minha citação inspiradora para hoje. Vi isso e é perfeito para mim quando inicio a semana 3 do Bootcamp de codificação. Que coisa nova você será corajosa o suficiente para chupar?
Progresso de hoje :
Progresso de hoje :
Design da interface do usuário (UI):
CSS:
Progresso de hoje :
O progresso de hoje : ontem foi Hackathon na sexta -feira na Escola de Código. Utilizamos nossas habilidades de UI/UX recém -desenvolvidas para projetar uma página de destino comercial. Trabalhando juntos em um par nós:
Today's Progress :
Funções contínuas de codificação, loops e matrizes para o workshop de recapitulação do JavaScript com a Escola de Código.
Uma das muitas coisas que eu amo na escola de código é que eles conectam cada um de nós a um mentor que já trabalha no setor de tecnologia e está disposto a se encontrar conosco 1: 1 a cada semana. Arthur é meu mentor e ele já me incentivou muito com suas dicas, conselhos e apoio. Ele me enviou uma citação inspiradora esta manhã, quando eu estava desanimado e eu a repeti para mim o dia todo. Obrigado, Arthur!
#javascript #mentoring
Progresso de hoje :
Progresso de hoje :
Nesta semana, estamos aprendendo sobre o desenvolvimento de back -end. Estamos usando o NodeJS (um tempo de execução JavaScript de código aberto) para executar o JavaScript fora do navegador.
#NodeJS #BackendDevelopment #json #expressjs
Progresso de hoje :
Progresso de hoje :
Progresso de hoje : Hackathon Friday na Escola de Código na construção de um back -end. Construiu uma API REST do zero. Configure as rotas Crud e as levou a correr em nosso roteador. Criou as funções do modelo e passou para rotear os manipuladores no roteador.
Progresso de hoje : bifurcou o repositório do workshop que fiz com meu parceiro de pares de programação na semana passada na criação de uma API REST usando o Node.js e o Express. Desta vez, fiz isso de novo sozinho para reforçar o que eu havia aprendido.
Progresso de hoje : nesta semana, estamos aprendendo sobre a linguagem de programação, SQL.
Progresso de hoje :
Progresso de hoje : hoje, aprendemos a conectar uma biblioteca a um banco de dados.
Progresso de hoje :
Progresso de hoje : Hackathon sexta -feira na Escola de Código! Trabalhando juntos em uma equipe de três, nós:
Progresso de hoje :
Progresso de hoje : nesta semana, estamos aprendendo sobre testes e práticas modernas de engenharia de software. Aprendemos sobre jestjs.io, desenvolvimento orientado a testes (TDD) e cypress.io.
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Link (s) para o trabalho : acampamento de código livre
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Progresso de hoje :
Thoughts: Every day on my lunch break I try to walk outside. É ótimo para minha saúde e também provou cientificamente aumentar o pensamento criativo em uma média de 60 %! Uma ajuda perfeita para uma solução eficaz de problemas.
Progresso de hoje : Hackathon sexta -feira na Escola de Código. Tentamos usar as habilidades no ReactJS que aprendemos a semana toda para criar um aplicativo "Lista de To To". Meu parceiro de emparelhamento e eu decidimos que precisávamos voltar a entender alguns dos princípios básicos do React, como estado e adereços. Como resultado, passamos algum tempo analisando a lista de reprodução do YouTube do Ninja, o tutorial completo do React e discutindo para garantir que o entendamos.
Progresso de hoje :
Hoje aprendi a transformar o seu login #100DaysOfCode Log em uma experiência visual graças a este artigo do Free Code Camp.
Atualizei posteriormente este log com imagens, links e alterações de formatação com a ajuda do código de marcação, como:
itálico
Audacioso
Link
BlockQuote
Inline code com backsticks
# code block
print '3 backticks or'
print 'indent 4 spaces'
Link (s) aos recursos :
Tutorial de Markdown
Tutorial de Markdown e Código do Visual Studio
Pensamentos: Depois de uma semana intensa, quando eu estava doente com gripe e tentando aprender a codificar usando o React JS, eu precisava de uma pausa mental. Achei que é encorajador e motivador aprender a melhorar meu #100DaySofCode Log no #Github para tornar mais interessante ler. Esperamos que um dia estabeleci postar alguns projetos reais, mas por enquanto este é um bom primeiro passo. Esta citação do código First Girls era exatamente o que eu precisava ler hoje:
Progresso de hoje : aprendido sobre funções puras em reactjs como o usefeft hook. Como buscar dados de uma API usando busca, useeffect e uso de uso.
Progresso de hoje :
Aprendeu sobre o gerenciamento de filiais no Git. Isso incluiu aprender alguns novos comandos Git, como:
check-out git –B Adicionando-to-Remote. Isso cria uma nova filial chamada "Adicionando-to-Remote" e muda para ele ao mesmo tempo.
GIT PRINCIPAL PRINCIPAL.
git push-set upstream origem newbranchname
Também aprendemos sobre o UserEDuces, que é um gancho que permite gerenciar seu estado no React quando você deseja manter tudo sob controle.
Progresso de hoje :
Refatorado uma lista com o UserEduces da Escola de Código UserEduces Workshop
Trabalhou na solução de um 6kyu Kata em Code Wars com meu parceiro de emparelhamento.
Tive uma atualização na redação do código de teste em preparação para o nosso projeto de grupo na próxima semana.
Em seguida, trabalhou em um workshop de teste de componentes do React.
Aprendi sobre o aplicativo Create React. React Testing Library.
Progresso de hoje :
Aprendi mais sobre o trabalho ágil, o Conselho Kanban, as iterações ágeis de sprint, o MSCW (deve ter, deveria ter, poderia, não ter). etc.
Mais revisão sobre os componentes de reação de teste.
Também conduzimos e apresentamos projetos de pesquisa em grupo sobre os seguintes tópicos:
Progresso de hoje : continuação completando as lições no curso JavaScript no Freecodecamp
Link (s) ao trabalho : algoritmo JavaScript e curso de certificação de estruturas de dados
Progresso de hoje : continuação trabalhando através de lições no curso JavaScript no Freecodecamp
Link (s) ao trabalho : algoritmo JavaScript e curso de certificação de estruturas de dados
Progresso de hoje :
Nesta semana, na Escola de Código, fomos colocados em grupos de quatro e pedimos para projetar um aplicativo Web Stack completo, que ajuda a enfrentar os desafios que os bootcampers enfrentam enquanto aprendem remotamente. No final da semana, apresentaremos nossa solução a um painel de juízes da indústria
Um de nossos objetivos nesta semana é usar práticas ágil de desenvolvimento de software enquanto planejamos, gerenciamos, desenvolvemos e apresentamos nosso aplicativo. Portanto, como equipe, concordamos pela primeira vez com os itens principais do manifesto e a estratégia de recuperação. Em seguida, usamos uma prancha e o método de ideação da Disney para debater idéias e depois restringi -las. Também concluímos nossas histórias de usuário, árvore de componentes e estrutura de arame de baixa fidelidade no figma.
Antes de começar meu dia com a escola de código, assisti a vídeos instrutivos do YouTube pela Net Ninja sobre Node.js e React (usando o JSON Server e o UseEffect Dependências).
Progresso de hoje :
Hoje, criamos um conselho da Kanban na Trello para fins de gerenciamento de projetos. Em seguida, derramamos em pares de programação com um par começando a construir o front-end e o outro trabalhando no back-end.
Para o back-end, desenhamos um diagrama mostrando quais tabelas nosso banco de dados conteria e como elas ingressam. Também escrevemos uma tabela de planejamento de API para os pedidos que nosso back-end lidaria. Em seguida, criamos um banco de dados PostGresql na Railway.app
Pensamentos:
Este foi um dia muito estressante. O atrito que tivemos na equipe ontem piorou hoje. Um de nossos colegas não estava em sintonia com o resto da equipe e nos encontramos gastando muita energia articulando por que estávamos fazendo o que concordávamos anteriormente, tentando avançar contra uma força recuando. No meio da tarde, tornou -se insuportável e nossa equipe atingiu um ponto de ruptura.
Progresso de hoje :
Um dos desafios hoje foi conectar as extremidades da frente e de trás que havíamos desenvolvido. Acabamos baixando um pacote Node.js chamado CORS, que fornece middleware expresso e ajustando nossos componentes do React para responder adequadamente.
Também tínhamos um console.
Conseguimos fazer com que dois componentes funcionem corretamente.
Pensamentos:
Começamos hoje com incerteza sobre o que iria acontecer com nossa equipe. Continuamos trabalhando como um trio, mas ainda estávamos um pouco perdidos, pois era difícil prosseguir enquanto as coisas estavam mudando ativamente.
Ficou assim até o meio da tarde, quando recebemos oficialmente uma decisão da escola de código que, a partir de então, seríamos uma equipe de três. Estávamos claramente para trás, mas essa confirmação nos deu o que precisávamos, que era certeza. Durante o resto da tarde, nós três reavalizamos nossa situação, reescrevemos nosso plano de recuperação e começamos a reconsiderar nossa definição mínima de produto viável (MVP).
Progresso de hoje :
Hoje de manhã, em nosso stand-up diário, decidimos que nosso objetivo até o final do dia era que nosso aplicativo tivesse um painel modularizado com seções claras e estivesse visualmente bem estruturada. Tivemos que fazer alguns sacrifícios em nosso plano original para alcançar nosso MVP revisado até o final do dia, como:
Depois de revisar nosso MVP, criamos um esquema de cores, modificamos nossa estrutura de arame de baixa fidelidade e discutimos nossas prioridades e responsabilidades para tarefas usando nosso Conselho Kanban no Trello.
Aprendi hoje como usar o CSS no React to Style Components e gostei de ver resultados visuais imediatos da minha codificação.
No final de todos os dias desta semana, nos encontramos para uma retrospectiva, usando a técnica 4LS, para discutir o que amamos, detestamos, desejamos e aprendemos naquele dia.
Progresso de hoje :
Hoje, nosso foco era preparar e apresentar nosso aplicativo a um painel de juízes da indústria.
Nossa solução é um painel para ajudar os bootcampers a descompactar após um intenso dia de aprendizado. Possui atividades, organizadas por categoria, que ajudam a aumentar o bem -estar. Você pode adicionar a ele todos os dias e ver seu progresso com base em seus objetivos. Ele também tem um gerador de piadas aleatórias. Finalmente, há um aviso para escrever coisas pelas quais você agradece com uma lista que lembra o que você foi grato no passado.
Ferramentas usadas: Jamboard, Figma, Trello, Vscode, Git, Github, Zoom, Google Docs e Google Slides
Pilha de tecnologia usada: JavaScript ES6, Node.js, Expres.js, React.js, PostgreSQL (Elephantsql e Railway.App), HTML e CSS
Pensamentos:
Tivemos contratempos inevitáveis nesta semana e depois nos tornamos uma equipe de três quando já estávamos atrasados. Depois disso, embora nossa equipe fosse menor, trabalhamos como uma equipe coesa, comemoramos nossas vitórias por menor que seja, e nosso nível de produtividade disparou pelo telhado.
A grande opinião para nós é a importância da mentalidade e uma atitude positiva ao enfrentar desafios como equipe. Tivemos uma chance única de experimentar o tipo de obstáculo que se poderia enfrentar em um ambiente de trabalho real. Era importante continuarmos avançando e permanecemos ágeis.
Nesta semana, vivemos os seguintes valores do manifesto ágil:
Sou incrivelmente grato aos meus colegas de equipe neste projeto, Gabe e Milly. Eles também apoiaram, encorajadores, gentis, flexíveis, resilientes e brilhantes na codificação! Enfrentamos grandes desafios, mas os superamos juntos, trabalhando como uma equipe coesa com uma atitude positiva. No final da semana, apresentamos aos juízes um aplicativo em funcionamento que foi codificado quase inteiramente em um dia. Que conquista!
Vocês mostraram uma sólida compreensão dos diretores fundamentais do design de software e do ciclo de vida de desenvolvimento de software em geral.
Trabalho muito bom, fazendo uma situação positiva em uma semana difícil.
A infeliz jornada, dados os problemas que eles tiveram com um membro da equipe, mas ainda assim entregues no projeto, o que é impressionante.
Naturalmente, seu produto final foi menos desenvolvido do que outros que vimos, mas isso é absolutamente compreensível quando levamos em consideração os problemas que você teve na semana (e foi completamente inevitável!) O que você apresentou foi genuinamente impressionante para o que é essencialmente o trabalho de um dia.
Progresso de hoje : antes do SOC começar esta manhã, eu li no Reactjs Docs sobre o Estado para reforçar minha compreensão.
Na escola de código hoje, passamos a manhã em nossos grupos de projetos da semana passada, mantendo nossa retrospectiva de sprint. Criamos um conselho de Trello para discutir o que correu bem, o que precisa de melhorias e itens de ação para o futuro. Também aprendi a adicionar uma opção de votação para os cartões Trello para que pudéssemos votar nas três idéias que gostaríamos de ver no topo da lista.
À tarde, focamos em análises de código. Lemos as diretrizes de revisão de código e nos encontramos com outra equipe da semana passada para revisar seu código (e vice -versa).
Links para alguns recursos usados :
Estado: a memória de um componente
Noções retrospectivas de Atlassian
Progresso de hoje : hoje começamos a implementar algumas alterações no código em nosso projeto com base no feedback que recebemos da nossa revisão de código de pares ontem.
Pensamentos: Gostei muito hoje e sinto que aprendi muito. Enquanto estávamos revisando nosso código, tentei explicar em voz alta aos meus colegas de equipe o que o código estava fazendo. Meus colegas de equipe foram brilhantes em explicar tudo o que eu não entendi. Eles também estão me ajudando a começar a usar a sintaxe correta. Muitas vezes, entendo e posso explicar a lógica do código, mas não me lembro das palavras técnicas corretas a serem usadas (como "renderizar um componente").
Links para recursos : ferramenta jsdoc para adicionar comentários de documentação e editor de Markdown ReadMe
Cypress testando um componente do nosso aplicativo: 
Github Network Gráfico de nossos compromissos: 
Progresso de hoje : criou os documentos de leitura para os repositórios de front -end e back -end do nosso projeto de grupo a partir da semana passada. Terminou em escrever comentários do JSDOC no código para os repositórios de front -end e back -end. À medida que passamos pelo código novamente, foi bom revisar minha compreensão de como cada parte se conecta e se comunica com outras partes da frente para o back -end.
Progresso de hoje : hoje aprendemos sobre a identidade como um serviço (IdaaS), uma autenticação baseada em nuvem construída e operada por um provedor de terceiros. Exemplos de provedores de Idaas são Auth0, AWS Cognito, Firebase e Supabase. À tarde, comecei a tentar configurar a autenticação no front -end de um projeto React. Usei o Auto0 para integrar os seguintes recursos em um aplicativo React de uma página:
Today's Progress : Today I continued working on yesterday's project. I learned how to call an API that validates ourJSON Web Tokens. The aim was to get our user's metadata to display on the page and we managed to do it!
Next, we worked on protecting the backend of our React project. We created an API that supports the following routes:
It took ages to figure out how to get the last one (private-scoped) to work but we finally managed to find and tick the right boxes in the Auth0 API settings to get it to work (hint: check the Machine to Machine Applications tab).
In the last few minutes of the day, I built a React app from scratch that uses authentication via Auth0. The one bit I haven't figure out yet is how to code it so that you can only access the app once you have logged in. Right now it's showing on the main page and also when you log in. Will tackle that problem another day.
Today I also added a demo video to the README files for our week 9 Group Project: Globally Scoped Project Frontend and Globally Scoped Project Backend
Today's Progress : Learned and practiced how to deploy React app projects via Netlify.
Today's Progress : Learned and practiced how to deploy a backend environment using Render. Then deployed the related frontend (a React app shopping list) via Netlify.
The highlight for me today was learning how to set up my React App from last Friday (2 Dec) so that the user has to log in first before they had access to the app, their user info and their user metadata.
To do this, we leveraged the Identity as a Service (IDaaS), Auth0 React SDK. It is a JavaScript library for implementing authentication and authorization in React. We used the useAuth0 hook in our components to access authentication states such as (isAuthenticated and user), authentication methods such as logout, as well as the logical conjunction (&&) operator to do it.
In the morning I also completed some katas on Code Wars with my pairing partner for an hour. We started going through Katas list of Training JS series together.
Today's Progress : Today we learned about a React Hook called useContext that lets you read and subscribe to context from your component.
Links to resources : React Hooks: useContext and Passing Data Deeply with Context
Today's Progress : This morning I completed a CodeWars kata with my pairing partners. Then we worked on completing the workshop from yesterday on custom hooks.
In the afternoon, we learned more about Couchbase. Couchbase is a DataBase as a Service (DBaaS) provider.
Today's Progress : Hackathon Friday at School of Code. Our challenge was to ideate, plan, and build a full stack app that included:
It was a huge challenge to do in just 5 hours. We managed the first task and had started on the second one when it was time to present at the end of day.
Thoughts: How do you maintain motivation to keep going when you are worn out? After twelve weeks of intensive learning with the School Of Code boot camp, I took the advice that Women In Technology (WIT) shared below so I can press on to keep going in my #100daysofcodechallenge.
Today's Progress : We started learning about TypeScript today. Here's a little code snippet from the first part of our workshop practicing writing in TypeScript:
Code Snippets
/* TASK 1.1: declare and initialize a boolean variable */
let isTrue : boolean = true ;
/* declare and initialize a string variable */
let myName : string = "Stephanie" ;
/* declare and initialize a number */
let myAge : number = 32 ;
/* declare and initialize an array of booleans */
let isVeryTrue : boolean [ ] = [ true , false ] ;
/* declare and initialize an array of strings */
let stringArray : string [ ] = [ "2" , "b" , "6" ] ;
/* TASK 1.2: Declare and implement a function which takes in two numbers and
returns their sum.*/
function totalSum ( a : number , b : number ) {
return ( a + b ) ;
}
console . log ( totalSum ( 2 , 8 ) ) ;
/* TASK 1.3: Declare a new type that describes an object containing the keys and
types below:
amount: a number
uniqueId: a string
isValid: a boolean
addressLines: an array of strings */
type Data = {
amount : number ;
uniqueID : string ;
isValid : boolean ;
addressLines : string [ ] ;
} ;
function getData ( personalData : Data ) {
return personalData . uniqueID ;
}
console . log ( getData (
{
amount : 15 ,
uniqueID : "Sam" ,
isValid : true ,
addressLines : [ "1 Park Lane" , "2 Falcon Way" ]
}
) ) ;
/* TASK 1.4: Declare a new type which is any one of: "BLUE" or "YELLOW" */
function setColor ( color : string | string ) {
return "My favourite color is " + color ;
}
console . log ( setColor ( "BLUE" ) ) ;
console . log ( setColor ( "YELLOW" ) ) ;Today's Progress : Learned how to convert React JavaScript to TypeScript. Spent the day with my pairing partner converting all the .js components of a “to-do list” React app to .tsx components.
Today's Progress : Today we learned how to use VS Code to debug code. We also learned a bit more about how to code using TypeScript.
Tomorrow I have a progress interview. Therefore, I also took some time to review the code from our week 9 group project to make sure I understood it. My programming pair partner for this week, Beatrice, was kind enough to let me practice explaining it to her. She asked me some good questions about it too.
In the evening I met with my mentor, Arthur, and he helped me review and practice answering common interview questions that someone might be asked when interviewing for a software development job.
Today's Progress : Hackathon Friday at School of Code. With our programming pair partner our challenge was to build a weather checker app using Typescript and React. The user needed to be able to input the name of a city and have weather information about that city added to the page.
We first made a plan then created a component tree diagram in Miro before we started any coding. I had my progress interview in the middle of the day so Beatrice did a large chunk of the coding during the 1 1/2 hours that I was away for my interview.
In the last bit of time we had at the end of the day we managed to add a background image and weather icon which reflects the city's weather.
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification. Also started watching Dave Grey's Node.js Tutorials on YouTube.
Link(s) to work : JavaScript Algorithms and Data Structures Certification
Link(s) to resources : Node.js Tutorials
Thoughts: I have now completed the first twelve weeks of the School of Code (SoC) boot camp. When I started, the only coding I knew how to do was some basic Python from the Code First Girls intro course I took last summer. I didn't know any JavaScript, HTML, or CSS. I didn't know how to use Git or GitHub. I had never heard of a PERN Stack much less how to code using PostgreSQL, Express, React, and NodeJS. In these past twelve weeks, we have been taught a massive amount and I've worked incredibly hard - day, night, and every weekend. It's amazing how much I have learned and grown in just three months.
I still feel so behind though in my comprehension and was feeling quite discouraged yesterday. However, Bee helped me gain some perspective by pointing out that before our SoC boot camp started, she spent two months going through some Udemy courses on JavaScript (while also working). At our SoC bootcamp we only spent 3 days learning what she had spent a full 2 months learning on her own.
I really enjoyed going through this basic JavaScript course on Free Code Camp today. It's so much easier on my brain. I'm learning things that so many others on my SoC course already knew before they started. Some of these concepts look familiar to me because we have used them in our coding at SoC but I had not learned them yet.
This post encouraged me too:
Today's Progress : This morning David Adams, Site Reliability Engineer (SRE) at ManyPets, gave us a interesting, practical presentation about the Continuous Integration and Continuous Delivery (CI/CD) cycle.
In the afternoon, I met my new programming pair partner for the week and together we started learning more about Amazon Web Services' many products. We created a new AWS account and followed the Amplify with React tutorial to create a full stack application with the AWS Amplify Comment Line Interface (CLI). We didn't have time today to add authentication to the app or deploy and host it but managed to get everything else done from the tutorial.
Link(s) to resources : Amplify with React Tutorial
Today's Progress : This afternoon we did group research projects on Nextjs, Gatsby, and Remix. Each programming pair was assigned one of the React frameworks to research. We later presented to groups who looked at the other two frameworks. My programming partner and I were assigned to research Remix. As part of our research we created a Remix project from scratch. Our group presentations at the end led to some interesting discussions about which framework was better to use depending on your needs.
In the morning I also solved a CodeWars kata with my programming pair partner for this week.
Link(s) to resources : Nextjs, Gatsby, and Remix
Today's Progress : Continuted watching Dave Grey's Node.js Tutorials on YouTube and writing the code along with the tutorial.
Link(s) to resources : Node.js Tutorials
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification.
Link(s) to work : JavaScript Algorithms and Data Structures Certification
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification. Also watched more of Dave Grey's Node.js Tutorial playlist on YouTube.
Link to work : JavaScript Algorithms and Data Structures Certification
Link to resources : Node.js Tutorials
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification.
Link to work : JavaScript Algorithms and Data Structures Certification
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification.
Link to work : JavaScript Algorithms and Data Structures Certification
Today's Progress : Continued to work through more of the Free Code Camp curriculum for the JavaScript Algorithms and Data Structures Certification.
Link to work : JavaScript Algorithms and Data Structures Certification
Today's Progress :
This month at School of Code we have been put into teams of six people and tasked with designing a full stack web application which solves a real-world problem. The aim of this month-long project is to help us experience what it's like to be part of a real-life engineering team building a practical solution for our end users.
Today as a team we accomplished the following:
Key Principles from our Team Manifesto:
Pensamentos:
Today was our first day back after a two-week holiday and the first thing we did was find out who our teammates are for this final project. I have only worked with one of my five teammates (pair programming) before but know some of them as we're in a larger 40 person group (A) on the bootcamp. I am very excited to about our team. They are all great people and we have huge potential.
Today's Progress :
Disney Ideation Method:
User Stories:
The Unique Selling Point (USP) of our app will be:
Now that we had agreed on an idea for our app we decided on a team name: Frugal Fanatics
Today's Progress : Today we began to define our Minimum Viable Product (MVP) and to design a basic low fidelity wireframe based on our requirements.
We also created a Market Research Survey on Google docs. I shared it on LinkedIn, Facebook, and on the School of Code Slack channels to gather as much feedback as possible.
Link to our survey : Frugal Fanatics Market Research Survey
Today's Progress :
We had 74 people complete our Market Research Survey! The results led us to quickly pivot our MVP based on the user feedback.
It showed that the vast majority of those surveyed have increased stress and anxiety as a result of the cost of living crisis. This led us to decide to add a component to the app which would help them, such as a mindfulness element.
Users also indicated that they were keen to have a budgeting tool as well as a tracker for their expenses and saving. However, not many indicated that they needed help with managing debt. So we decided to shelve the debt tracker for the time being.
Today we also finished our low fidelity wireframes.
Today's Progress :
We made final decisions on our Tech stack today, including using relational databases over non-relational. We also decided on our Git branching strategy (GitHub Flow) and practiced it using a practice repo. We will be protecting the main branch and deploying after every sprint. In addtion, we agreed on our colour scheme.
Tech Stack:
Colour Scheme:
Today's Progress :
We finally started coding today!
Team Rota:
Other work we did today as a team:
On the Front End:
On the Back End:
Entity Relationship Diagram 
Today's Progress :
We merged all the front and back end branches this morning so we are moving forward on a uniform copy. With my pair partner for the day I set up the back end to include 3 models and 3 routes connected to the database tables on elephantSQL.
Today's front end teams:
Today's Progress : Today I was working with a different partner on the back end. We debugged and successfully tested GET requests for userRoutes, expensesRoutes, and savingsRoutes via Postman. We also successfully debugged and tested POST for userRoutes.
I drafted the README doc for our back end repo.
We also deployed the back end to Render: Users Table, Expenses Table, and Savings Table
Today's Progress : This morning, with my partner, I finished debugging and testing the back-end GET and POST requests for users, expenses and savings.
We then prepared our group presentation for our mid-month product demos which we showed in the afternoon to everyone in Group A (around 40 people). We received some helpful feedback from the coaches which we will bring into our planning next week.
Today's Progress : Worked on documenting our teams progress since we started, including taking screen shots and recoding videos which demonstrate our app as it is today.
Today's Progress : Today we discussed our goals for our next week-long sprint which starts today. Our top priority is to get the front and back end connected. Right now we have a fully funtional back end with GET and POST requests working. The front end is working too but with dummy data that's been hard coded.
My programming pair partner for today and I worked on cleaning up the code on the front end: breaking down the components into groups and updating the terminology to match the database. At the end of the day, we met as a team of six again and decided that tomorrow morning four of us will work together to agree upon how we want to connect the front and back end so we are not doing separate things (on the front and back end) that don't end up working together.
We are also considering at what stage we will implement authentication - at the start before completing the budget information form, or only after that form has been completed but before displaying the custom dashboard which is populated with data from the completed form.
Today's Progress : Last week, we created a custom Express.js server on the back end and built our front end using the Next.js React framework. We realised this week that there are some challenges with connecting these two. Therefore, today we explored some other options for the back end that would work better with Next.js, such as Supabase. Some of the features that Supabase offers are a Postgres database and authentication. It is also open-source. We spent today discussing, researching and experimenting to determine the best option to use. While I was doing this with a few of my teammates, two others from our group worked together to get the front end deployed on Netlify as well. When we divide and conquer we make great progress together as a team!
Link(s) to resources : Supabase
Today's Progress : Yesterday afternoon we created a test branch off our main front end branch and scaled it down to test whether we could get Supabase working with authentication and our simplified Next.js app. We managed to get it working so decided to go with Supabase + Next.js instead of elephantSQL and Express.js with Next.js. It was easy to quickly replicate our Postgres database in Supabase. Then we started refactoring our code on the front end using Supabase. It's been slow going as it's all new to us. Up to this point, the only authentication that we've learned in the bootcamp was how to use Auth0 as a login for a simple static site. Our app for this project, however, requires authentication and authorization when accessing the database and it's also a dynamic website.
We also spent time as a team today discussing how we can make our app fun and gamefied since that's one of our unique selling points. We have some great ideas which we hope to implement once we finish connecting the front and back ends.
Two of our team worked together today updating the front end to make it accessible. By the end of the day, Google's Lighthouse accessibility audit was showing all green with 100% ratings.
This evening I spent some time reading through documentation on Next.js and supabase so I have a better understanding of how they work. I feel more confident now going into tomorrow.
Tech Stack starting week 3
Accessibility - Lighthouse Audit
Today's Progress : Discussed our goals first thing this morning. Decided to make dark mode the default mode for our app as we all think it looks better (based on our high fidelity wireframes).
Then we split into two teams for the day. My team continued refactoring the code on our front end to add authentication with supabase. It was slow going but we made some good progress.
The second team worked on making the savings page of our app look more fun with icons and colors.
We also had the opportunity to hear from two companies that are hiring for roles that we can apply for when we finish the bootcamp. One of them is hosting a hackathon next week for potential applicants. Excitante!
High Fidelity Wireframe dark mode
Today's Progress : Today we agreed on the name of our app: frumo (short for frugal money).
My pairing partner and I started working on the dark mode version of our app. I enjoyed learning how to use Tailwind CSS for the first time.
We also prepared and gave a presentation to the coaches and other teams in Group A summarizing what we accomplished this week.
Sprint goals week 3 and accomplishments:
Savings page with features added to make it more fun:
Today's Progress : I spent most of today with my pairing partner updating the code so that our app runs by default in dark mode and the dark mode matches our high fidelity wireframe. It was a lot of grunt work but the end result looks good. It also helped me to get more familiar with the interworking of the code on the front end, Tailwindcss, and Figma. We also tried adding a celebration animation to the app for when a goal is achieved to make the app more fun.
Another pairing group from our team worked on the landing page. The third pairing group from our team continued working on the savings page.
At the end of today, the team decided that I should be the scrum leader for the rest of our time working together. I served as the scrum leader our first week and then we started changing to a new scrum leader every two days. Even though half the team initially weren't keen on being a scrum leader, we thought everyone should have the chance to lead because it would be a good experience. It was also interesting to see people's different leadership styles.
frumo app in dark mode:
Today's Progress :
As the scrum leader today, I ran the daily stand-up and end-of-the day retrospective. That evening, one of my teammates sent me a message which boosted my confidence. They said,
“Hey Stephanie, I think you did a fantastic job leading the team today! You kept the stand-ups on point and I think we were a lot more clear and productive thanks to it!”
It was a surprise to receive their message and their encouraging words made my day.
We paired off into three teams today with tasks to complete. My partner and I worked on making the app responsive so that you can view it on mobile phones as well.
By Friday we have to prepare a short video introducing our project, create a new YouTube account for our team, and upload the video to this account. Therefore, I started preparing the PowerPoint presentation and embedding a demonstration video of our app into it.
Today's Progress :
I had a fun day today participating in my first hackathon for a potential employer. It's the first step to apply for a junior software developer role at this company. I was put in a group of four and we were given four hours to design and create a web app to promote sustainability to individuals and software development project teams. We also had to prepare and give a 5 minute presentation to a panel of interviewers from the company about our app.
Throughout the day, we were each pulled out at different times to meet one to one with someone from the company for a casual interview. I enjoyed my conversation with the person who interviewed me and learned a lot more about the company. All in all, it was a great experience. I had never worked with the three people in my group but we worked well together and the interviewers said that our presentation was really good.
Today's Progress :
Today was the last day to work on our app. It was a flurry of activity and stress but we got through it. The main things we worked on were:
Today's Progress :
Today we recorded our presentation and submitted it. You can view it here:
Frugal Fanatics presentation
If you'd like to try out our app for yourself, check it out here: https://frumo.co.uk/
Celebrating the completion of our final project!
Today's Progress :
Today I took on a 6 kyu Shopping List kata on CodeWars. First, I wrote a plan in plain English. I did something differently today though. Once I'd written the plan, I worked backwards. I looked at the best solutions and then wrote code to solve it. I did it in steps, first writing the code to solve the simplest part of the kata. For the next step, I wrote the code to include any discounts and buy one get one free deals on the products. Throughout I wrote comments explaining each line of code. I did all of it in a private repo in js files and tested them in JS Console.
Link to resource : Codewars Shopping List kata (6kyu)
Today's Progress :
Continuing on from yesterday, today I wrote code to test the solutions that I wrote yesterday. I initialised a Node.js project and installed Jest as a dependency. Then I created the test files, wrote the tests, and ran the tests ( npm test ). Loved seeing those green pass test results!
Today's Progress : Today we worked on preparing and rehearsing our presentation for the School of Code demo day.
Today's Progress : I worked with one of my Frugal Fanatics teammates this morning to write some end to end tests to test our app using Cypress. It was really fun to explore testing with Cypress. We hadn't done it since week 6 of the 16 week bootcamp.
Today's Progress :
Today we shared our frumo app to the School Of Code's partner companies who are looking to hire talented junior developers. Our team had the chance to share our frumo app with 12 people from 9 different companies. Their responses blew me away! Here are a few quotes:
"Awesome idea"
"The best presentation I've seen all day. Very professional"
"Shout out to the gamification of savings"
"Amazing app"
"Awesome presentation"
"Really useful"
"Makes dealing with money more digestible for non-financial people"
"Looks fantastic"
"Maravilhoso"
"The dashboard is beautiful"
"Really good looking app"
"Looks really impressive. Very professional."
My personal favourite quote for the day though was:
"Anyone can learn to code with enough time. How you work with people and your communication skills are much harder to learn."
It gives me high hopes as I continue learning how to code even after my days at the wonderful School Of Code are done. I am incredibly grateful to the School Of Code for choosing me, from among the 4000 applicants, to have the opportunity to attend their fantastic bootcamp. I have been stretched beyond measure and learned more than I ever thought possible these last four months. I can't wait to keep learning and coding!
