The assertions are quite generic to the point you could apply them to most pursuits or hobbies.
I think there is definitely an interesting link between coding and creative writing, but to me it's the way it scratches the same itch of producing something out of nothing, of the planning and different approaches you can take. They are similarly rewarding to me.
In all other ways beyond the surface level of yes, both involve writing words, I think they're wildly different. My anecdotal evidence is I find it very difficult to swap between writing code and writing fiction on the same day - I am either doing one or the other, and I feel it's because of how differently the brain works in these 2 modes.
If anything, I think coding has stronger similarities to maths, and it's just interesting that many coders also do creative writing - which I'd attribute it mostly to an intersection of people who like science fiction and also like making things.
Your comments are very reminiscent of non-technical managers I've known - they often have a very shortsighted view of the value of code reviews, because they don't need to work on the code.
'It works - why don't we just merge it? Keep velocity high!'
A code review is exactly where it's worth spending time making sure: the code is maintainable, doesn't degrade the quality of the repo, and above all teaches the junior things they can use next time to do a better job faster.
Spending some time using a review as a teaching experience pays so many dividends later. People who don't touch the code don't understand that.
Of course, there's a level of 'good enough' a senior should be able to identify and approve. But the bar should be high.
Your and some of the other comments I've read are very reminiscent of some of the worst senior developers I've worked with, because they treat code reviews as a way of molding the code base to their own personal expectations rather than improving it especially when a junior engineer finds fault in their code. They waste time using code reviews as a teaching exercise that gives bad habits to junior developers that need to be broken later.
Why? His comment was the perfect description of what a senior developer should do during a code review.
Code reviews between a senior and junior are teaching exercises and always should be. It is critical and a fundamental step for juniors to be become more experienced.
As already written by the comment you replied to, the right balance has to be found, but this is part of the job description if you call yourself a senior developer.
I'm planning on posting a blog about my experience here at some point, but it was fun. You can find a draft of it on the site if you're interested in my thoughts on using it as datasource for an app.
Basically, I agree - you need to use DaVinci to get good results and it's expensive. That means restricting the amount of queries a user can make (I do it through restricting the inputs a user has) and saving the results, so other users get the saved results instead of hitting OpenAI.
For more free-form inputs, I think the only option is to make users pay a small fee (which is tough, because even DaVinci struggles sometimes and I don't want users paying for errors). I'm also experimenting with AdSense but I doubt it'll cover the costs.
I wouldn't say I plan to 'make money' but with luck it might be my first side-project that will break even
Also a layman but my understanding is the issue is 'percent of emissions' part of the fact. The emissions are methane, which are 'worse' than CO2 - so some statistics normalize for this and result in a high % of emissions. I think it's semantics and bad-faith actors use the wording that helps them the most, which muddies the waters.
The previous Premier of the state (Gladys) resigned due to corruption. The new premier is involved in a plot to give sweet fake jobs to his political buddies, as well as various other schemes. The previous Labour government got swept out because of massive corruption. At a federal level, NSW politicians are involved in water grafts (Angus Taylor and barnaby Joyce) as well as huge handouts to nonexistent companies (great barrier reef foundation got 700 million dollars with no office and 5 listed employees and have done nothing visible with the money - except to say that it's been spent). NSW is very openly corrupt at all levels of government.
I thought the opposite - the underground city was the highlight of my trip to Turkey! Being down where people have walked for thousands of years, imagining the living conditions and what would make people do such a thing (e.g. retreat for decades to hide from an occupying force), was incredible. Sure, visually it's just holes in rocks - but so are a lot of other things worth seeing too.
Agreed. My company has a (relatively) mature MFE platform, and it rocks. The MFE team handles builds, deployment, and can build features like experimentation into the platform, so the teams can focus on the MFEs.
The MFEs are not arbitrarily small - they are related to specific experiences. A single MFE might be a collection of pages in a flow, for example.
It means less work for devs, more consistency across a big company, and much safer deployments - the worst thing that can happen if you ship a bug is to tank your MFE because they're all isolated. At a big company, being able to change something small on your MFE and push to prod without worrying about every other page in the site is awesome.
The assertions are quite generic to the point you could apply them to most pursuits or hobbies.
I think there is definitely an interesting link between coding and creative writing, but to me it's the way it scratches the same itch of producing something out of nothing, of the planning and different approaches you can take. They are similarly rewarding to me. In all other ways beyond the surface level of yes, both involve writing words, I think they're wildly different. My anecdotal evidence is I find it very difficult to swap between writing code and writing fiction on the same day - I am either doing one or the other, and I feel it's because of how differently the brain works in these 2 modes. If anything, I think coding has stronger similarities to maths, and it's just interesting that many coders also do creative writing - which I'd attribute it mostly to an intersection of people who like science fiction and also like making things.