That would probably help but imho isn’t enterprise grade software far more complicated than a small repo!
It’s like putting different kernel commands all together and shipping a shell file to someone who doesn’t even know about terminal
Talking of deletion...I mistakenly deleted production server, yesterday!
I was trying to create some AWS micro instance in Mumbai region which were for some reasons were not accessible. Eventually I had to create a mini instance. So I was terminating all those micro instances and some where by mistake one of my important prod instances got selected and boom.
Though I had an AMI created few months back and it took around 15 mins to get latest code working but yeah I learnt my lesson.
But again I think this is a bad ux from AWS where you can directly terminate any instance without any prompt or warning.
I hope they change it some day!
I'd suggest turning termination protection on across production instances as a first solution, and consider some sort of infrastructure as code in the long term.
Right now we sit in one open office where our maximum communication happens verbally which is the reason i am not very confident. Our slack/skype uses are very minimum. I think we should practise first with work from home twice or thrice in a week to see if we can actually go with working remotely kinda job.
This is the way to start, it will let you work through the communication changes.
In fact, you should make sure you have Slack setup with channels and things are well defined for people on what will go where and when etc. Have Slack be the tool even internally when people are in the office that they turn to and ask person X a question, versus interrupting his/her work by walking over to his/her cube. Getting that nailed down decently will make someone being remote so much easier.
I do agree you need to define a primary communications tool, but also leave others on the table. In other words, my team uses Slack for 95% or more of the communication, but most calls are done on Zoom because the experience is better than Slack, especially when we are doing things internationally a lot of the time. Slack does work, but it isn't as smooth, however, I use it a lot when it is just a few of us jumping on a call as it works great then. So you'll find tools that work, and just make it clear to the team and make it simple.
Other things to think about, make sure you have something like 1Password setup, so those shared "secrets" like production creds, or keys etc are all stored someplace secure where everyone can get to them. You don't want people sharing those over email cause Jane is out of the office today and needs access to it and forgot to grab it from John before she left.
Good luck, remote teams are actually more productive in the long run in my experience, but they are not free or without some extra work, especially in the beginning.
If your team is using both Slack and Skype, I think it'd be better to choose a tool and stick to it. Face-to-face communications can still happen via video for both tools, so you can still have that but it may just require more coordination and isn't as instant as in the office.
As your team slowly gets a hang of things, another thing I'd keep in mind is to make sure you keep the team motivated and maintain a good remote team culture, as remote work may feel lonely at times or team members may feel detached from one another.
There are some well-known remote teams that you can try to learn from, like Buffer and Zapier.
Absolutely, i will even double quote it,
"The thing about programming is that the devil is in the details".
Actually the problem is that in my workplace we keep on creating few mini apps where i get the html done by any ui dev which usually take 3-4 hours or something.
After that sometimes pluging it into a framework takes too much time, even though there are few api calls only.
I was wondering if there is any simple SPA framework available where i can just add a simple controller and few routes and voila app is ready.
In the general case, it's not really possible. However in specific cases it is. The key is in the fact that code reduces repetition. If it turns out that you build a lot of really similar SPAs, then you can write code that makes it very quick to churn out those SPAs. The problem is that nobody can write a general tool for that -- you need to think hard about your use cases and optimise the code to churn out those use cases. A good contractor may be able to build such a system. It would be costly up front, but could pay for itself over time -- as long as you get the analysis right and the SPAs really are similar.
This is pretty much how frameworks come into being. No (sane) programmer sets out to build a general purpose framework. Instead they start building code for a particular purpose. The framework is well suited for that purpose. Over time they add more generality to it until it's useful by a wide group of people. But the important thing to understand is that it's always going to be a more or less awkward fit for anything other than the original purpose. There was a great quote I saw somewhere that Rails is the perfect tool if you want to build BandCamp.
It's kind of unfortunate because what you really want is something simple so that you don't need expensive talent to use it. But the only way to get the simple thing is if you have the expensive talent to build it. But that's programming...
Its a very basic recharge app. So if its a spa i can give a very smooth ux without any reloading or anything.
Also i was thinking to add service worker so i can cache assets and giving it a look of a native app (like other pwa)
Basically idea is to create a very minimalist PWA.
What do you think will be future of Bitcoin 4 or 5 years down the line. I am not talking about cryptocurrency or blockchain, just bitcoin specifically. After hitting heights it has became more of a commodity/stock rather than a currency.
I think it'll continue to be a very volatile store of value. For as long as there is greed in this world the price will continue to fluctuate. The key is that the supply gets cut in half every four years, so theoretically, as long as people continue to want to purchase bitcoin it will get more valuable with time.
