mortalapeman

7 ms·

1.
by mortalapeman 17d ago
My company recently had to cut back our usage to effectively nothing and I get to code by hand again. I'm going to appreciate it while I can. The AI just wasn't providing enough value for us
2.
by mortalapeman 17d ago
Where it really shines for me is when the best solution is explicit and obvious code, but really tedious to write. Now I'll choose to have AI write it instead of me, where before I might have tried to write a bad abstraction. Things li
3.
by mortalapeman 17d ago
As someone who has made a career by having unique insights into solutions for software problems, I can confidently says it's not the same as the calculator. AI is bad at gathering context from an in-person customer meeting, linking the
4.
by mortalapeman 1mo ago
With generated code, the directory structure, interface design and general state management is usually a haphazard mess. Even with the best frontier models. But what really gets me is the model often tries to make assumptions for me that I
5.
by mortalapeman 1mo ago
This has been my experience as well. The best model I have access to right now is Opus 4.8. It's really good at fixing bugs in an established architecture or adding a similar feature, but it's absolutely mid tier at putting togeth
6.
by mortalapeman 2mo ago
That's funny, I found the article to align exactly with my own personal experience of working with LLMs in cobdebases with poor test coverage, uncertain requirements and non standard production deployments. As soon as you are off the h
7.
by mortalapeman 5mo ago
As a senior dev who has been using these tools to their fullest effectiveness in production environments, until AI can reduce the entropy of a codebase while still adding capability I will continue to be underwhelmed.
8.
by mortalapeman 13y ago
I partially agree, directives are not easy to learn, and there is not enough good documentation or literature on how to write them well. However, I have found the api to be very expressive , concise, and flexible once mastered. I can't
9.
by mortalapeman 13y ago
The only reason one would use scope.$watch in this fashion is to have a function executed when a digest occurs. The original purpose of the $watch function is to take 2 functions, one that returns the watched value and another to be execute
10.
by mortalapeman 13y ago
A single element cannot have more than once isolated scope. It only makes sense to use an isolated scope when a directive has a template associated with it. Otherwise, one should rely on the $parse + the "attrs" object + $scope.$w
11.
by mortalapeman 13y ago
Directives are a DSL for creating new behavior using HTML. Once you learn the language, the symbols make sense and directives are easy to read. I think you are confusing "intuitive" with "familiar". Since you are not fam