We are mostly (95%) a PHP company but going by trends; we did some projects in Python, NodeJS and Rails a few years ago.
Now I look back; I see the projects which have technical debt were flawed in design and did not get maintenance they needed. Most of them did not get traction to the point where scalability issue came into the picture.
So this year, we started moving that 5 % non-PHP projects to PHP counterparts. Again, we are miles away from any real-world scalability issue, but at least we are now able to maintain projects as we have a large PHP team.
At a small to mid-size organization level, it is more important to use one language for all projects.
I believe technical debt is not related to the choice of language but anticipating direction a project might take and picking up right design patterns to support that.
Which programming language is better is a highly overrated question!
I am wondering how much extra time it will take for 3D printing as we add support for 10 minute time interval, 1 minute interval and then seconds (extra set of digits HH:MM:SS).
Also will it be practically possible to have second-level granularity?
The width of the Sun in the sky is wide enough that it takes about 1 minute and ten seconds to cross its own diameter. So optically speaking, it would be pretty much impossible to have any resolution finer than a minute, no matter how small the holes are.
I cannot see how to do it, but one way to beat that limit might be the use of diffraction gratings. It might be possible to have the light from two opposing edges of the solar disk interfere and produce a darker spot, thus allowing one to draw the time in darker text on a light background.
If that can work, I guess both the design (I can't see how to design one object that shows a number for say 5 seconds; now fit thousands in a single object) and the engineering challenge would be quite a bit higher (at submicrometer scales), and that the resulting contrast of the display would be a lot lower.
I think it should still be possible, but it will depend a lot on the length of the holes too.
If you imagine a really long tube, any light entering at an angle will eventually hit the side, and if the sides do not reflect any light, nothing will come through the tube.
I don't want to bother doing the math to figure out how big the diameter of the sundial would have to be to have sub-minute accuracy, but I think it is very possible.
skykooler's point is that the Sun is not a point source. I think you may be mentally modeling it as a point source. A point source would make it just a matter of length, but when it's not a point source you can't help but get overlap between two "points" that are close enough together, because they both will be lit up at the same time, no matter how long the tube may be.
Perhaps a nighttime version intended to work with starlight would work. It could be aimed at Polaris and combine the light from all the stars swirling around it to project the digits.
I wonder of you could do some kind of mechanism so that when the leading edge of the sun turns on a pixel, that also warms up something causing expansion which is used to block an earlier pixel that is still on and you want to turn off?
The change in the direction of light per second will be way too little to create a digital sun dial of this style. It would need some sensors to detect it which kind of defeats the purpose again. It's not a shortcoming of 3D printing but of optics/physics
Consider the size of the sun: it's not a point source. Even if it was, the "seeing" (astronomical term for sharpness of objects in the sky) is usually on the order of arcseconds at night, probably much more (due to convection) during the day. So even with image-forming optics, 1 sec temporal resolution is very tricky. (earth turns 15 arcseconds in one second)
You'll only get diffraction when the slits are comparable to the wavelength of the light, i.e., on the order of a micron. I believe you can see light peeking out through a micron slit if you're looking directly at it in a dark room, but I don't think it's feasible to see diffraction in shadows. The fuzziness you see in normal shadows comes from the finite angular size of the light source, not the wave nature of light.
In most places 24 hours wouldn't be possible, because even if you were somewhere with 24 hour sunlight, for part of the day the shadow would not be cast on the earth. You need to angle the sundial so that it's perpendicular to the sun's path through the sky, so for at least a portion of the cycle the sun would be 'below' the sundial, casting a shadow upwards. I suppose if you were very close to a pole near the summer solstice it could work though.
I happened to see this on twitter before here and was wondering why I was already following this account..... It wasn't a retweet. I hadn't really used twitter much today and definitely didn't follow it today.
Now I look back; I see the projects which have technical debt were flawed in design and did not get maintenance they needed. Most of them did not get traction to the point where scalability issue came into the picture.
So this year, we started moving that 5 % non-PHP projects to PHP counterparts. Again, we are miles away from any real-world scalability issue, but at least we are now able to maintain projects as we have a large PHP team.
At a small to mid-size organization level, it is more important to use one language for all projects.
I believe technical debt is not related to the choice of language but anticipating direction a project might take and picking up right design patterns to support that.
Which programming language is better is a highly overrated question!
I wish I had learned this few year ago.