I understand why you have these feelings. I ended up in a similar place for awhile after a traumatic event. The desire to be sure it’s not going to happen again is incredibly strong.
The thing is, there is no way to know for sure that you are healthy. Any of us could keel over and die from some previously unknown or suddenly occurring problem at any moment.
You’ve already done your due diligence by checking to be reasonably sure you do not have high blood pressure. Now, you just have to let it go. When it comes to stuff like this, 99.9% sure is the best you’re ever going to do. Accept the uncertainty. It would be a real shame to waste part of the life you do have by constantly checking for something that doesn’t exist.
The best thing for your mental and physical health is to accept you are probably, albeit not certainly, just fine. If you cannot get over this yourself, I highly recommend cognitive behavioral therapy and medication as appropriate. Good luck!
The New York Public Library | Senior Mobile Engineer | NYC
The New York Public Library is reshaping the world of e-books and library lending with its SimplyE and Open eBooks mobile applications. These e-reading apps let people connect to their local libraries, check out e-books free of charge, and begin reading effortlessly.
Our small and dedicated team is looking for a mobile software engineer who shares our passion of improving public access to information. At the main NYPL branch near Bryant Park, you'll experience the pleasure of working full-time on open-source software, enjoy a healthy work-life balance, and be proud to know you're improving the lives of users around the country.
While we offer the opportunity to learn and develop for both Android and iOS, only knowledge of one platform is necessary when coming in:
– If you're an Android developer, you should have a strong command of Java and Gradle, be intimately familiar with Google's Material Design guidelines, and know your way around the usual SDKs. While our existing codebase is primarily written in Java, we make use of Kotlin for new development whenever possible.
– If you're an iOS developer, you'll need to be competent with both of Apple's languages: We're using Swift for all new development, but we have an existing codebase that makes heavy use of Objective-C too. You should also have experience with Apple's SDKs, be able to effortlessly apply Apple's human interface guidelines, and be comfortable doing library-based development via Carthage or CocoaPods.
In addition to one or both of the above, you should:
– have an interest in working with the open-source community,
– be willing to participate in a mutual code review process with your peers,
– understand how to build responsive user interfaces via concurrency, and
– be proficient with Git, GitHub, and related workflows.
Special consideration will be given to candidates with:
– knowledge of the EPUB format,
– experience building accessible applications, or
– a solid understanding of functional programming.
Send your résumé to nypldigitaljobs@nypl.org and let us know why you're eager to join our team!
The New York Public Library is reshaping the world of e-books and library lending with its SimplyE mobile and web applications. Our small, dedicated, and compassionate team is looking for an exceptional Android engineer to help us in the quest for ever greater public access to information. Join us in our efforts at the main NYPL branch location (of Ghostbusters fame) and you'll experience the pleasure of working full-time on open-source software, enjoy a healthy work-life balance, and sleep well at night knowing you're doing what's best for the patrons of the library, not someone else's bottom line.
Our native app is written primarily in Java with new development being undertaken in Kotlin. You should be competent with Git, know a thing or two about SQL, and understand the basics of JavaScript and DOM manipulation. Knowledge of the EPUB format, familiarity with building accessible apps, and a good understanding of functional programming are major plusses. We're also very passionate about our institutional values of collaboration and mentoring.
Ready to improve the experiences of library patrons around the US? Send your résumé to "nypldigitaljobs@nypl.org" and let us know!
I am not sure if you have ever been on the other side of this, but having people constantly assume you are a man because you know how to program and you're on the internet gets very old, very quickly. You can either accept being constantly referred to as a guy, which becomes flat-out alienating, or you can speak up for yourself, in which case you get responses like the one you just wrote.
I get that the gender of the author doesn't matter to you, and it may not even matter to the author of the article, but it does matter to a lot of people. No one is suggesting mistakes are a grave sin—even if her blog does say "Julia Evans" in giant letters right at the top. If someone makes one though, the correct response to people pointing it out is to accept the correction and keep it in mind for next time, not to accuse them of spam.
You're perfectly allowed to use "they" since you weren't sure.
It's not nice to assume "he" to always be the default - that is what was being corrected. One did not have to know that "she" was correct, but it was easy to find out that "he" was probably wrong. Let's keep discussion on topic, rather than venturing into talking about what you're "allowed" to do.
The New York Public Library is reshaping the world of e-books and library lending with its SimplyE and Open eBooks mobile and web applications. Our small, dedicated, and compassionate team is looking for an exceptional full-stack engineer to help us in the quest for ever greater public access to information. Join us in our efforts at the main NYPL branch location (of Ghostbusters fame) and you'll experience the pleasure of working full-time on open-source software, enjoy a healthy work-life balance, and sleep well at night knowing you're doing what's best for library patrons, not someone else's bottom line.
Our ideal candidate is a generalist with experience writing single-page applications who is eager to contribute across the stack. Our front-end makes use of TypeScript, React, and Redux. Our back-end employs a mixture of languages atop PostgreSQL, AWS, and a microservice architecture. In addition to command of the technologies mentioned (or similar SPA- and RDBMS-focused approaches), a working knowledge of Git, familiarity with the EPUB format, experience building accessible web applications, and a good understanding of functional programming are major plusses.
Ready to improve the experiences of library patrons around the US? Send your résumé to "nypldigitaljobs@nypl.org" and let us know!
The New York Public Library is reshaping the world of e-books and library lending with its SimplyE and Open eBooks mobile applications. Our small, dedicated, and compassionate team is looking for an exceptional mobile software engineer to help us in the quest for ever greater public access to information. Join us in our efforts at the main NYPL branch location (of Ghostbusters fame) and you'll experience the pleasure of working full-time on open-source software, enjoy a healthy work-life balance, and sleep well at night knowing you're doing what's best for library patrons, not someone else's bottom line.
Our native apps are written primarily in Objective-C and Java with new development being undertaken in Swift and Kotlin. We're looking for an Android or iOS expert who is eager to eventually contribute on both mobile platforms. You should be competent with Git, know a thing or two about SQL, and understand the basics of JavaScript and DOM manipulation. Knowledge of the EPUB format, familiarity with building accessible apps, and a good understanding of functional programming are major plusses.
Ready to improve the experiences of library patrons around the US? Send your résumé to "info@librarysimplified.org" and let us know!
> Inferring types of function parameters and results isn't as useful. Combined with generics, it gets really complicated.
I wonder why you think so? The inferred types in a language like Haskell or OCaml are almost always exactly what the programmer would have written. So long as a language has principle type inference, the worst case is that the inferred type is a bit more general than you expected.
> Also, whole-program type inference and separate compilation inherently conflict.
There is no conflict here, actually. All type variables in definitions exported from a module are generalizable. As such, no uses in other modules will further refine those types.
> I wonder why you think so? The inferred types in a language like Haskell or OCaml are almost always exactly what the programmer would have written
I have no experience with ML-using languages but in Scala, which has inferior but still useful type inference, it is recommended to add explicit types to public functions/methods because otherwise, implementation details or errors might alter the signature.
Take for example:
data Tree = Node Leaf Leaf | Leaf Integral
makeEmptyTree x => Leaf x
I assume `Leaf` will be inferred as a type, while the programmer might have meant `Tree` to be the public API. (or vice-versa)
This is largely to do with subtyping and it's well known that systems with user-defined nominal subtyping don't have good inference. Scala's inference is really in the middle: squarely better than C/Java and much worse than Haskell/OCaml.
The thing is, there is no way to know for sure that you are healthy. Any of us could keel over and die from some previously unknown or suddenly occurring problem at any moment.
You’ve already done your due diligence by checking to be reasonably sure you do not have high blood pressure. Now, you just have to let it go. When it comes to stuff like this, 99.9% sure is the best you’re ever going to do. Accept the uncertainty. It would be a real shame to waste part of the life you do have by constantly checking for something that doesn’t exist.
The best thing for your mental and physical health is to accept you are probably, albeit not certainly, just fine. If you cannot get over this yourself, I highly recommend cognitive behavioral therapy and medication as appropriate. Good luck!