UK-AL

8 ms·

61.
by UK-AL 3y ago
CI/CD is making sure your code is always in a production ready state and validating with tests and other tools automatically.
62.
by UK-AL 3y ago
I've worked at many software companies, and the idea that a engineering manager can do a system design is hilarious. Most come from non technical backgrounds, or we're in a technical role for a short time.
63.
by UK-AL 3y ago
Seems like a very paternalistic style of management.
64.
by UK-AL 3y ago
The majority of new .net apps are linux in my experience. Because they all run in containers. Containers are best supported in linux.
65.
by UK-AL 3y ago
It's useful, but i find most design doesn't tend to be driven by the engineers themselves. So you end up design focus on things that don't matter, and things that do get skipped over.
66.
by UK-AL 4y ago
You'd probably separate example tests and validation tests. Also test descriptions should fed into the prompt to help guide it, like BDD style tests. On test failure, the data is fed back into the prompt about what failed for another i
67.
by UK-AL 4y ago
You can write tests about properties you care about which may not be everything. Generally in some of the more financial applications i've written I would be ok with people rewriting the app as long as it passes the tests. I've ev
68.
by UK-AL 4y ago
I think they've done it backwards in regards to it writing tests. Tests are the check to make sure the A.I is in check. If A.I is writing tests, you have to double check the tests. You should write tests, then the A.I writes the code.
69.
by UK-AL 4y ago
You shouldn't perform work that is unneeded. It's a problem for politicians on how people should earn living after that.
70.
by UK-AL 4y ago
What gets me is that it's really a software thing. You can get rocm working on RDNA 2 consumer cards. It's just a pain, only works linux and when you set it up on linux it's fiddly and can't just use the built in amd stu
71.
by UK-AL 4y ago
Eh? systemd unit files are tiny compared to the huge massive scripts that came before it. Often those scripts we're only understood by a few people as well. I think this why a lot of people really hate systemd. Suddenly a bunch of arca
72.
by UK-AL 4y ago
You can't approve a fact.
73.
by UK-AL 4y ago
I have. A lot.
74.
by UK-AL 4y ago
DDD is about behaviour rather than just data. In fact many business domains don't map in relational very well.
75.
by UK-AL 4y ago
I find that problem kind of rare these days. Everybody knows about it.
76.
by UK-AL 4y ago
It means you're mostly compute limited. Which i find is rare in web api's.
77.
by UK-AL 4y ago
I find BigO performance is very rarely the cause of bad performance. It's normally slow IO, timeouts, deadlocks etc I think I've actually seen performance decreases by people trying to decrease BigO. BigO only starts to really dom
78.
by UK-AL 4y ago
There's the intent behind it. Some systems expect you to do get right first time, but often doesn't. Others expect it to be wrong first time.
79.
by UK-AL 4y ago
I've worked on very complicated systems(Mathematical simulations etc), you can always break it down to sub problems.
80.
by UK-AL 4y ago
There's 3 approaches. Deadline & No Fixed Scope. Fixed Scope & No Deadline. Deadline & Fixed scope and padding appropriate to uncertainty to hedge risks. All 3 are admissions you can't estimate accurately.
81.
by UK-AL 4y ago
This is what agile actually wants you to do. You can have a deadline but no fixed scope, this what CI/CD is for. So when deadline day happens what you have is already released. Or you can have fixed scope but no deadline. Or you can h
82.
by UK-AL 4y ago
Tbh if entire tasks are taking 3 weeks you have problems.
83.
by UK-AL 4y ago
Deadlines are real, but estimates are very inaccurate. The best you can do prioritise the important features. Then what gets released is what you have at the time. If you want to plan for real hard deadline with a fixed scope, you need to b
84.
by UK-AL 4y ago
Real hard deadlines aren't that common in real life except in a subset of industries. What people want estimates for is budget reasons. They want to lock down both scope and time. So if you want to start removing edge cases and details
85.
by UK-AL 4y ago
That's a good thing, TDD is a prompt to say you don't really understand this requirement. Requirements aren't a design. TDD makes you define what your input is, and what your output is. What's in the middle your free to
86.
by UK-AL 4y ago
Quite frankly very few people can do TDD well. Hence why most developers hate it. They've never been taught by a master. The majority of developers have less than 5 years experience, and they're teaching new devs. So the skills th
87.
by UK-AL 4y ago
It adds a lot of effort.
88.
by UK-AL 4y ago
I assume they are used more in manufacturing and factories? That's the environment kaizen was born in, to optimise production lines.
89.
by UK-AL 4y ago
Isn't this just the entry exam to be educated. Not the final exam?
90.
by UK-AL 4y ago
Love this. Fully understandable why he would snap.

More ›