About 3 hours. We have a CLI tool which is essentially a wrapper around docker and containers. It also manages DNS so that containers (backend, frontend, microservices, etc.) can talk to each other.
We also have "medics" who are people who have been around a while and know how to debug and troubleshoot issues that arise. As well as some documentation to assist. The documentation could be better, though.
hey OP I had a similar situation to you, except I was still working while making the transition.
Background - IT degree comprised mainly of electives from a Law dual which I ended up dropping. Worked as a business analyst for 4 years and before that in IT support. All at the same pseudo-govt body.
Over the last 1-2 years working there, I spent my days at work just surviving. Enough to get by. The nights & weekends were spent building product(s) that I tried and failed to launch as startups. I had pretty much no programming exp. but grinded through it. Started with Ruby on Rails, rebuilt the same app about 3 times. Then moved to React front-end and Rails backend. Built that one twice.
Eventually worked up the courage to start applying. Made sure my resume/interviewing focused on two things:
1. my experience working in a team environment and solving problems (i.e. my BA work); and
2. my experience building web applications as seen by examples that were deployed. In answering most tech Q's I referred to things I had done to get my web app to work which were similar.
I now work as a front-end (React) dev in an awesome company getting paid well and building interesting things. I've been there for almost a year now.
You may need to grind and it will be frustrating but you can do it. Good luck.
Does a 304 with Fetch have a status of OK? Reason I ask is our middleware in our redux app would treat this as a successful request and then consequently dispatch a FETCH_SUCCESS action. Re-renders would still occur.
That said, the middleware could be updated to specifically handle 304s differently.
>-Finally - be humble and be accountable. It is always your fault, because you are accountable for the success of your product. Don't throw your engineering team into the middle of a sh*tstorm of management politics - be their umbrella. Don't blame customers, politics, or resources. It's always your fault. Find a way to fix it.
Man, I would love to work for someone that actually strives to do this. Awesome.
In regards to your proposed workflow, I would prefer to have "the API" use a webhook to let the App know that the email has been verified.
This way I can update a user record and make a nicer experience the next time the user comes back rather than having to make a call to the API to check they are verified.
Rails for my backend and react/redux SPA for my frontend.
I was using Rails for both but I love the freedom, ease, and capability that comes with React.
I could move to using something "lighter" than Rails on the backend but I really do like the 'batteries included' stuff that means I don't have to think about much to get up and running.
My agency has a particular focus on working with startups to build their MVP. It can definitely be done and there are a lot of great suggestions in this thread. A few key things that we look for as the people on the other side of the table from you:
* Clear understanding of the problem you are trying to build an MVP for
* Wireframes / UI Mockups / User flows / User stories are so, so beneficial
* Being open and realistic in regards to timeframe which depends on the complexity of MVP
* Willingness to communicate often and stay in touch regularly throughout the build.
Happy to discuss offline if you'd like to talk about it more. My email is on my profile. We're based in Australia.
> * Build relationships with people. Be their friends. Talk to them about non- work related things
Making friends and socialising is not something that comes easily to me so this is something I have been actively working on for the last year and it has had a profoundly positive effect on my work-life.
I am still amazed at how much more willing people are to go out of their way to help me work-wise when we have even a small(?) personal relationship.
Your title suggests that due to your own experience that _all_ email newsletters do not work. I believe that might be a bit of a narrow view. In fact, I'm sure there are expert marketers which would strongly disagree with this.
Perhaps a better way to phrase things would be "how to make my newsletters more engaging?". Have you tried researching the topic? There are lots of resources online about "growth hacking" and email marketing.
Perhaps I'm a bit cynical but this seems like a clickbaity contrived effort to promote your site.