Settling In
Week one is done, and I can confirm that Swedish offices really do empty out by the time the clock hits a reasonable hour. The flat hierarchy thing also checks out, which took some getting used to coming from a culture where titles tend to do a lot of talking. But more on the culture later. This week was mostly about getting my hands dirty with an actual project, and to my surprise, it had less to do with spreadsheets and more to do with a web server.
What I Actually Did
My first real assignment was setting up and managing a website for the internship. If you had told me before arriving that my “financial analysis and data refining” internship would open with me knee-deep in networking configuration, I would have raised an eyebrow. But this is exactly the kind of thing I was hoping for, the messy, real-world tasks that do not show up in a syllabus. So let me walk through what actually goes into standing up a website, because like data refining, it sounds simple until you are the one doing it.
The first step is having something to serve. That part is straightforward enough, you build the site and run it locally on your own machine, where it lives at an address only your computer can see. The problem is that “only your computer can see it” is not very useful when the whole point is for other people to reach it.
Every device on a network sits behind a router, and by default that router blocks outside traffic from reaching individual machines, which is mostly a good thing for security. Port forwarding is how you carve out a specific, intentional exception. You tell the router that any traffic arriving on a particular port should be passed along to a specific internal machine running the website. In plain terms, you are punching a small, deliberate hole in the wall and pointing it at the right room.
Once the forwarding is configured and the site is actually reachable, the job shifts to managing it, keeping it running, monitoring it, and making sure it does not quietly break the moment someone tries to use it.
Where This Is Going
Running a site off a local machine behind a forwarded port is fine for getting started, but it is not how a real company should operate long term. It depends on one specific computer staying on, it is harder to secure properly, and it does not scale. So my next goal is to help migrate the code over to a proper company server.
The idea is to take everything currently living on a local setup and move it to dedicated infrastructure the company controls, where it can run continuously, be backed up, and be accessed reliably without depending on a single machine in the corner of an office. It is the same instinct as data refining, taking something that technically works but nobody fully trusts, and turning it into something stable enough to build on.
I will admit this is the part I am most excited about, partly because it stretches the systems administration side of my background that I do not always get to use, and partly because it is satisfying to take a fragile setup and make it permanent.
More soon. Vi ses!
