Location: Tbilisi, Georgia
  Remote: Preferred
  Willing to relocate: Yes
  Technologies: TypeScript, React, React Native, iOS / Swift, Node.js, PostgreSQL
  Résumé/CV: on request
  Email: afidrya81@gmail.com

I currently hold a position as a Software Architect at a software consultancy, but I'm not attached to the title. I can quickly prototype things on my own, making me ideal for bootstrapping startups, or I can assemble and train a team.

For the past 7 years, I've primarily been working with, and am most proficient in, TypeScript, React, React Native, iOS/Swift/ObjC, Node.js, and Postgres. I've worked with many other languages and technologies and can easily pick up new ones if needed.

Here is a list of some other languages and technologies I’ve worked with previously: C, C++, Ruby, Rails, Lua, PHP, C#, .NET, Java (J2ME), OpenGL, WebGL, Cocoa, Qt, QML, MFC, ATL, QNX, Linux/Windows device drivers, Blockchain (miner development, wallet integrations, monitoring, Solidity), etc.

Another approach that can work is to give your memory a bit of time to adapt. For instance, if you're asked to share a story from the past and you don't have one prepared and can't recall anything, suggest starting by discussing your past in general. For example, list the projects you've worked on and briefly describe them. You will feel how, during this process, the ability to recall events returns.

Comments URL: https://news.ycombinator.com/item?id=36741026

Points: 3

# Comments: 0

I think an easier way is to find script's location and construct paths for accessing script dependencies, for example (works on Linux & macOS):

  script_root="$(cd "$(dirname "$(readlink "$([[ "${OSTYPE}" == linux* ]] && echo "-f")" "$0")")"; pwd)"
  source "${script_root}/common.sh"
  source "${script_root}/packages.sh"
  source "${script_root}/colors.sh"

  Location: Europe (PST is also fine)
  Remote: Yes
  Willing to relocate: Yes
  Technologies: TypeScript, React, React Native, NodeJS; Swift, ObjC, C++
  Résumé/CV: Upon request
  Email: afidrya81@gmail.com

Looking to join a team as a full-time contractor on a 3+ mo project. Small teams / early stage startups preferred. Relocation is possible if needed.

Also it'll be harder to go back and review changes when troubleshooting issues because formatting changes were squashed together with business logic changes. With merges at least there are still original commits available, and it'll be possible to either rollback everything or a single commit.

  Location: Russia (UTC+3, but any TZ is fine)
  Remote: Yes
  Willing to relocate: No
  Technologies: TypeScript, Swift, C, C++, ObjC, React, Electron, Node, Docker, Docker Compose, PostgreSQL, Qt
  Résumé/CV: On request, please email me
  Email: afidrya81@gmail.com

Previously I've worked on wide variety of projects such as multi-tiered web apps with SSO, Shopify / WooCommerce plugins for delivery services, Linux device drivers, video streaming apps, mobile banking apps and so on.

I'm always open to learn something new, particularly interested in Rust and Go.

- https://bugzilla.mozilla.org/show_bug.cgi?id=1548679

- https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...

  const [x, setX] = useState()
  useEffect(() => {
    let isMounted = true
    someAsyncFunc(result => {
      if (isMounted) {
        setX(result) // should not be called on dismounted component
      }
    })
    return () => { isMounted = false }
  }, [])
  return 

Imo choosing a different name for new useEffect would be better (like useAsyncEffect or introducing a parameter), because just changing its behavior won't even result in compilation errors or guaranteed run-time errors, only make old code unstable.

Is there a way to reliably detect if component is still mounted before updating it when doing async operations in effects?