I like my react ecosystem better, it's more comfortable to me (and I've built it that way). Tonight I finished setting up jest the way I want it after ejecting create-react-app (which I've rarely used, but it was nice this time)
I admit that vuejs tooling is much simpler, since I discovered today a way to work with vue that required no tooling beyond what we have already (which is some typescript imports). Just export a config object, and go.
So, today I unwound the weird vuejs code my co-worker wrote and made actual, composable components, and built a UI out of it, with actual event handlers and data updates.
It's still mostly a mock up of the UI, but it's definitely advanced. Oh, and as of Monday, I didn't know vuejs at all. I'm not an expert now, but there's some transferable knowledge from React.
The paradox of productivity in 2018 is even if you're writing a quantum tech article whilst simultaneously dogwalking, podcasting your fourth Ph. D, & inventing the next revolutionary drudge-work-automating app (that will be consumed by a tech giant), you'll always be making not-enough per hour for a dignified existence.
No amount of neurohack pills, 180-hour crunches and AI assistants will ever free us, because neofeudal capitalism will consume all abundance.
The wheel must break.
I'm taking the next two days off of work to work on the project, my goal is to get it running again from loading the file to displaying one of the forms, with editing and saving back to the file.
All of that with tested code, and close to 100% test coverage (following some suggestions, I"m not testing some of the boilerplate code in my index.js)
Back in Nov, I got my home project working, realized it didn't work for the primary user (ME:) and tore it down.
I've been rewriting it more intentionally (Nov was a push for functionality over all else), and -- now that I understand the tech I'm using -- writing it with TDD.
I'm updating some tests and cleaning them up this morning, and its just so satisfying to see the tests auto run with error after error until they are green. It's like putting the last piece of a jigsaw puzzle together.
My Grandad's advice for safe driving was: "Always remember you're controlling a potentially lethal weapon". I think it helped me to take driving even more seriously.
Perhaps it's good advice for us technologists too...
"Always remember you're programming a potential platform for bullying and harassment".
"Always remember you're designing a potential system for mass surveillance".
"Always remember you're deploying a potential tool for mass social unrest".
Good day of hacking on my home project, I've got most of the unknown tech working, along with most of the scaffolding.
While all I have now is a list of folders from Drive, the stuff I needed to do to get that working was pretty large (some of it just learning/understanding things)
It feels pretty good. One more feature, and the google integrations should be mostly abstracted, and that'll leave just UI I've got vacation coming up so, hopefully it'll be usable by 12/31 as planned
I want to give the folks I'm working with a git 101 class, but I think they actually need to go to git preschool first.
The thing is, the reason & way we're using git on this project is in many parts the same reason & way git was created in the first place.
Distributed teams and a need to control merging at multiple levels.
But their git repository doesn't have an upstream of their branch on our repository. And the person "merging" those branches is cut and pasting files...
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!