Agreed - For the last 20 years or so, designers at basecamp.com do all of their frontend design directly in rails/html/css and then have the developers "re-implement it". The upside of this approach is designs which really work in the browser and they found it to be faster. The downside of this approach is that it's harder to find designers who have both of those skills, but that was an acceptable tradeoff for them because they are a smaller run company.
To me, it seems obvious that AI will attack this from both directions - upskilling developers to make more design changes AND upskilling designers to make more design iterations and more changes to the codebase -- the design artifact is "new react components" (which can be re-implemented or not) instead of a figma design.
1) commit messages often capture the "why" something changed - versus the code/tests which focus on the what/how for right now.
2) when you have a regression being able to see the code before it was introduced and the code which was changed at the same time is very helpful in understanding the developer's intent, blindspots in their approach, etc.
Agreed. Having a "HTML + CSS" engineer on the team was largely due to the number of hacks needed to make css work -- purposely adding invalid html that would only be parsed by specific browsers, ie5 vs ie6 vs netscape being wildly different (opera mobile was out of this world different), using sprites everywhere because additional images would have a noticeable lag time (especially with javascript hover), clearfix divs to overcome float issues. To be clear, I'm not saying "things were harder back then" or "css is simple now", but things with CSS were so wild and the tooling was so bad, that it what a unique skill of it's own that is less needed now, and the shift has been for people to focus on going deeper with js.
feedback: i'm trying to understand the highlevel flow/usage but still a bit confused.
ideas:
1) maybe add a .yml example to the readme under the /test_nyno screenshot so i know how you configured that workflow
2) what are ways to trigger a workflow? just tcp?
3) the example runs "bestjsserver" which looks like it runs workflows? are some workflows auto running? that just logs from tcp commands you manually running in other terminal? a bit confused what's going on here
If I'm correct that the data center shown is on Belfort and Glenn Dr, then you don't even have to "research" zoning, just look across the street.
In 2021/2022 before it was built:
* Here is what that lot looked like [1]. To assume something wouldn't be built there is optimistic at best. (And there was precedent for data centers at the time - there was already a data center less than half mile away on Vantage Data Plz across the street from Tart Lumber.)
* If you look across the street, ie if the video would have panned to the left, you would have seen the "US Customs and Border Patrol" building - not winning any architectural design awards [2].
For someone who bought their house decades ago, then yes - the area has transformed drastically. But grouping someone who purchased recently with someone who purchased decades ago is a bit muddled.
Also live near the data centers. While I'm obviously not 100% sure, I think that blue one is on Glenn Dr - for a bit of context, that is less than 3 miles (drive) from the Dulles International Airport. I'll see if I can record a video of the sound later tonight.
But there is an upside to this - you get the benefits of being a city with big business (tax revenue, donations to the local schools, investments in infrastructure), but don't have increased commuter traffic.
Would open sourcing the core IP of a company “typically” require board approval?
If a company goes under, the investors will want to sell off the IP, open sourcing everything would make that IP less valueable. There must be some blanket clause in the term sheet to cover that, right? Ie: founders won’t do anything which will materially hurt the company without board approval (or something, I am no where close to a lawyer, this is all conjecture)
"But these days the human cost is just another cost" - this is where I think you, "key_stroker", and the GP, "brookst", might agree on something, in my opinion.
If someone agrees with your premise that "these days the human cost is just another cost", then it seems logical that a newspaper editor/author will shape the headline about economic suffering, instead of mental suffering.
By adding more information to the headline about "$2 per hour", it might make the discussion more confusing by much of the comments discussing the economic part. BUT, a clickbait-y title might increase the reach of the article.
I'm curious if there are any podcasts/blogs/books which give "pricing ideas/strategies" based on a "risky" premise like this: keep it very simple and don't worry about theft, because enterprise customers won't steal, and the math works out.
Here's an excerpt of their pricing terms:
Do I need a paid subscription to use the images on Docker Hub for commercial use?
Images on Docker Hub can be used for commercial use, as long as Docker Desktop is properly licensed. Paid subscriptions are needed for commercial use of Docker Desktop at organizations with more than $10 million annual revenue OR more than 250 employees.
Find someone from [communications department], and ask them after the meeting - hey, can I pick your brain? Tell them you don’t understand and ask them to teach you. When they use high level buzzwords, ask “can you login to that system and show me?”. From my experience, they will be excited to teach you about their field and super interesting things can come of it.
I'm trying to connect Tailscale's product with their goal "The internal dashboard and CI system that will never need to be public-facing. The HR database that will always have far less than a thousand queries per second. The dozens or hundreds of devs that ssh or RDP into servers, not the millions of users being served."
Does this mean - instead of deploying a dashboard/ci to aws, I should host it "locally" on a single computer (macbook, raspberry pi) and then internal employees can access that site via Tailscale's network layer?
To me, it seems obvious that AI will attack this from both directions - upskilling developers to make more design changes AND upskilling designers to make more design iterations and more changes to the codebase -- the design artifact is "new react components" (which can be re-implemented or not) instead of a figma design.