14-Month School Year Calendar Template: Fill & Download for Free

Work on something you have never worked onThe company's culture that dates back to '09 - taking major pivots like finance portal to community forum to mobile Customer Relationship Management (CRM) company with no background in mobile whatsoever. Which means everyone who joins us is consciously put into situations where they have never worked on. All the time! This keeps everyone extremely busy, the appetite hungry, and result innovative. We like folks who treat it like a rodeo. Have the attitude that you want to mount it (learn new things & processes), and you won't fall off.Smart people; capable of building anythingWhere to spend time building what - is the only limitation. As a result we're always excited about what we're going to be doing next. We have also had hackathons introducing several directions/features.Opinionated product designThe CEO sets the vision for a product/quarter; product managers break it down, spec it out & product designers bring it to life; we try and reduce ambiguities to zero between the day we start working on it until finishing.Consensus over MeritocracyAnyone can discuss or bring up any point/argument. We thrash things out, but try to reach a decision among the group before leaving a meeting. After a decision is arrived upon - it becomes everyone's foresight/fault. We're all in this together and everyone's invited to contribute.New engineers should be able to get the entire product running locally in < 3 hoursCourtesy Vagrant (software), Ansible, DevOps love (we've reduced this and still pushing). Our solution to managing Database Schema & migrations across time/teams works for us quite as well.Hire for potential; not fitWe genuinely like to help candidates & can empathize with folks new to a programming language. Most people we hire have never worked with Clojure (programming language). We fire fast in cases where it's not working out at all. Hiring is as much about convincing you how much more we as a company can grow; as it is about we expecting you to grow. This is opposed to folks who are perfect for a role. you're not going to be working in familiar work even if you have. We will push you out of your comfort zone as mentioned in (1). We want your best work yet, to be every last quarter with us.A flat engineering team (that pays well)We're a flat organisation. If you earn the respect of your peers - you will attract what you emit. Everyone starts off a beginner (coincidence - that's what our CEO still calls himself to this day). We pay extremely well. But we've de-coupled pay-scale with your work. Our open office space also helps. Our last hire managed to grab an empty seat right behind the CTO (we've just moved to a nice big office, but started looking at expanding it already)An interesting hiring processA long Q&A questionnaire to be replied over email. Small Fizzbuzz like problem. A bigger take home task that involves creating a devspec, mostly followed up with implementing the dev-spec. A phone interview and finally interviews with 3-4 engineers who could be your team mates. Meet with a PM. Meet the CTO/CEO.Spend the first month getting mentored by the CTOWhere you're trained/onboarded to Clojure, Emacs, and possibly some research about the work you may be expected to work on. Except for interns - you can pretty much open up the source for any project/repo.Encourage the creation of repositories/micro-services/servicesWe have 100's of them, across several languages - mostly Clojure - but also include Go (programming language), Erlang (programming language) and of course web & mobile languages as wellSpend the next week creating a repository/service/library/jar others useYou own that service/repo. Every service/repo needs to get 2 other contributors who peer review. This way a 2 year old repo by our earliest dev; and your's have pretty much gone through the same process, and freedom. Naming of repo's are always fun.Time spent on specs (before code) is time well spentEven someone who is expected to implement and write code, usually spends a week or two prior just writing their thoughts, flow of action before writing a line of code. This also happens after they're done with code - when talking to ops - regarding benchmarking, infra requirements, etc. Making templates on Jira that anyone can use have helped immensely.Developers write unit-testsAlmost every commit has tests that accompany them. Except for maybe strongly typed languages like go on which some our services are built. Our Ops team constantly works on life savers like parallel Jenkins testing, isolated db's & env's for every run, and now moving towards providing staging and benchmarking env's on demand.QA are developers tooOur QA developers review code and write amazing code. They face nice problems about how to automate data generation, mocking, creating sand boxes and integration testing. a lot of these are open source. a lot of automation. At Helpshift you won't be surprised to find QA file bugs and then fix them themselves. That's the kind of competence and culture we've come to expect.Kafka is your glue between teams, services, pipelinesWe absolutely swear by Apache Kafka at Helpshift. Both simple and complex feature/pipelines make heavy use of the distributed message queue which makes how we push/consume from it immaterial to an extent, also making testing easier, allowing teams to work in parallel and problem set broken down to more manageable tasks.Lambda computing encouraged, but open to anythingWe're seeing more teams accept stream processing, append-only and incremental consumption of data. But that doesn't stop our data platform team optimizing searches on terabytes of data. You get to decide how to build stuff - and it's up to you to build consensus through strong reasoning via data/specs/benchmarking to back them up.Code reviews are your best teacherAll code is peer reviewed, and most repos have bots to reply with test results. A recent hire added code styling comments injection. Very cool. it's never too early to invest in a code-review system. It's not un-common to see 10+ patchsets while you're learning. And that's ok. An environment that accepts you not knowing/learning is a great motivator.We use Gerrit. Most of us use Emacs, tmux & plenty of internal toolswe also love JIRA, Confluence (Atlassian), Slack (product).Rigour for predictable handoff between teams & releasesThanks to a ops team that's created some amazing workflows - there are hardly any surprises when it comes to shipping. We ship twice a week apart from hot-fixes, etc this allows everyone to plan their week & work-life balance. Because of our product led flow - we spend time getting started - but once we do - we have product hand-off's , design hand-off's , developer hand-off's, qa sign-off's , op's sign-offs, and then releases. Many folks who have joined us from larger companies find life much less stressful, more rigorous but as a result more predictable & less pain in the long-term. After the first few months - this will come naturally and is a pleasure seeing teams running like well oiled machines between sprints and releases.Contribute to & support open-sourceHas several active github contributions and repo's. While it's a given that startups embrace open-source technologies; our ops team is not afraid to host private maven & debian repositories, and prefer hosting/managing our own infrastructure deployments where we can. They can easily re-deploy practically the whole infra in Amazon EC2 or Microsoft Azure or ... - recreating prod infra in a few steps. We love our Devops team. And they love automation. Their philosophy could be another essay altogether.Good Work-life balanceOfficial timings are 9 to 5.30. Cabs to pick up and drop you. 5 day week.From a macro/long-term perspective - given the team size we typically ship multiple startup worth of work multiple times a year. Our teams are moving from 2-week sprints to weekly. Most of these are just engineers sitting and talking about our problems, progress & a great way to keep everyone in the loop.Great place to workAmazing open spaced office with an industrial finish.Breakfast. Lunch. Everyone's always bringing home cooked snacks or goodies from abroad or donuts or ice-cream or whatever our chief happiness officer has an appetite for that evening. Bunker beds. A gym. TT, games. Twice a week futsal on synthetic astro turfs under lights. Conference & travel allowances. We host developer meetups on most saturday mornings & help organize/sponsor several large events/meetups across the country/world. Standing desks. We measure & can configure the intensity of light to your desk. Sofa's. A mini library. A massage chair (we had a massuer come couple of times a week - but not too many used his services) . Grab a meeting room when you want them (it's all scheduled on a calendar to avoid conflicts). Expensive chairs. Macs. Accessories. Toys.Diverse teamWe have school dropouts (including one from Nepal!); guitar playing assembly line turned release engineering folks; an Australian automation engineer whose visited more of India than I have; several CS language & functional programming geeks; Mythology, Astronomy & Mathematics nerds, minimalism seeking designers (or not!); hustlers; gamblers; Hackers and Painters. No pun intended.Business updates - Frequent & TransparentSince we're growing our teams in both San Francisco & Pune, Maharashtra, India - our CEO (or our CPO if he's in the US) shares business updates at least once a month on a Friday where we have an open house style gathering at "the wall". He treats us all like potential entrepreneurs here - having learnt a lot from his early days with big names as well as his biggest teachers - customers. a lot of inside info; Employee Stock Ownership Plans, sales & funding updates, lot of anecdotes and stories from the valley, and early days of Helpshift's past avatars all the way back to '09. celebrating small wins & big. Introducing new employees. Vision. Focus. Execute.A.B.I (Always be Improving)Lot of these have gradual changes evolved over several years. I can't wait to see where we are a year from now!Scale & ChallengesUn-precedented. Let's put it this way. We're building a team & stack that can handle the impact of our SDK on billions of phones. Think of what happens when an update launches to several of the top apps across most categories. Flipboard, Supercell (company), Microsoft (company), Zynga (company), WordPress, and hundreds of other largest apps & most of the newest trending apps in any given week. we power the help & support experience in these apps, but need to be able to take the load of all these apps. Combined. At the same time. We take that responsibility seriously. eg: as we grew from 6k reqs/sec to 20k reqs/sec - our latencies actually went down 1/3 rd. That said we have a backlog of 100's of exciting things to do. we just need smart & driven engineers, designers & product managers to lead the way.OpportunityOnce in a life-time. we're riding on three big waves.Come find out :)

Babylonian mathematics - WikipediaInfluence[edit]This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.(October 2017)(Learn how and when to remove this template message)Since the rediscovery of the Babylonian civilization, it has become apparent that Greek and Hellenistic mathematicians and astronomers, and in particular Hipparchus, borrowed greatly from the Babylonians.Franz Xaver Kugler demonstrated in his book Die Babylonische Mondrechnung ("The Babylonian lunar computation", Freiburg im Breisgau, 1900) the following: Ptolemy had stated in his Almagest IV.2 that Hipparchus improved the values for the Moon's periods known to him from "even more ancient astronomers" by comparing eclipse observations made earlier by "the Chaldeans", and by himself. However, Kugler found that the periods that Ptolemy attributes to Hipparchus had already been used in Babylonian ephemerides, specifically the collection of texts nowadays called "System B" (sometimes attributed to Kidinnu). Apparently, Hipparchus only confirmed the validity of the periods he learned from the Chaldeans by his newer observations.It is clear that Hipparchus (and Ptolemy after him) had an essentially complete list of eclipse observations covering many centuries. Most likely these had been compiled from the "diary" tablets: these are clay tablets recording all relevant observations that the Chaldeans routinely made. Preserved examples date from 652 BC to AD 130, but probably the records went back as far as the reign of the Babylonian king Nabonassar: Ptolemy starts his chronology with the first day in the Egyptian calendar of the first year of Nabonassar, i.e., 26 February 747 BC.This raw material by itself must have been hard to use, and no doubt the Chaldeans themselves compiled extracts of e.g., all observed eclipses (some tablets with a list of all eclipses in a period of time covering a saros have been found). This allowed them to recognise periodic recurrences of events. Among others they used in System B (cf. Almagest IV.2):223 synodic months = 239 returns in anomaly (anomalistic month) = 242 returns in latitude (draconic month). This is now known as the saros period, which is useful for predicting eclipses.251 (synodic) months = 269 returns in anomaly5458 (synodic) months = 5923 returns in latitude1 synodic month = 29;31,50,08,20 days[14] (sexagesimal; 29.53059413... days in decimals = 29 days 12 hours 44 min 3⅓ s, P.S. real time is 2.9 s, so 0.43 seconds off)The Babylonians expressed all periods in synodic months, probably because they used a lunisolar calendar. Various relations with yearly phenomena led to different values for the length of the year.Similarly, various relations between the periods of the planets were known. The relations that Ptolemy attributes to Hipparchus in Almagest IX.3 had all already been used in predictions found on Babylonian clay tablets.All this knowledge was transferred to the Greeks probably shortly after the conquest by Alexander the Great (331 BC). According to the late classical philosopher Simplicius (early 6th century AD), Alexander ordered the translation of the historical astronomical records under supervision of his chronicler Callisthenes of Olynthus, who sent it to his uncle Aristotle. Although Simplicius is a very late source, his account may be reliable. He spent some time in exile at the Sassanid (Persian) court and may have accessed sources otherwise lost in the West. It is striking that he mentions the title tèresis (Greek: guard), which is an odd name for a historical work, but is an adequate translation of the Babylonian title MassArt meaning guarding, but also observing. Anyway, Aristotle's pupil Callippus of Cyzicus introduced his 76-year cycle, which improved on the 19-year Metonic cycle, about that time. He had the first year of his first cycle start at the summer solstice of 28 June 330 BC (Proleptic Julian calendar date), but later he seems to have counted lunar months from the first month after Alexander's decisive battle at Gaugamela in fall 331 BC. So Callippus may have obtained his data from Babylonian sources and his calendar may have been anticipated by Kidinnu. Also it is known that the Babylonian priest known as Berossus wrote around 281 BC a book in Greek on the (rather mythological) history of Babylonia, the Babyloniaca, for the new ruler Antiochus I; it is said that later he founded a school of astrology on the Greek island of Kos. Another candidate for teaching the Greeks about Babylonian astronomy/astrology was Sudines who was at the court of Attalus I Soter late in the 3rd century BC.In any case, the translation of the astronomical records required profound knowledge of the cuneiform script, the language, and the procedures, so it seems likely that it was done by some unidentified Chaldeans. Now, the Babylonians dated their observations in their lunisolar calendar, in which months and years have varying lengths (29 or 30 days; 12 or 13 months respectively). At the time they did not use a regular calendar (such as based on the Metonic cycle like they did later) but started a new month based on observations of the New Moon. This made it very tedious to compute the time interval between events.What Hipparchus may have done is transform these records to the Egyptian calendar, which uses a fixed year of always 365 days (consisting of 12 months of 30 days and 5 extra days): this makes computing time intervals much easier. Ptolemy dated all observations in this calendar. He also writes that "All that he (=Hipparchus) did was to make a compilation of the planetary observations arranged in a more useful way" (Almagest IX.2). Pliny states (Naturalis Historia II.IX(53)) on eclipse predictions: "After their time (=Thales) the courses of both stars (=Sun and Moon) for 600 years were prophesied by Hipparchus, …". This seems to imply that Hipparchus predicted eclipses for a period of 600 years, but considering the enormous amount of computation required, this is very unlikely. Rather, Hipparchus would have made a list of all eclipses from Nabonasser's time to his own.Other traces of Babylonian practice in Hipparchus' work are:first known Greek use of the division the circle in 360 degrees of 60 arc minutes.first consistent use of the sexagesimal number system.the use of the unit pechus ("cubit") of about 2° or 2½°.use of a short period of 248 days = 9 anomalistic months.

BambamBambam is a great tool for small companies, school administrators, freelancers, and development teams. Free for up to ten people, this software includes a task feature that can be optimized for Agile notation. Freelancers and project managers particularly like this cloud software for its time-tracking features and permissions settings.Pros: Optimized for Agile, free for up to ten users, and unlimited projects and disk space regardless of the plan.Cons: Difficult to customize, lacks notable project management features, like Gantt charts and QA management, is not mobile, and is difficult to scale to larger companies.Price: Free for up to 10 users or educators. BamBam! offers 15 users and 14 days of trial for a starting cost of $70 a month.hiTaskEven though hiTask bills itself as “team task management,” its free personal task management software is among the best. This software is nice because it offers plenty of features—calendar, grouping, tasks, and subtasks, to name a few—yet is able to organize all of it onto one screen, so you don’t need to jump around different folders looking for your next to-do.Pros: Readily-available API for customization, free to use, great for people invested in Getting Things Done.Cons: Free users are limited to 10 projects and 100MB of storagePrice: Free; $4.17 a month for users who want unlimited projects and 1GB of storageMeisterTaskMeisterTask is a reflection of the operating system it caters to – Apple. And like Apple, it focuses on simplicity, aesthetic, and function. While these three ideals are certainly difficult to achieve, MeisterTask comes very close. This kanban task management software is so simple that you can open it up and be working within your first minute of use. The free version includes two free integrations, like with Drive, Slack, GitHub, or Zendesk.Pros: Lots of great integrations, intuitive, standout iOS app.Cons: No mobile version for Android (yet) and gives preference to developing for Apple.Price: Free for up to two integrations; $9 per user per month for more reporting and integrations features.PintaskIf you want an alternative to the popular free task management software option Trello (reviewed below), check out Pintask. The software offers users the ability to track due dates, attachments, and reminders so everything is done on time and on budget. The kanban-based software is wholly customizable through add-on extensions, allowing users to build their own perfect, low-cost task manager.Pros: Intuitive, easy to create your own extensions for, and great for team collaboration.Cons: Users must buy extensions that are otherwise free on other apps, like card mirroring.Price: Free plus the cost of extensions (starts at $3 a month)ProducteevNamed the #1 free project management software, Producteev offers a gamut of powerful project management tools. Users can create unlimited tasks and subtasks, attach files to tasks, and turn emails into tasks by just forwarding them along. All tasks can easily be labeled, assigned, arranged by priority, and made to be a recurrent event. Producteev is also a collaborative software, so all users can comment on others’ task feeds.Pros: All tasks can be filtered by a host of variables like status and due date, has DropBox integration, offers a mobile app, and has strong collaboration tools.Cons: Offers no time-tracking options.Price: Free for unlimited users, unlimited projects, and unlimited tasks. Businesses looking for Outlook integration, personalized support, and color and logo customization can upgrade for $99 a month.TaskworldIf you’re struggling to choose between kanban and task lists, choose Taskworld; this free to-do list software offers both! Built with the team in mind, Taskworld offers lots of options to keep files organized with assigned tasks, a robust commenting system, and custom workflows so everything stays together. Whether you’re using this software for yourself or for a team of up to five, you’ll have everything organized and ready to go.Pros: Could act as a free lightweight project management software option, excellent free features for up to five users, and allows users to easily create repeated tasks.Cons: No integrations available, users may feel overwhelmed with options meant for teams instead of for single use.Price: Free for up to five users; $11 per user/month/workspace thereafterTodo CloudThe above-mentioned apps do a whole lot—but some people just want a to-do list, with not a whole lot of bells and whistles attached. Todo Cloud offers exactly that.Create your tasks, order it by label, set a date, and go. Tasks can also be broken down into multi-level priorities, starred, and (my personal favorite feature) “focus,” or tasks that must be completed that day. This online task manager can be used for teams as well. Users can comment on, share, and sync their to-do lists, keeping everyone on task.Pros: Simple to pick up and use, cross platform (iOS, Android, Mac, and PC), well-priced, and unique tools like geotagging.Cons: Requires Internet access and mobile apps are only available in the paid version.Price: Most users can get away with Todo Cloud’s free version. For those looking for mobile and email integration, Todo Cloud costs $1.99 a month, or $19.99 a year.TodoistTodoist is a trusted standard in task management software. It offers a synchronized system that is available over iOS, Android, Windows, Mac, PC, and most major browsers. The interface is intuitive and set up similar to Gmail’s—on the left, there are categories (for example: due today, the next seven days, or “projects”), and on the right, there are the tasks themselves, which can be broken down into subtasks, sent out for collaboration, and can be filtered by their corresponding labels. And Todoist adds a small bit of gamification to its system, encouraging its users to earn “Todoist Karma” to track their productivity trends as they get their work done.Pros: Very simple design, offers a mobile app, and lots of cool task-based features, like Todoist Karma, that aren’t available elsewhere.Cons: The free version is limited in its capabilities and is not well-encrypted. Some of the mobile apps have design issues (like being unable to sort tasks).Price: Todoist is free for projects and tasks. For additional features, like reminders, filters, labels, and templates, users must pay $29 a year.TrelloTrello is another powerful task management software that made the list of top free project management software. It relies on the Kanban system of project management for users to visually organize their tasks. Use Trello to divide projects up by tasks, and then edit those tasks with descriptions, labels, checklists, and even attachments. Trello is particularly helpful for teams working on separate tasks toward a greater project goal, where the tasks are in need of a pipeline.Pros: Intuitive layout and design, great for collaborative projects, and most companies and individuals are satisfied with the free version.Cons: There is no good way to use this system to prioritize tasks between projects.Price: Free for unlimited projects and users. Users may choose to purchase Trello Gold to up their card attachments to 250MB. Businesses may opt for Trello Business Class, which costs $8.33 per user per month, paid out annually.WrikeWant a drag-and-drop task management system that’s great both for individual use and for group projects? Create and manage tasks based on due date and urgency with this tool. Users can use Wrike’s “Spreadsheet View” to mass-edit tasks and, with Wrike’s intuitive collaboration system, can share discussions and files that attach straight to tasks. Wrike also syncs with Google Drive, Dropbox, Box, and iCal, so users can keep all their projects and tasks aligned with their respective files.Pros: Wrike offers a host of features and is, overall, a powerful project management product. Outstanding customer service, always new features, and makes collaboration easy.Cons: The free version is substantially less full-featured than the paid option.Price: Free for up to five users. Professional plans come with many more features and run $49 per month for up to five users and $99 per month for 15 users.More?There are many other powerful task management software solutions availableSource : http://blog.capterra.com/