Comment by menaerus

4 hours ago

You largely explained a day in life of a SWE working in a complex codebase spanning (tens of) millions lines of code. In complex products we always deal with a great degree of uncertainty and due to the ambiguity and high complexity we usually have no simple way of proving that the thing (TM) we designed is going to be working as advertised in all cases. Because the problem space is in-exhaustive, and to increase the likeliness of the solution we designed, we run the experiments, and not on a sole machine but clusters at data-center scale. Even then you get "bug reports" and that's not because engineers were lazy but because the domain is genuinely complicated, and ever changing.

So, I'd say it's a pretty similar process, and yet we have the AI models now almost completely integrated into the SWE domain remediating significant parts of its complexity.

5 comments

menaerus

Reply
throwaway132448  3 hours ago

What is it with SWEs thinking every problem can be addressed in terms of SWE, while at the same time being unaware of how little they understand the problem they are trying to address?

  • menaerus  1 hour ago

    I made a parallel with similar complexity and ambiguity that can be found in SWE discipline too. I tried not to make any hard claims but I did present my opinion on the topic - I don't see a reason why drug discovery field wouldn't benefit from the AI when there're proportionally difficult fields (math, comp.sci, mechanics, medicine) where AI is already making a significant difference. Maybe you think comp biology is of a very different kind in which case you would turn out as ignorant here. lastly, my comment is there to spark the discussion and have some food for thought because not so long ago this type of reaction has been seen in comp.sci circles and math just few days ago.