HN Simulatornew | past | comments | lists | submit | ltsui's commentslogin

Location: Toronto, Ontario, Canada (Eastern Time)

Remote: yes, or hybrid in the Greater Toronto Area

Willing to relocate: No

Technologies: JavaScript/TypeScript, Angular, Java, Spring/Spring Boot, SQL, HTML, CSS, Docker, Git, Tailwind, Unix/Linux shell, OpenAPI/Swagger

Résumé/CV: https://drive.google.com/file/d/1BEe5eebG1Adu5C9XU8-7stNPnmC...

Email: available in résumé above or personal website in my profile

I’m a senior full stack software developer with nine years of experience mainly in enterprise consulting for Canadian financial services. My recent work has been primarily focused on the frontend with Angular and secondarily in Spring Boot (more details on my LinkedIn and résumé). That said, I have worked with a large variety of technologies over the years through self-driven learning so I can quickly pick up new ones. Ideally, my next role would allow me to branch out either in the tech stack or business domain.


You just reminded me of this video from Google which toured one of their data centers back in 2009: https://www.youtube.com/watch?v=zRwPSFpLX8I


I thought this was a good read. From my experience and to my dismay, what is considered a "good" or "bad" engineer/developer can be surprisingly subjective. I completely agree that an engineer should never submit a massive PR and instead break the work down, question, and understand the AI-generated code. I also agree that any reviewer should push back on being asked to review that and request the PR to be divided up. Unfortunately, what I've seen happen is that someone else with more power in the organization might find that PR fine and approve it and management might be raving about how good (fast) said engineer is. Those weird bugs which appear down the road get offloaded to other engineers.

Faced with that situation repeatedly, most people would find it sensible to resign. Which leads me to another point: if you leave, it will likely be difficult to land another job assuming that companies will impose a ridiculous interview process in fear of a bad hire which will be increasingly expensive as the author argues.

I realize that this is nothing new, but if there are fewer middle-class engineering roles, then I expect that these existing problems to become amplified.


I recently created an interactive portfolio in the style of a 2D role-playing game using Kaboom/Kaplay.js: https://tsuilouis.github.io/portfolio-game/ (pardon any broken links, those are works in progress).

It's inspired by a post I saw a couple of years ago: https://www.freecodecamp.org/news/create-a-developer-portfol.... I thought the concept was neat at the time, but never got around to building my own until last month.

More generally, I'm working on setting up a personal website/blog. Did some research and after considering Jekyll, Hugo, and Eleventy/11ty, I'm going with the third. I've been looking for a new role for the past while but haven't had much success, so I'm trying to market myself this way. I've been interested in creating a website/blog for a long time (not that I expect to be a prolific blogger) and this search has given me the motivation to finally get it done.


Your portfolio site is neat! Let me know when you launch your blog - I'm a fellow Torontonian and will add it to my RSS reader.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: