347 karma · joined September 22, 2017
(Sidenote: having this kind of architecture where you create layer of deps from one team to another is a bad idea from my point of view, but is still done a lot)
If you are big in one state in the US. You have the same lang and most likely the same regulations. In Europe its so many languages and its no more likely that we choose a company from another country in the EU vs the US.
I think that is not true for the US. So its easier to get big in the US, and then you are so big its actually likely the a company in the EU would choose you. Maybe not over another company from the same country (everything else beeing equal), but over a company from another country in the EU/Europe
How are the deployless senario now? Where you first serve only yourself then your team, then beta, then everyone... Or something similar to that. I really liked how that story was told and how much complexity it removed
Making hard connections between the editor and the lang was interesting also. Seems like they have moved away from that.
Hope there is a easy way to set it up locally, i was really intrigued when they first launched
Only 1 commit :/ Would love to see the prompts and how you iterated on this
Context and nuances
Any job, In any industry at any level should be working together with your manager to understand what the company goal and how to achive that. Its always going to be time/price vs quality if you work on creating software or clothing or whatever. There are properly companies and managers that do not care.. but imbany healthy organisation this should be the case. There is not garbage tasks. Its tasks that needs to be done. Any understanding that not all tasks that needs to be done in an organisation is fun but needs to be done is a sign of maturity that you want from your employees
Context always matters.
well done, will try it out!
Getting it to tell a story and mask the keyword somehow worked for me up to level 7. But i seem to be stuck there
I guess you are from the US and not EU? It's when they get too big and abuse their monopoly they will be regulated.
AFAIK nvidia have not done anything to abuse its power yet, but its hard for big companies to not use their monopoly in a illegal way since its always a good a Market strategy just illegal
But keeping the site up also cost money. So context is really important here. How much money do you spend on the last % of availability vs how much money so you loose on downtime. In my experience people have a more complicated setup then needed because of availability, but at the same time have not tested a real DR scenario.
Using devbox myself and very happy with it.
Would be great to hear what separates flox from the rest.
But it do not seems to have gotten the love I feel it deserves from the nix community.
I agree that they use price to regulate demand. But they want to sell as much as they can. So if the price is too high they will not sell out all cars. And they can afford to lower prices more then many of their competitors because they earn more per unit sold then the rest of the field [source: https://asia.nikkei.com/Business/Automobiles/Tesla-earns-5-t... ]
[1] https://asia.nikkei.com/Business/Automobiles/Tesla-earns-5-t...
I have chosen another part where i deploy and then it's automatically push to git. Buy windmill proves you with 3-4 really good ways of deploying from 1 cowboy just doing what he wants to the normal EE way of doing software meaning code-in-git and people only have read access to production and can not modify things. You can have separate instance running or just separate workspaces and promote.
I do not believe the EE version pings back either as of now. But I think the plan is to report back with usage. Or i need to report it manually.