wouldn't this be a good thing? I prefer my circadian cycles not to be disturbed by artificial lights and if i am reading this right, it is what happens with led lights. this would be different of course if i had no access to natural lights. glad to be corrected :)
Demonizing offshoring, nearshoring or reducing it to a cost saving strategy is ... terrible way of seeing it. It is about talent and talented people. And talent is everywhere. I say this because our company does nearshoring for the US from Argentina and Chile to US companies. We don't try to be the lowest price, we try to be as good as we can. If it saves our client's money, much better. But our goal is not to save our clients money: our goal is to deliver as much value as we can. We focus on frontend: we have 2 master classes a week about topics like debugging, communication, teamwork, data viz, javascript... We have english lessons to improve communication skills. We try to give back contributing to frontend libraries by fixing bugs on those libraries and sponsoring their devs. We have created open source tools like https://grid.layoutit.com/. We put our souls on this and we are very fortunate our clients trust us and value us. We are not the only ones doing this and doing it as good as we can. The base of business relationships is about mutual benefit.
I am a rails developer myself and I love rails, but this applies to rails too. Actually rails lowers this problems a little because it is an opinionated framework but you could same to Angular for frontend. In react case, you just have to build that yourself with the pros and cons.
Innovation doesnt come from adding a library to the package json.
You are a member of a big team, not a single dev on a pet project. Innovation is on the product, not in your developer experience (unless you are creating a developer tool). Consensus to make big decisions is not the way to limit your developer skills is the way to align a team to achieve a common goal. :)
The problem is not about react or not react, the problem is how to align big team to create an application.
If a big team is going to be working on it you need some strong opinions around it. Do not mess with the package.json. I cant stress this enough. Actually, the most important file in your whole application is the package.json. Almost nobody should be allowed to add additional dependencies because is the main point to generate chaos and problems in the long term.
Also, the design system matters a lot. Have a small team working on the UI components to tailor and extend the design system. Dont allow the rest of the teams to extend the ui components with new libraries. Stick with the design system
as much as you can. The rest of the teams should minimize the amount of CSS they have to write to components placement.
Usually the datagrid is the soul of any enterprise application. Choose it wisely and be sure it covers as much functionality as you can and also that it is customizable on an "easy" way. There is always a team with the need of a datagrid that sorts, groups, filters the data with dynamically adjustable cells and multi header items without pagination. Welcome to hell.
Use one pattern: hooks, central store, whatever you want. If at some point you have to change it you have to know which teams are using which one. Dont allow team members of the same team follow different patterns. Code reviews must take care of this.
Hope this small tips help one or two teams out there. I have worked on the migration of 5 big enterprise applications from angularjs to react or from legacy desktop application to react or from server pages to react.
I made a lot of mistakes that costed a lot of dollars. I have tried to learn from them. Also, dont take me very seriously, I am pretty sure I am about to discover another mistake I have made.
It depends on how effort do you want ton invest on your data visualizations. If you are looking to create a dashboard with some charts and not very specific UI requirements on them you can use a data viz library (recharts, vega, C3, highcharts, ...). If you need to go deeper with more specific requirements on the charts ui, the interactions with other UI elements and/or optimize for high volume of data D3 is the best path. If you want to create your own unique consistent experience you would probably even invest on your own library on top of D3. You can have the base of that library in 2-3 months period with the basic charts: barchart, linechart, scatterplot, pie, ...
I run a small dev company. This is the first lessons we teach our programmers. If your code cant be understood by someone else with minimal efforts it is not good enough.
I am a spaniard. I currently run a business on ruby on rails-ember.js development based on Madrid and I also lived in San Francisco and Chile for a year in both cases. So, I will share my experience in three basic elements: life quality, tech community, business management.
First, about Madrid. Madrid is a really beautiful and nice for living city. You can work hard and enjoy the life at the same time. You dont need that much money to make a decent living (1 - 1.5k€/month). There is a decent community for developers. Moreover, the developers technical level is good or pretty good. Finally, starting a business and managing the business is hard. It is hard because you start paying those 300€ month that sometimes are a big wall. Also, there is a lot of paperwork: taxes every 3 months, hiring someone is the hell, requesting money requires more money in prints than the amount requested.
Chile: The quality of life in Chile is not as good as I expected. The people here is pretty familiar (closed circles) so engaging with new friends is not as easy as in Madrid or SFO. There is a lack of cultural life in the city.
The tech community in Santiago is growing fast but still small compared with Madrid and thousand miles away from SFO. The tech quality is also mid-low.
The management of business on the other hand is very easy. The main problem is when you come here without a link to Startup Chile Program because being a non-tourist here is really complicated. You need a kind of id number - RUT that cant be get until you 5 months after you arrive if everything goes right. You cant have a telephone number, internet or bank account without this number.
SFO is the heaven and the hell at the same time. Lots of interesting people around from everywhere. I was living on hacker community that made my living fun and interesting. The main probloem is the cost of living in the city. And this is a HUGE issue in the midterm for the tech community in SFO. It is too expensive. The community in SFO, no words, just amazing. (I dont say anything about creating/managing business because i have no experience).
Hope this small and partial insights help anyone :)
I found this project really interesting. Forked it. It might be interesting to create platforms like this for the very commmon uses-cases: ecommecrce, blogging, CMS. Currently there are solutions for all this use cases in the rails community but imo they are pretty directed. I mean, they are "difficult" to modify. I would like something like rails composer where you can configure the basic elements of the platform without custom generators.