I have started to wonder to what degree programming discussion online is astroturfed. The financial incentive to flood programming discussion (any discussion related to work) with pro-AI messaging, and the simultaneous ease with which AI makes it to do so, makes it hard not to ponder what amount of seemingly organic pro-AI sentiment is not.
I'm sure there is some that is indeed genuine. It could even be most. But I'd be surprised if it is all.
The comment reads like flesh-generated language to me, but I might be fooled. The breadths of pro-AI sentiment is possibly astroturphed, but there's also an argument for an enthusiastic minority of people to write a lot more comments.
As the person above said, AI has significantly increased my ability to execute on ideas. I always liked computers, always liked building things, but was never that great at coding, and was never that good at going super deep into one topic. Instead, I have broad knowledge of a lot of things like product design, requirements engineering, devops, security.
I work with a fully agentic flow, but I would argue very seriously; My job has not gotten easier, I am doing at least as much hard thinking as before. From assisted RE over design (TDD focused Spec), implementation by agents, review by agents with partial human oversight, I have a speedup of maybe 50-100%.
More importantly, I can do things I couldn't do before. And when it comes to performance and defect-density, it is comparable to very senior people I couldn't touch before. I do agree that the code doesn't look like a human would write it - too abstracted, sometimes convoluted, often way too dense. But it isn't worse code, and if you accept that no one has to read that code ever again, then it is good. Agents are able to grok it just fine.
Out of curiosity, can you link to a publicly available furry work to help someone curious get into it? And help to know what to look for to appreciate it.
It really depends on your taste. If you want to be up to date with the latest stuff, then browse profiles on bsky or Twitter. furaffinity.net is a bit old school, but still active. e621.net is where you can find lots and lots of stuff and there are tags, but I rarely actually browse it.
My first experience with furry was a Tumblr blog of a guy who reposted art he liked and had exactly the same taste as me. Tumblr is a dead wasteland now though.
You'll have to browse through a lot of trash, but once you get a decent list of artists you like, your experience will improve dramatically.
Sounds a little vulgar, but IMO you should start with things you find sexy because you'll enjoy it even if the quality isn't there. Once you get a foot in the door, you'll be able to look for decent art that isn't porn.
Also, artists tend to be overworked and overly sensitive, which creates a lot of drama. Just ignore that.
Wikipedia is maybe the narrow end of a wedge into this topic but the controversy revolves around a very large and very complex paper that few people are equipped to understand and some of those who are able believe the proof is false.
I’m also interested in a study as I also have ADHD and this is also my work loop. I tend to cut up and serialise rather than parallelise. I can not deal with the degree of context switching described in this blog post. I’d have felt frayed within two weeks.
No you misunderstand me. I support such a view but cannot hold it because my pace at work is so much fast. And hand coding like this will make personal projects s slow and choreful with no visible progress. Like where is the joy in that?
Without an active harness (eg. Appium) that can end-to-end deterministically verify the changes you make continue to work correctly it is almost impossible to continue to keep the same pace on the app.
Unsupervised LLMs (even fabel) are categorically
incapable of running parallel unsupervised mobile app feature development.
That is my personal, first hand experience working in a team in this space.
What you are (I guess?) experiencing is user-in-the-loop light touch LLM development where you can 80% most tasks quite quickly (much faster than without assistance!) with a small number of human developers working on largely unrelated features and manually verifying they are correct and manually fixing the platform specific issues you encounter.
Maintaining a strong appium end-to-end test suite is still extremely challenging with notifications and maps.
Honestly, it blows my mind you could even being to claim that of all things, native apps using obscure languages like swift are suitable for this, compared to the much much easier path of web + react.
You might say “yeah yeah, but one month? Come on!”
…but have you actually seen how much code fabel can write in a month?
Its a lot.
So sure, you say, work at a slower pace. Don't just endlessly run a frontier model in unsupervised feature development mode.
Yes… you see, thats the point. Thats what the op is saying.
Move more slowly, and you can avoid building a spaghetti castle (ok sure! If you dont wanna, maybe don't retype every character by hand, but the point of that practice is not upping your wpm typing speed. :p It is to take the time to think, design and collaborate, not rush rush rush)
reply