Absolutely!
However, *TEMPER* your expectations. An impressive success for a new developer is the @ - on - a map level of contribution. Focus on making the absolutely minimal viable game first. You need extremely few mechanics to have a fun roguelike (especially if you make it yourself, and play it yourself!) When you get a simple "wander on a random map, smash monsters without being smashed first" game play done; it is time to start layering on the design. You can keep this up after the 7DRL - for the 7DRL, get the bare bones walking. It is incredibly important you can play your game yourself early - this is the motivation that keeps you going. Don't worry about your own spin. Make it beige-basic.
After a few months, you'll end with a huge ball of mud and realize you should have planned properly in the first place. So you'll throw it away and start over again and plan properly with engineering principles you learned. You'll design very detailed documents of how everything should work; and begin on a proper "clean" design. This will then fail with you never actually getting an @ to walk on a map as you were too busy writing PerambulationFactories to get any actual real code done.
Then, after throwing away the over engineered system that got nowhere; and the under engineered prototype that got tangled up in its own bootlaces; you'll be ready to tread the middle ground :>
Cf. https://en.wikipedia.org/wiki/Second-system_effect
My main complaint is too many people lead people to their second system first. Your first system should be the ball of mud that gives you positive feedback. If your first system is the bloated over-engineered system, it is really hard to have the desire to keep going.