5 ms·

For me it's the following: I want to improve my APL(Dyalog/co-dfns), Rust, and Coq skills to passible levels, i.e. being able to comfortably use them and writi

For me it's the following: I want to improve my APL(Dyalog/co-dfns), Rust, and Coq skills to passible levels, i.e. being able to comfortably use them and writing code in an idiomatic style. I also want to improve my skill with SystemVerilog and VHDL. I'm decent with HDLs but I need a lot of work with regard to my testbench writing, translating specs to a TB, and using the random constraints based testing(similar to property based testing in the SW world). I'm trying to properly pick up C++ template meta-programming and improve my familiarity with minimal to zero cost abstractions w.r.t FP and HOF. Outside of programming skills, I want to start learning some project management skills, i.e. feature breakdowns, timeline estimation, and the basics of when/how to pivot. Finally, I'm trying to learn how to tell when I start falling into one of my biggest issue as a developer and how to curb it: getting stuck on an idea and overlooking better alternatives. It's a bit to take on but I'm young and don't have too many commitments so I figured it shouldn't be too unachievable.

raybb 7y ago
> getting stuck on an idea and overlooking better alternatives Care to elaborate on this at all?
- jacoblambda 7y ago
  For me the issue basically boils down to getting hung up on a certain way of doing something or implementing some feature/subsystem. An example is reinventing the wheel in a (what is in hind sight) pretty janky way of handling dependency injection because I for whatever reason was hung up on minimising dependencies. It was in C++ and within a month I had realised my mistake but the damage to the code was already done. I should note that the overall principle of my design/decision I still think has value but it was implemented poorly due to entirely pointless self-imposed constraints. I've gotten better about this but I still occasionally see myself getting hung up on what are ultimately pointless details and self imposed constraints. One of the problems for me has been finding where to draw the line on my self imposed constraints since a lot of them help me write better, more maintainable code but when taken to extremes they can occasionally negatively impact my work and cause long-standing technical debt.

raybb 7y ago

> getting stuck on an idea and overlooking better alternatives Care to elaborate on this at all?

jacoblambda 7y ago
For me the issue basically boils down to getting hung up on a certain way of doing something or implementing some feature/subsystem. An example is reinventing the wheel in a (what is in hind sight) pretty janky way of handling dependency injection because I for whatever reason was hung up on minimising dependencies. It was in C++ and within a month I had realised my mistake but the damage to the code was already done. I should note that the overall principle of my design/decision I still think has value but it was implemented poorly due to entirely pointless self-imposed constraints. I've gotten better about this but I still occasionally see myself getting hung up on what are ultimately pointless details and self imposed constraints. One of the problems for me has been finding where to draw the line on my self imposed constraints since a lot of them help me write better, more maintainable code but when taken to extremes they can occasionally negatively impact my work and cause long-standing technical debt.