Hey X,
My name is Collins,I am 18, just Started my journey to becoming a software engineer, No experience - just me,my laptop and my curiosity to learn.
I will be sharing what I learn,small projects,wins and failures.Wish me
Goodluck as i begin my journey.
#learningHowtocode
Coded insert at beginning, end, middle + deletion.
Deleting still feels a bit tricky. You make the previous node skip the one you want to remove.
Anyone else struggle with this?
#DSA
A server needs to manage its connections and distribute work efficiently without exhausting its resources.
Next: Finish my test design and start implementation.
Still learning. Still building. ๐
Today, I continued designing my Java HTTP server and focused on understanding how to test its behaviour before implementation.
Some things I worked on:
Understanding the Router's responsibility in handling HTTP requests.
Distinguishing between 404 Not Found and 405 Method Not
Today, I spent time understanding how to design a backend HTTP server using Java and raw sockets.
I went deeper into some important backend concepts:
How HTTP requests and responses work.
The relationship between TCP, sockets, and HTTP.
How a server handles multiple client
Understanding how thread pools handle multiple client connections concurrently
One thing that clicked today: accepting multiple connections isn't the same as processing multiple requests concurrently.
why each component exists, what responsibility it owns, and how the components work together to solve a problem.
Next: Finalising my test design before implementation.
Still learning. Still building. ๐
Today, I spent time understanding how to design a backend HTTP server using Java and raw sockets.
I went deeper into some important backend concepts:
How HTTP requests and responses work.
The relationship between TCP, sockets, and HTTP.
How a server handles multiple client
Today, I worked on understanding how to design a backend server from scratch using Java.
I'm building an HTTP server with raw sockets, and I focused on understanding how its components work together.
Here's what I learned:
How ServerSocket and Socket handle client connections
I also started thinking about testing before implementation (TDD) and how to test different scenarios, including invalid requests and unsupported HTTP methods
One thing that's becoming clearer to me: building software isn't just about making things work. It's about understanding
How separating responsibilities makes server architecture easier to maintain.
One thing that clicked today: a good backend isn't just about processing requests. It's about designing components with clear responsibilities.
Next: Test design and planning before implementation.
Today, I worked on understanding how to design a backend server from scratch using Java.
I'm building an HTTP server with raw sockets, and I focused on understanding how its components work together.
Here's what I learned:
How ServerSocket and Socket handle client connections
Today, I went deeper into how web servers actually work under the hood.
I'm building an HTTP server in Java using raw sockets, and today I focused on understanding:
HTTP request and response structure.
How sockets establish client-server communication.
How threads and thread
Why accept() accepts TCP connections, not HTTP requests.
How a router maps endpoints to approved resources to prevent access to unwanted resources by clients.
How Java's File API reads HTML and JSON files.
Why UTF-8 encoding matters when sending responses.
Hey @X algorithm ๐
Looking to #connect with people interested in:
โข Java & Spring Boot
โข DSA & Problem Solving
โข Full-Stack Development
โข AI/ML
โข Open Source
โข Freelancing
โข Building in Public
I'm learning, building, and sharing my journey.
#LearningInPublic#connect