1,281 karma · joined August 26, 2018
The resulting diagram shows no relationship arrows.
Turns out the Fossil's schema uses REFERENCES clause with a table name only; I guess, this points to table's primary key by default. Apparently, the diagram generator requires explicit column names.
Does work with sqlite3 v3.40 and likely higher too.
Do you generally experience slow physiological and neural reactions? In other words is it a 'hardware' limitation?
My guess, in your case it may be more about specific contexts. Some topics/domains may not be your forte, so to speak, yet you could be familiar with them enough to get engaged.
So a reasonable choice could be not to engage into debates, instead take a role of a talk show host which encourages guests to talk and tell. It's a win-win case, the other side shines, you learn about the person and the topic.
Eventually you'd know which topics are "yours". It's not possible to know everything, yet it's very much possible to listen to anything (unless it's a preschooler asking for ice-cream non-stop).
Also, exercising your memory may be of great help in life in general. Fast recall saves you more time for processing the information.
Yes, if talking about the Fourier transform. My understanding was that author proposed that "trick" in context of discrete series for bounded non-periodic functions x(t), y(t).
Instead, what followed was more like an extension to periodic function.
Wouldn't this effectively make frequency 0?
Later on for the drawings you pick period T to be equal to 1, thus frequency to be 2*pi. This does make more sense both practically and mathematically too.
P.S. A small nit, a typo "f_t and y_t" should rather be "f_x and f_y". Very fun read, thanks!
So, naturally, as one progresses in the field, the level of complexity often increases with experience. Sure, some tasks become easier, but those are getting assigned to 'juniors' or just are no longer interesting...
Here it is, more experience, yet still uphill with complexity. It does get tiring at some point.
Well, roughly this is equivalent to
92909**2 = 8632082281
Assuming 'pedes' is steps, 'untia', 'minuta', and 'secunda' are some dec divisions of a step, then the result notation has too many points to keep the meaning.
Looks like more of a reading/spacing convenience for a whole number with many digits. Not much about decimal point.
I find that "algorithmic thinking" is too artificial for young kids. They are very versatile in a richer set of methods, which often are mutually conflicting yet lead to desired result.
Once we played with a programmable mouse that needs to find cheese. Very predictably, the most used button was "do a trick", which makes mouse make funny noise without moving further... Sweet times for the kid, doomed moments for the teacher.
There are way too many dots in the text.
- DO WHILE and END DO statements
- INCLUDE statement"
- IMPLICIT NONE variant of the IMPLICIT statement
- Bit manipulation intrinsic functions,..." [1]
Modern Fortran is like both C and C++ in the same language.
That's remarkable persistence. Apparently this is the main/only product of the company. Good news for those who still use it.
Yet it's hard to validate a rationale for adopting a Fortran based GUI toolset for new projects.
Frozen Supercharger connector is not a clickbait. It's a reality of -9F over 3-day weekend.
At some stations snow drift would be up to the charger so that cable may accidentally fall into the snow when putting it back.
I can see how such connector would be then put upright and the moisture would end up in the mating holes.
Also, waiting in the line at the charger (some waits were over 1hr) would likely cool the battery, unless driver would manually keep the battery conditioning on, which eats the charge too!
Then it goes to slow charge due to cold battery. Which increases the wait time to the others in the line...
Dismissing these issues on personal experience does little to improving the infrastructure and charger design.
The Tesla connector latch issues in freezing temps are likely common as well.
Latch problems in freezing temps is not new. Some drivers even work around the frozen connectors by parking sideways (!) to the charger then bringing the connector indoors just to warm it up enough for the moisture to thaw out. Don't know how long this could take.
Perhaps, some heated receptacles on the charger or some antifreeze laced cradle could deal with that. Again, this is the reality of wider EV adoption, extension of field-test. So some adjustments are due.
How could a Supercharger freeze? I don't know all details, but some connectors would report as NO LATCH and Tesla would refuse to charge.
Apparently it's about some moisture freezing in the connector and preventing proper mating with the port. Literally, some ice in the 'needle' holes. Maybe some other issues.
I'm not sure if this is a design problem or maybe some improvements are due if this type to become standard.
Does it mean it's around your software product, or it's some sort of agency?
Is it a dreamland or such clause is really possible in the present day cookie-cutter contracts?
Then, when implementing a more 'remote' on-screen pointer, the notion of pointing perpendicularly at the site was best projected by a tilted 2D marker.
Think of the mouse pointer kinda sticking out of the screen as a dart.
I can't imagine the arm strain the users of the light pen had to endure back in time ... Though the workflow was probably still more keyboard-bound.
Well, it's an author's column. Very much reflective.
Sometimes both of these coincide. Lucky! Sometimes you grow into accepting 1) to become also 2). Well, lucky too! If you also have a choice to enjoy doing this in later years, then you are very much lucky and happy.
Otherwise, like lots of people, we keep on our pursuit of happiness. Retirement from a well-paying yet not that rewarding job, just gives us another chance to catch that happiness, perhaps now being able to detach the 1).
Living long and remaining active is no less lucky!
So the weekend coding is an example of the opposite - having control over the choices, owning your time and inspiration.
Well, some degree of OCD likely is another factor in the burnout and the weekend coding just manifests this OCD.
Managing the high degree of complexity while being constrained by time by itself has a huge toll in the burning out.
I think at this age kids just naturally want to have their footprint in the digital world. Games is just an obvious space.
On the same subject, when my 5yo came up with a very detailed comic story, all hand drawn in a span of two days, we just scanned the drawings and put them in a video sequence.
Sure, the grand vision was some real action, but seeing his work digitized and animated has served it's inspiratory purpose.
Also, it gave this 5yo some ammo in conversations with his peers who would brag about "creating their own game in Roblox".
Take sin(x), C math would give a different approx value for sin(x+2*pi) even though it should be the same. Well, if only pi was known exactly...
I did not look into the code, however such casts can be a reasonable way to implement polymorphism in C.
Of course, having some common type field would be more robust, instead of blindly casting whatever pointer comes at input.
For example, such type could be defined as first field in the 'base' structure. Thus the cast into, say, `int` should yield a valid/expected type value, which would be checked in the called functions before casting into the expected type.
It seems to be a proper media for 'printing' a video.
Of course, choosing challenges and finding solutions is what drives fun.
Ask it if is there life on Mars in that parallel reality