really work towards them. But this also holds on a smaller
scale. When, during coding you encounter a problem, it's often easy to
solve just that problem. However, after stacking a few small solutions on top of each
-other, things get complicated real fast. Then, it helps to take a step back and
+other, things get complicated real fast. It helps to take a step back and
try to find the bigger problem you are trying to solve, and evaluate
subsolutions in that perspective.
quickly apparent that trying to design the hardware in an optimal way, was
completely impossible (when trying to stay within area and power constraints).
The most important issue here is finding the balance between two sides
-of a tradeoff, which was quite often hardware vs compiler complexity. Especially
+of a tradeoff, which was quite often hardware versus compiler complexity. Especially
this last issue makes it very clear that when designing hardware, the supporting
tooling should be designed in parallel, to prevent the tooling from needing to
be overly complex.
suitable, but this is mostly solvable and should be less of an issue once the
new hardware is finished.
-All in all, I feel that this internship has worked out quite well. The people
-were cooperating, the job was fun yet challenging and the result is
-well-received.
+All in all, I feel that this internship has worked out quite well.
+Cooperation with other employees was pleasant, the job was fun yet
+challenging and the result is well-received.
projects / matthijs / projects / internship.git / blobdiff