Anywhere.re | REMOTE (US) | Full-time | https://myjob.io/Taairww
==================
The Anywhere Real Estate Core Capabilities API Engineering team develops reusable, enterprise capability APIs which are leveraged by both internal & external product development teams use to rapidly build and release real estate software.
Our tech stack is: Node.js / Mongo / AWS shop.
We're looking for:
* Strong backend experience
* Strong REST API experience
* Some project/team leadership
* Mongo / NoSQL data modeling experience
* Node.js on the backend specifically. You've worked on and contributed Node.js-based APIs
* Infra / Cloud experience. Ideally AWS
The interview process is fairly straightforward:
* 30-minute experience screen
* 1-hour pair-programming to build an API endpoint in Node.js and JavaScript
* 1-hour system-design
* 30-minute culture fit
I've been using the following to pick up a new hobby (wood working [surprise]) and start learning about potential business ideas (data/ML space and pet industry):
I'm sure there are topics you're curious about or sound interesting to you. Maybe there's a hobby you wanted to try out? Spend a little bit of time watching YouTube, listening to podcasts, reading blogs or joining discord/slack communities for that topic.
This doesn't have to be some huge investment. Spend an hour or two looking at a topic. This can be in 5-minute increments or a 2-hour block, w/e.
Are you still interested? Do you want to learn more about the topic? Do you want to try your hand at it? Go for it. Go as deep as you want on it, actually make your own version of w/e you're interested in.
Now go talk to people in various communities online. There are so many slack and discord groups out there, you'll find something you connect with. Ask questions. Engage in conversations. If you're feeling up to it, reach out to people to setup video calls. Some meetups are starting to offer in-person events, if you're comfortable doing that.
Still interested, still want to turn it into something more? Check out The Mom Test by Rob Fitzpatrick. It's fantastic guide on how to actually do customer development. Doesn't have to be about making something into a business. He's got great tactical advice on how to get info from people in a regular conversation and learn about stuff.
Been working with Rails close to a decade now. I've built several, non-trivial products using Rails for the API, by myself. What I and my coworkers dislike about Rails is the sheer amount of magic. Oh and concerns, let's not forget that pattern.
Rails is amazing at standing up a CRUD app (really API) in a matter of minutes. I can have a basic CRUD app with authentication, authorization, API, caching, background jobs, local development (docker compose), production in any cloud / k8s and CI/CD done within a day. Adding business logic that's well tested is simple.
Once the app starts to get serious usage, needs to integrate with complex enterprise systems, handle huge loads of data, etc. it becomes necessary to step away from Rails-way of doing things. All of a sudden you can't push more into Sidekiq cause of how much it impacts the DB via ORM loading. Now you're writing custom SQL. It's not all that hard to do in Rails, but at that point, you're writing Ruby and not using Rails magic any more.
Your dismissive comment does not address the realities of building a solution that goes beyond CRUD. It ignores the many levels of experience present on a team or the amount of technical debt one accrues while building a non-trivial production system.
While it doesn't take much experience to get started with Rails or to get a good amount of progress on a product, it takes skill to keep the technical debt under control. Or to make good decisions about architecture. Or to understand which parts of the system to optimize. It requires actual experience building web solutions without the crutch of a framework to know when to ignore Rails and when to double-down on it.
I'm with @greazy on this one. The assumption made is that a set of labeled images is enough. Was the training set validated against a diagnosis based on biopsy of some kind? I.e. the images that were trained on, marked by some radiologist (more likely multiple radiologists), how were they validated to contain cancer or be cancer free? Did someone follow up a few years later and confirm the diagnosis was correct?
Also, different modalities will produce different quality images, how was that accounted for in training models? Did they use all the images for a single scan or a subset of the images of a single scan?
The problem is you're trying to train a model where you have many images for a single scan, like slices. Depending on the modality, you'll get different resolutions, different "visual" inclusions, etc. etc. So labeling the individual images and labeling the entire collection is really hard.
Can this be done using existing PostgreSQL functionality around replicas? I think there's a plugin for PostgreSQL that supports master-master replication as well.
First, what are you looking to gain from knowing C? IMHO C is great for embedded programming, that's it. C isn't a great language for "web programming". It's terrible at string manipulation. It's mostly used for embedded and systems programming. Yes, there are plenty of exceptions, but we're dealing with generalities here.
If you're just looking to better understand memory or pointers or something similar, K&R + What Every Programmer Should Know About Memory are all you really need. Throw in a book on linkers and loaders, even an old one, and you'll have more than enough info to understand what most programs are doing under the hood.
I learned the language in school and at the first few jobs I had, all embedded or systems work. If I had to learn it today, I would do the following:
2. I like Learn The Hardway series of books for the tools he teaches. It's really hard to be effective with C without knowing how to use a debugger or some static code analyses tools. https://learncodethehardway.org/c/ You can learn make, GDB, valgrind, etc. on your own too - plenty of O'Reilly books on the topics. I do recommend learning at least make, GDB and valgrind - they will help you build your code and figure out where you screwed up with your pointer arithmetic - which you will do.
3. Decide on what kind of projects you want to work with C. I learned by rebuilding some of the standard Unix utilities (e.g. curl or wget) as well as some systems programs, like a network scanner.
4. Build something a lot more complex, like a bootloader for an Arduino board. As in, get a cheap Arduino nano and write your own little bootloader that will load a simple program that blinks an LED. Plenty of other alternatives, e.g. build a basic git implementation. Try your hand at building a JSON parser - you'll hate strings by the end though.
5a. Get a book on Linux device drivers and go through it; build a few of the drivers - it's really not that hard. The Linux kernel is just another framework. You can also just look at https://kernelnewbies.org/ to see what else you can do and find other resources.
5b. Alternatively, build your own database. Can be a clone of Dynamo or Redis or some kind of RDBMS. You can even build your own pub/sub system if you want. Whatever you're curious about.
6. If you really like working with C, go through a Data Structures course and implement all of that stuff in C. You'll hate yourself but you'll learn a lot about the language. By now, you'll have picked up a bunch of that stuff anyways, but don't let not knowing quicksort algo stop you from building something. All the sorting/searching algos are better learned once you're comfortable debugging your code and looking for pointer issues.
Personally, I love working with C. It can be incredibly frustrating, but it's the first language I learned, so it's my home. In the last 10 years, I only worked with it when doing embedded work. I'll reach for Go as a system's programming language first (haven't learned Rust yet). For web development, there are too many modern frameworks and languages that are much much better than C.
- What kind of software dev do you do and what kind of job are you looking for?
- What industries are you looking to work in?
- Which part of the world are you looking for a job?
- Can you share a link to your resume so people can review it?
- Have you tried sites like Vettery or Hired? My xp with them was neutral at best, but doesn't hurt.
- Have you done anything on HackerRank? Yes, it sucks with all the algo crud, but that's where things are with the industry.
GNU Radio has a guide of how to compile it for Android. Having said that, if you're just trying to run it on your phone, it doesn't (usually) have enough power to do anything "fun". You need more capability than your average Android device. The other option is to have something a little more powerful running GNU Radio stack and then control that via your phone :)
This is awesome, thank you for making this available. Having had to piece this together from multiple books, blog posts, tutorials, GNU Radio, etc. having a single reference is really helpful