@mika_benjamin Hi, webdev here, feel free to DM any questions you might have. I can offer help regarding JavaScript and generally the ecosystem around it. Same for anyone else who might have the same need. DMs open.
@jennypotts I've been writing on my tech blog for more than a year now and the advice I would give to myself would be to not have too many expectations. People will like, not like, but most of the time they won't feel much about it. Don't let it get over your head. Write to teach yourself.
Testing is the bane of many developers, but you can start adding some simple and reliable tests in under 5 minutes in any application https://t.co/IenuATI1m2 #web-development #cypressio
Using JavaScript for styling (styled components etc..) does not mean style should go in the same file as the logic. Concerns still need to be separated.
@DavidWells Depends on the reliability of the people maintaining the project. For size alone, no I wouldn't. Developer time to maintain code is very high.
@acemarke@kyleshevlin I had the luck (?) to try both in different jobs, a heavily typed codebase with no tests and a heavily tested codebase with no types. The first was way easier to get comfortable with. I find it less time consuming to add tests later than types.
@DavidWells True, but if a null has the chance to be the param it should require an if statement to detect it. Otherwise the code would be unpredictable anyway, regardless of the error.