1,440 karma · joined March 25, 2014
Aside from mitigating local dev accidentally pointing to the prod db, if you have the db accessible externally means it’s susceptible to network attacks and password attacks
> Rails is a great framework and the productivity is unmatched, but with time a 2-3 years old Rails project is always tricky to maintain.
It isn’t any less tricky than a Django or Express project. With any codebase discipline and regular tending to the garden of code is important to prevent weeds from growing.
If anything that Ruby (and Rails) has going against it is still the raw language performance and higher memory requirements/usage than its counterparts, which makes it less desirable for workloads that require low latency or small memory footprint
So you’re saying, we should be paying engineers in Europe and in the US the same as an engineer in LATAM or India or Asia that has the same level of experience and skill.
The only way to be non discriminatory is to have a standardized formula of compensation that takes into account cost of living (rent, food, healthcare, taxes etc) where the final take home pay in locations around the world are equivalent - which I believe should be the case at most companies
Software needs to be maintained. It is ever evolving. I am one of those that will not use a library that has not been updated in the last year, as I do not want to be stuck upgrading it to be compatible with Node 20 when Node 18 EOLs
Without knowing the details if your project and team, I’d take a monolith any day over 400 microrepos and the 70+ backend microservices. Our customers don’t care if it’s microservices or monoliths as long as it works and meets SLAs, so the question really is do I want to upgrade ruby or rails 400 times and deploy 100 services or just do it once in my monolith and deploy once?
Need to upgrade a gem that’s used in 100 of those repos to address a CVE - no thanks. Worse, 10 of those repos were owned by someone who left the company a year ago and since there were no PRs, no one knows how to work in the repo or understand what it does.
Tldr; scrum is another tool in your toolbelt you can reach for. Some teams work better with scrum, some dont. Experiment and see which one works - ultimately the goal is the same which is a productive, well oiled machine, regardless of the ‘how’
Launch School is great if you want more in depth learning compared to a coding bootcaml but not a 4 year degree.
Many have doubted Elon Musk during the early days of Tesla and SpaceX thinking he was incompetent in running those companies and the goals were lofty. People still doubt him with as much ferocity as his fans that adore him. It’s super fascinating IMO.
That being said, I do think Instagram will have some success with threads the same way Reels has been successful in fending off TikTok (as in not made completely irrelevant). People who share on TikTok also cross post on IG reels for more views and for eyeballs that are not on TikTok. I think the same thing will happen, where there will be some crossposting. Twitter still has a large audience - that will still make it relevant for some time.
Tech workers on the other hand, say engineers, can easily get a high paying FAANG job without a 4yr degree - just spending time grinding leetcode or a coding bootcamp. Not to mention the RSUs, office perks like free lunches, WFH, on site laundry and daycare, flexible time off, no set work hours… come on
Even without RTO, people will still leave for other jobs if the grass is greener on the other side. If anything, WFH makes it easier for someone to go job hunting and do interviews.
If the environment is your downside to RTO - you’re reaching.
The loss in productivity when someone does 2 hours in traffic a day is probably a more compelling argument. Companies also have to stock their pantry, hire more office management, renew their office space leases.
Turning it around - would you also take a paycut, or even clawing back bonuses or past income if the company starts losing money?
Their market is probably saturated and perhaps declining that they are reaching for optimizations elsewhere.
- application instances
- load balancer
- database
- cache
- search cluster if application search is necessary
Sounds like any cookie cutter application to me, even modern ones. How is that complicated?
Not sure if you are in tech, but if you are, the tech job market is at an interesting point right now. Cost of labor is likely going to be trending down as companies stop paying top % for engineers, FAANG stops hoarding talent, and more people enter the job market from layoffs.
If you are able to shop around for a job and get a few offers, that will put you in a better position to negotiate. Just be ok jumping to one of those offers if you don’t get the raise.
There are plenty of teams that do standups async. I dont need to know what everyone else is working on on a daily basis. Not to mention a 15 min recurring meeting to start the day is soul sucking, especially when you hear the words ‘I have a blocker’ and it becomes a 30 min meeting
This is partially the fault of Tesla, but it could have just been any other car having issues such as running out of gas, or an engine failure, or a medical condition with the driver… and the result would have been the same. That being said, there’s obviously no reason for FSD to stop the car like that - Tesla needs to figure out these random stops in the middle of a freeway