![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mom always said that if you've got a family, you help each other
*cracks neck*
Okay, if I'm seriously going to let myself flip out and go all test engineer on DW, there has got to be a better method than "clicking random things and see what's not there/what breaks". I mean, all I've noticed thus far is that a significant number of the FAQ pages have nothing, but I'm chalking that up to "omg, documentation and my damn code isn't working and I will deal with this later".
I have spent enough time debugging Verilog code to understand that sentiment completely.
Seriously, I'm in this state where I want to help, but I'm far too used to getting handed a testbench and told "go do this and report back to me". Ugh, it's reminding me of some of the choices I made in choosing to go straight hardware. (Beyond some vague mumblings about learning Python one day, all I know is Verilog and that's very much a hardware language, so unless DW wants me to design chips for them, that skill ain't seeing much use here)
Is there a way to figure out what seriously needs testing, go test it, and then come back with a stack of data on what works and what doesn't?
Okay, if I'm seriously going to let myself flip out and go all test engineer on DW, there has got to be a better method than "clicking random things and see what's not there/what breaks". I mean, all I've noticed thus far is that a significant number of the FAQ pages have nothing, but I'm chalking that up to "omg, documentation and my damn code isn't working and I will deal with this later".
I have spent enough time debugging Verilog code to understand that sentiment completely.
Seriously, I'm in this state where I want to help, but I'm far too used to getting handed a testbench and told "go do this and report back to me". Ugh, it's reminding me of some of the choices I made in choosing to go straight hardware. (Beyond some vague mumblings about learning Python one day, all I know is Verilog and that's very much a hardware language, so unless DW wants me to design chips for them, that skill ain't seeing much use here)
Is there a way to figure out what seriously needs testing, go test it, and then come back with a stack of data on what works and what doesn't?
no subject
no subject
no subject
no subject
no subject
no subject