Joel Ross
Winter 2025
<info 340/>
Conclusions
View of the Day
-
Last Questions?
-
Conclusions: Tools & Libraries
-
Administrivia: Evaluations, etc
Any last questions?
(can also review any Firebase stuff)
Project Final Draft
For the Final Draft of the project, we're looking for it to be totally complete! See the Canvas page for full details.
- Well-structured and appropriate HTML (in React)
- Well-constructed React Components. Uses props and state!
- Interactive features: "two and a half" significant features
- Routing and navigation Needs multiple pages; url params
- External React Library rendering a Component. react-bootstrap is okay (if used meaningfully e.g., interactive widget)
- Data Persistence through Firebase (includes asynchronous work; effect hooks, etc)
- Good Visual Style, Accessibility, Responsiveness
- Correct code style -- check the course textbook!
What have we learned...?












So many tools...

Tool Dependency
Much of the web (and software in general) is built on shared, reusable libraries.

"Protestware"

Are they the right tools?
The juxtaposition of The HTTP Archive’s analysis and The State of JS 2020 Survey results suggest that a disproportionately small—yet exceedingly vocal minority—of white male developers advocate strongly for React, and by extension, a development experience that favors thick client/thin server architectures which are given to poor performance in adverse conditions. Such conditions are less likely to be experienced by white male developers themselves, therefore reaffirming and reflecting their own biases in their work.
Future of Frameworks?
I've been building lots of apps by using LLMs and Agents. I'm currently up to about 17 tools, utilities and demos over the duration of a couple of weeks. I build them for me and because tools like Replit have enabled me during my small spots of free time to build fully working sites and apps that solve the immediate problem that I have. I've felt incredibly productive.
...
I'm of the belief that software development is entering a radical shift that is currently driven by agents like Replit's and there is a world where a person never actually has to manipulate code directly anymore. As I was making broad and sweeping changes to the functionality of the applications by throwing the Agent a couple of prompts here and there, the software didn't seem to care that there was repetition in the code across multiple views, it didn't care about shared logic, extensibility or inheritability of components... it just implemented what it needed to do and it did it as vanilla as it could. I was just left wondering if there will be a need for frameworks in the future? Do the architecture patterns we've learnt over the years matter? Will new patterns for software architecture appear that favour LLM management?
- Paul Kinlan, Chrome Developer Relations Team lead, Nov 2024
Course Feedback
Check your email for course evaluations! Do them NOW please!
Thank you for your hard work in this class!
Action Items!
-
Complete the Course Evaluation
-
Late/missing Problem Sets due by Friday Mar 14
-
Final Project due on Monday March 17
-
Hard deadline; no grace period
-
Extra office hours on Monday (time TBD)
-
-
Have a great break!
info340wi25-conclusions
By Joel Ross
info340wi25-conclusions
- 13