If choosing what to have for lunch is making you involve your imagination and analyse choices, then I guess it would fall in the category of art.
And due to restraints of time, budget and prior experiences, you might go for default choices anyways.
100 karma · joined January 13, 2017
If choosing what to have for lunch is making you involve your imagination and analyse choices, then I guess it would fall in the category of art.
And due to restraints of time, budget and prior experiences, you might go for default choices anyways.
You make similar kind of choices while programming as well. Hence, programming is definitely an art since there are many ways something can be implemented, almost to the level that you can recognize who has written the code by seeing the code itself. Most such programmers don't even have the visibility to higher level goals of the org they are working in, I used to be in this group earlier.
I remember it used to be a 'problem' for a lot of senior developers, who used to ask for consistency in how code is written, like spacing between keywords, indentation, start/end of parenthesis, naming convention, etc. Wondering if they'll settle for more 'Soul' in the code now :). Or maybe, they have permanently shifted to the other groups now - where only the output matters.
I very much doubt that they listen to countries in tier 1 and 2 also. If not for the fear of US's relatively stronger regulations, don't think Meta would even pay attention to any complaints in US either.
This would not change with the change in leadership in Meta simply because 18Bn is fairly affordable for Meta's scale, but they should be worried about setting the legal precedent (though they denied any wrong doing).
Other countries may not have the same ability to impose penalties owing to their weaker laws also.
Wondering what happens when tomorrow AI accepts and learns from the feedback and gets trained on all the failed initiative as well. It wouldn't be so hard if failed (something which wasn't right at all or hasn't got the traction) projects and ideas are all listed somewhere for an LLM to scan through. LLM may finally figure out how to add personal scars, hard decisions and personal insights which can be personalized further.
Also I don't think it might be so undesirable for an org, if there is a system which observes and present hard facts based on last quarter or year JIRA (pi planning and sprint planning) and commit histories.
"What happens at Grandma’s, stays at Grandmas" - Highlight of the article, best line I have read today. Made me smile and heavy at the same time.
I was interested in similar thoughts around definitions and scopes long time ago https://www.experts-exchange.com/articles/4182/List-vs-Categ...
Something may look obvious to you unless you get into definitions (stage 1), discussions about definitions (stage 2), trying to get alignment on definitions (stage 3), and so on.
If you are supposed to stay on frontend for long, then it is critical that you learn DOM fundamentals, even propagation, caching, browser storage, layouts, etc.
Vibe coding is absolutely okay, just pace yourself to build only what is absolutely required (spend time on refining this) and don't get carried away too much with what claude can do.
Wondering how this applies to scenarios where regulation and risk analysis cannot be deferred, and you cannot plead ignorance later ;)
Completely agree with it.
> I’ve been thinking a lot lately about what software would look like if we made keeping software understandable to humans a first-class design goal in the age of AI.
It is already understandable if you are producing only required and necessary features. Understandability can be managed by scope control and not getting carried away with being able to produce more and more features.
I believe engineering teams will be working on trying to optimize for more engineering accountability in coming years, as the reality is catching up.
For example computers have been processing information for decades now, but only recently they have been almost-successfully accused of having (artificial) intelligence.
Intelligence was applied while writing the programs which process information (outside or before system even boots up), not while executing those programs.
Its only now with LLMs (and agents based on LLMs) we are noticing that systems can do intent extraction, intent management, and ReAct to it.
Having a good experienced team generally helps in mitigating some of them, especially in tough situations.
The terrorists made sure to ask the religion of the Sindoor before symbolically erasing it—because apparently, even brutality comes with selective targeting.
And in a poetic twist, the government and the Army honored those very women—while unapologetically ramming that same religion right back down the throats of the terror industry’s headquarters.
Though, it looks little far fetched making big conclusions on the basis of experiments that is basically about remembering letters.
- Asset economic viability i.e. you must be able to recover the cost.
- Ability to build and nurture a solid team that can deliver a product of reasonable quality and robustness.
- Find who your end-customer and paying customer is and whether this problem is light or hard in their head. Accordingly curate the right messaging for the product for marketing purpose.
- Ensure that there are no legal challenges.
It is one thing to take an idea to market when you are selling for companies like IBM, Accenture, Google, etc.
But when you have to sell the same idea on your own, that takes real skill and hard-work!