What I like to do is to make sure after a engineer works on a specific feature/system, to update the documentation in a separate PR. This can be as simple as a .md file in the docs folder (that's how the early stage startup team I am in does it). That 20 mins spent documenting simple, key things can save the next person 2 hours.

job hunt @ new grad

Sabih Sarowar

1. Why does it feel repetitive exactly? What kind of work do you do?
2. Do you get the freedom to choose your work?
3. How interesting is the product you work on?

Never heard of that before but that seems very interesting. Someone on r/experiencedDevs, told me that he interviewed many senior/staff with good resumes, but when he asked them about the projects they were on and why certains decisions were made, most had no idea. He also told me of an example of how he solved a latency issue a DB had when generating reports with millions of points of IoT sensor data. Was interesting to hear how he considered the business tradeoffs and chose a less robust, but more practical solution (kicked the can down the road with a bandage solution due to cost).

(replying to your reply)

imo, having any original side project that's deployed puts you in the top 10% of applicants. Most of my friends don't have an original, deployed side project on their resume. They just say x project but there's no link to it.

new grad

If it's original, functional, and something someone can play around with or see it has users, I think it'd have value on your resume. Plus it's a great way to learn how entrepreneurship works.

Also, what process did you use to find leads and send emails? Currently trying to do this myself. Using Apollo for sending emails but idk if they are best bang per buck, using the free trial rn.

For your startup idea, how did you reach out to those big corporations?

I like it, nice and simple. I would add "magin: 0 auto" to horizontally center it.

Entry-Level Software Engineer at Unemployed

<https://www.antride.ca/>: The easiest way to organize carpools.

ant ride is a carpooling website you can use with your to automatically create the most optimal carpooling routes between drivers and riders 24 hours before the event starts. Usually, carpooling is tedious to organize but my website automates the matching process based on location. Check it out and let me know of any feedback. 

Github: <https://github.com/kleenkanteen/ant-ride>

Ideally the best project idea is one that you've been wanting to make for a while and is not too complex. This takes time to come up with and exposure to different problems/fields. I have a Obsidian file where I list every new idea that I think could be viable.

Another way is to get ideas from others. For this, you can simply ask people or find collections. Here is a tweet with many ideas: <https://x.com/\_buildspace/status/1793805155080777955>.

I'm currently making a carpooling website at [antride.ca](http://antride.ca/). I remember talking about the idea 2.5 years ago in a internship interview (which I did not end up getting), and I'm finally getting around to making it. The idea is from personal experience of a uni club I was in that would be have off-campus events intermittedly. Carpooling wasn't attempted by the organizers and the current websites are unintuitive. No carpooling website currently exists that auto-matches people into groups based on location to make the optimal carpooling routes. So I decided to make one.

Once you start your idea, make a project overview document. List the problem, the solution, and the minimum viable product you would have to make to bring value. Keep scope as small as possible. Resist the urge for perfection. 

If it has the ablity to get users, do a bit of upfront research by making a survey or asking potential users what they think of it.

And remember to enjoy the process by working on an idea that excites you.