3 ms·

Good suggestion! I'm just a little skeptical as the job is remote and paid hourly. I submit my hours at the end of each week. I don't want to submit my timeshee

Good suggestion! I'm just a little skeptical as the job is remote and paid hourly. I submit my hours at the end of each week. I don't want to submit my timesheet and then be like "Oh hey yeah by the way these X hours are for something completely unrelated to what I was assigned. Hope that's okay." If it were salary based or something else I'd be totally willing to dive in but as is I don't want to ask to be paid for something that they may not have even wanted me to do.

andrewfromx 5y ago
Donate to them 20 gifted hours of your time. I’ll bet whatever passion project you make in those hours they will love and want to fund for real.
- MathCodeLove 5y ago
  Honestly not a bad idea. If I can find something I'm passionate enough about I think I'll do this. I'd be making something in my free time anyway - might as well make it something that could potentially make my time on the clock better. Thank you!
  - noicebrewery 5y ago
    It's actually an awful idea. The whole benefit of working for a large company is that you DON'T need to sacrifice outside of your 9-5. This is that outdated grind mentality that managers sell to convince people this is needed to get ahead before they hand out promotions to their mates anyway. Secondly, and I don't mean to disrespect you in any way, but if you're self-taught, and your prior experience is one man jobs working on small sites then I wouldn't expect the quality of your code to be great. I would be wondering how much time it would take to ensure whatever you build is really readable, documented, fully tested, maintainable, in line with the company's current tech stack, performant and scalable. The benefits of working at a large company is that they have products that run on massive code bases that are, for the most part, REALLY STABLE. They move slowly, but they also move surely. New code won't be scrappy and volatile. Old code can stagnate, but it's because it hasn't broken in years. All of these things are learning opportunities you can take with you even if you strike out to start/work at a startup.
bcbrown 5y ago
Do something small, submit on your timesheet, and then ask for feedback. If they don't like it, it's just a couple hours, so less of a big deal than a couple days or weeks of work. If you ask your boss for feedback on what's possible to submit on a timesheet, I'm pretty sure you're guaranteed a response.
muzani 5y ago
I consider refactoring as part of the job and submit it on the timesheet. However, be careful because as a junior you might be approaching it the wrong way.

andrewfromx 5y ago

Donate to them 20 gifted hours of your time. I’ll bet whatever passion project you make in those hours they will love and want to fund for real.

MathCodeLove 5y ago
Honestly not a bad idea. If I can find something I'm passionate enough about I think I'll do this. I'd be making something in my free time anyway - might as well make it something that could potentially make my time on the clock better. Thank you!
- noicebrewery 5y ago
  It's actually an awful idea. The whole benefit of working for a large company is that you DON'T need to sacrifice outside of your 9-5. This is that outdated grind mentality that managers sell to convince people this is needed to get ahead before they hand out promotions to their mates anyway. Secondly, and I don't mean to disrespect you in any way, but if you're self-taught, and your prior experience is one man jobs working on small sites then I wouldn't expect the quality of your code to be great. I would be wondering how much time it would take to ensure whatever you build is really readable, documented, fully tested, maintainable, in line with the company's current tech stack, performant and scalable. The benefits of working at a large company is that they have products that run on massive code bases that are, for the most part, REALLY STABLE. They move slowly, but they also move surely. New code won't be scrappy and volatile. Old code can stagnate, but it's because it hasn't broken in years. All of these things are learning opportunities you can take with you even if you strike out to start/work at a startup.

bcbrown 5y ago

Do something small, submit on your timesheet, and then ask for feedback. If they don't like it, it's just a couple hours, so less of a big deal than a couple days or weeks of work. If you ask your boss for feedback on what's possible to submit on a timesheet, I'm pretty sure you're guaranteed a response.

muzani 5y ago

I consider refactoring as part of the job and submit it on the timesheet. However, be careful because as a junior you might be approaching it the wrong way.