I love Typst for text and equations, but I find that it is taking me time to adapt to their table syntax and be able to make tables similar to booktabs. I'm hoping that Estout or Modelsummary will be able to write Typst tables with complex formatting soon.
Upright antennas will yield higher coverage with less antenas.
Slanted antennas will limit the amount of non useful RF escaping upwards into airplanes' radomes but will have a range limited by the slanting + beamforming angles.
An analogy is having public lighting with the bulb focused horizontally versus focused downwards. If it is facing horizontally the light will illuminate farther but a fraction of the light will be light pollution pointed at the night sky. If the light is facing downwards it will be limited by the aperture of the lamp post holder.
While all reasonable points, his resume doesn't actually list any experience in industry. There is certainly a lot of data analysis skills that can be learned while at academic institutions.
I would argue, however, that a skill that is often not put on these lists of 'what you need to become a data scientist' is some time being at a real private sector company. In my experience, there are quite a few differences between writing academic papers and coming up with the terse, actionable information that is useful for a profit-driven company.
about this, I use brackets, a lot of it does look like brackets maybe with some ideas taken from light table http://www.lighttable.com/
There's a thread on discuss.atom.io about what distinguishes the two http://discuss.atom.io/t/what-distinguishes-atom-io-from-bra...
I guess I don't feel atom does enough different from brackets that I can justify switching editor at this point, but if anyone has more to add than was found there I'm interested to hear.
