I would think web apps have the major advantages, and have for some time.
Seems to me the biggest draw one would be see how you can retain the people that are willing to go the extra mile to download your app. You must be solving a problem for them in a significant way. A web app is a quickie, it's useful or isn't. And besides the reasons why they are useful above, it helps you to fail /or/ scale faster.
I thinking being transparent about it and highlighting how it could be a good thing for them down the line (Interview Question: "How do you handle challenges at work?") if they do improve the things you're noticing. Provide evidence of why you think that and say they aren't in trouble, but we want to improve the quality of your work in this one area.
- Hey X, I brought you into today to talk to you about something I noticed. There is an issue/errors with your work, when doing Y[provide evidence of common errors/average errors of others], I just want to say you're not in trouble, but we want you to improve this area and wanted to make sure you were aware of it.
- I want to extend any resources I have available for you to improve in this area, and of course I have some ideas, I wrote everything down on this paper/email.
- You can come with a plan of your own. Or we can collaborate on it--if you're not sure why issues are happening. Take some time and think about it, and when you're ready to talk about how we might ago about improving in this area, please schedule some time with me and we can work on this together.
I only see him valuing the pipelines themselves, and perhaps not as strong of a shift into absolving fossil fuels like everyone expects. Humans are slow to change and adapt, I mean look at coronavirus and masks in the US.
Natural gas is great because of the low levels of emissions, the not so great aspect is fracking continuing to mess up peoples homes, i.e. flaming sinks.
Those that are in control should advocate for the publics best interest imo.
The not so great aspect of gas is that its a high carbon fossil fuel that causes global warming. 490 gCO2-eq/kWh is not even close to low. Low carbon sources have lifecycle emissions closer to 10.
I disagree, I think side projects are a sign of being able to put their head down, day in - day out. They have a certain divergent way of thinking that I think might be significantly valuable for companies looking for that type of thinking, especially in a crew of people that don't maintain and assist open source or create their own side-projects. I think this could go either way of course, but it's not a set in stone thing to say side project-people are a 'type.'
I will agree with the balance issue, I do think they can tunnel vision, as I'm guilty of it. On trying to create features they feel they need. WTS, I feel strategic in my cause of prioritizing what me and my users could benefit from.
We've used it for several years after switching away from it for Docdb last year and then back again in November. We've had applications running on both MongoDB and AWS continuously through 2019, but our clients and team in general needed certain things: Ddb doesn't support everything we've done w/ mongo in the past. Our team also feel it's easier to integrate and translate to clients.
Well most things still work through API calls (Postman), but the front-end for the CMS might be ready in the next couple months. Right now is the only administrative UI component is the upload form that lets my wife upload her designs.
The source file content is served from disk, and everything else from the database.
This is an important point, and kinda scary; because I'm now actively aware of it and how I haven't viewed it this way before.