Computer Engineering student @ Politecnico di Torino
PoliTong Double Degree · Tongji University
electronics · computing · signals · whatever interesting comes next
I'm a third-year Computer Engineering student, currently looking for an internship closer to hardware and electronics.
Software has been a big part of my studies and projects so far, but I'd like to spend some time on the other side of the computer: circuits, devices, signals, measurements, and the physical systems underneath all the abstraction.
I don't have a perfectly defined destination yet. Electronics is probably where I'm heading next, but I'm more interested in keeping that direction open than forcing myself into a specialization too early.
Long term, I'd love to end up doing research somewhere in the world on some frontier technology — photonics, graphene, AI, or something I haven't heard of yet.
There are too many interesting things to learn and not nearly enough time to learn them all, so for now the plan is simple: keep learning, put myself in unfamiliar situations, and get on interesting trains when they pass.
A native macOS workspace I wanted for myself and couldn't find.
I defined the product, behaviour, requirements, interaction model, UX and testing, then used AI tools to turn that specification into a working application.
More than a coding exercise, it became an experiment in how software can be built when implementation is no longer the only difficult part.
A Software Engineering project developed with a four-person team at Tongji University, starting from an idea that came up living the campus life in China.
Alongside the technical work I had a coordination role: keeping the different parts of the project aligned, helping turn open questions into concrete decisions, and making sure the work moved forward as one coherent product rather than a collection of separate tasks.
I worked across requirements, architecture, documentation, backend/mobile integration, testing, moderation and administration flows, and the final demo.
A MATLAB project comparing FIR and IIR digital crossovers, including reconstruction, delay behaviour, audio processing and experimental analysis.
It also happens to connect engineering with one of the things I enjoy outside university: sound and sound systems.
There is something satisfying about studying a signal on a screen and then being able to hear the consequences.
I occasionally contribute when I find something useful, broken, or simply interesting enough to dig into.
One recent contribution was merged into OmniRoute, where I restored and synchronized the project's Italian documentation with the current upstream version.
C · Python · MATLAB · Assembly · TypeScript
Node.js · PostgreSQL · React Native · Expo
Git · GitHub · Linux
These are things I've used, not percentages of my personality.
Like many Computer Engineering students, I eventually wondered how much sense it still made to spend years becoming exceptionally good at writing code.
I took that question a little more literally than most and consciously stopped treating writing code itself as a skill I needed to optimize.
That doesn't mean avoiding it. I can read, understand and work with different languages, and I'll use code whenever it is the right tool. I just care more about understanding the system, defining the problem, making good technical choices and knowing whether the result actually works.
In an era where generating code is becoming increasingly cheap, I'd rather spend more of my limited time on the parts of engineering that are harder to outsource.
Whether that turns out to be a brilliant decision or a terrible one is still an open experiment.
learning as much as possible before there is time to specialize