47 karma · joined November 20, 2018
Feel free reach out: adamp319@gmail.com
Also hilariously, they're basing their whole argument off of this apparent "trend" that they haven't supported of mail-in ballot share shifting from D to R... But then they provide an example of Georgia, where... that isn't at all the case... and then gloss over it. Laughably bad analysis.
Took 20 minutes to confirm the "trend" and immediately none of the following states follow the "trend": Alaska, Florida, Hawaii, Illinois, Indiana, Maryland --- aaaand I've stopped looking because this is silly.
Full disclosure, this was just a quick visual inspection of the data presented, plotting x='vote_share_dem' against 'timestamp'.
https://blog.twitter.com/engineering/en_us/topics/infrastruc...
https://romelperez.com/talks/javascript-animations
Pretty neat.
It only makes sense if you're absolutely sure you'll never need to extend or change the interaction between front-end and back-end.
Think just about schema migrations on the database. If you change your schema, you have to change your front-end. Maybe that's okay for the time, but that can get out of hand pretty quickly.
On the other hand, with a service layer, you could completely decouple that dependency on the front-end, by providing the front-end an interface (the service layer / API). The migrations on the database layer don't affect the front-end whatsoever, because the front-end communicates with the interface. You can change the underlying implementation without changing the front-end's interaction with the interface.
http://best-practice-software-engineering.ifs.tuwien.ac.at/p...
As others have said, the ideal route is to validate the market first, and guarantee customers before effort is committed.
If you'd like to tag up, just to chat casually about the idea or just entrepreneurship in general, feel free to e-mail me (in bio).
I kind of hate the scrolljacking. It's too flashy. It's sluggish. It is kind of distracting. I think the small gif of the kanban is much more effective, and the rest of the copy is too.
Maybe a bit of top padding on the 'CenterCallout' where you say "Writing is just one click away" and "A new way to note".
You might want to sprinkle one or two more calls to action for purchase or trial in between some of the feature descriptions.
Otherwise, the kanban setup for chapters and such seems really intuitive and I'm surprised I haven't seen that before in this context. I'd definitely be interested in giving it a shot. Maybe paying the $8 will encourage me to write more. I'll bookmark it to check out after work!
How do you test the efficacy if you don't know who you're injecting? Maybe it works really well on a certain population, and reacts harmfully to people with some pre-existing genetic trait or condition. You wouldn't know, because you took a random set of volunteers.
If you're going to counter and say "we'd still do the pre-analysis on the volunteers"... Well, that's what takes time.
For example, perhaps you have some poorly written legacy service that has a memory leak. Let's just say for the sake of this argument, that any sort of boolean indicators (e.g. checking if the process is running) will give you an 'Okay' or green. You are still probably interested in monitoring the memory usage to make sure the service is operating correctly and/or performant. After monitoring for some time, maybe you determine your ops engineers are taking some action whenever the memory gets around 80% or something... then you can setup the trigger event. But without that manual monitoring upfront, you can't just magically set that threshold.
Build things you want to use. Or build things other people want to use. Do practice problems online (LeetCode, Project Euler, etc.). Read more documentation.
Pick a tech stack that you want to become an expert on (preferably an employable one), and start learning. Buy the books.
It sounds like you're feeling a lack of confidence in your knowledge and abilities, and the only way to improve those is to continue learning and improving.
One other consideration is: do you spend a significant amount of time on repeated processes? Perhaps during development you're 1) logging into your database, 2) dropping some tables, 3) re-running some tests that populate the database, 4) viewing the results. Can you automate such processes? Can you put together a few scripts or utilities that make you more efficient? Can you find boilerplate or scaffolding that gets you 20-30% of the way there rather than starting from scratch?