ASET Partners | Senior Fullstack Developer, Senior Software Engineer | Full-time | REMOTE | US Only | Go + Python + React + Kubernetes + Terraform + AWS + Postgres + GIS
ASET Partners is developing a geospatial intelligence platform and we're looking for talented individuals who enjoy working on a small team that moves fast and makes significant impact.
Applicants must be able to acquire a Public Trust, be US citizens residing in the US, and submit to a technical pre-screening.
Reach out to tim [dot] henrich [at] asetpartners [dot] com for more information.
ASET Partners | Senior Fullstack Developer, Senior Software Engineer | Full-time | REMOTE | US Only | Go + Python + React + Kubernetes + Terraform + AWS + Postgres + GIS | ASET Partners is developing a geospatial intelligence platform and we're looking for talented individuals who enjoy working on a small team that moves fast and makes significant impact.
Applicants must be able to acquire a Public Trust, be US citizens residing in the US, and submit to a technical pre-screening.
Reach out to tim [dot] henrich [at] asetpartners [dot] com for more information.
ASET Partners is building a geospatial analytics platform used by analysts across the US. We're looking for individuals to join the small but talented team to help us continue to build out the platform and develop new products and capabilities.
I'd hardly call Kubernetes, Docker daemon and tooling, etcd, CockroachDB, geth, and nsq tiny CLI projects.
If anyone has any reservations about learning Go, don't judge the language based on a list of flaws written by some programmers who used it for a few months, became frustrated, and wrote a blog post.
Go is a language that's easy to use, but a challenge for beginners to use well, especially if you try to force [insert another language] constructs into it.
I see programmers that are new to Go often struggle with trying to apply their object-oriented mindset into a language that's not object-oriented and run into trouble, complain about the language, and call it rubbish. Or, focus on the lack of generics and other part of the language they don't like (e.g. slice manipulation).
Go is certainly far from perfect but after spending the better part of 7 years with it, it's usually the first tool I reach for.
"Go is a language that's easy to use, but a challenge for beginners to use well, especially if you try to force [insert another language] constructs into it."
Strongly agreed. There's a lot of languages out there with very rich feature sets, and the way you get jobs done is to go find the right feature you need for your current problem. With Go, you need to learn the language and extract every last drop out of every language feature. This is exacerbated by the fact that the feature set isn't what people expect, e.g., object composition is not what they are used to, and while interfaces are simple there's still some art to using them properly.
Despite the vast, vast distance between Go and Haskell on the general-purpose programming language landscape, I found my experiences in Haskell to be quite useful in Go, because while they were specifically inapplicable to an imperative language, the general practice I got from Haskell of taking a bizarre set of programming tools and learning how to make sensible programs out of them even so was quite useful.
(It isn't necessarily the first language I reach for for personal tasks, but it is a superb professional programming language, offering a nearly-unique blend of the ability to get the job done you usually need to do for a wide variety of standard programming tasks (but not all!) while resulting in source code that is still comprehensible to almost every programmer. It isn't my favorite overall, but it's the best professional choice of language I have in my belt, which is often precisely because it does not permit me to indulge in flights of clever fancy that solves a problem in 25 impenetrable-to-the-next-guy lines of code. I know a lot of people may not love to hear that, but it's a factor you really have to consider when you are being paid to solve problems.)
Yes, this is plain telephone conferencing and the landing page could definitely do a better job explaining that.
API Gateway + Lambda might still be an upcoming deployment option for this. App Engine was chosen as the initial deployment target because some of the additional features that will be added are cheaper / free for low volume usage when compared to AWS. This already requires Twilio, so releasing this initially for App Engine seems to resonate better.
I was talking about "Twilio Functions". It's new. It happens to use AWS Lambda under the covers, but they don't mention that. You don't need an AWS account.
Elastic Beanstalk's Multi-container environment can be a nice way to ease a project into containerization, but it seems like it doesn't get much love from AWS these days. You're still forced to set hard memory limits on containers even though ECS support soft limits.
ASET Partners is developing a geospatial intelligence platform and we're looking for talented individuals who enjoy working on a small team that moves fast and makes significant impact. Applicants must be able to acquire a Public Trust, be US citizens residing in the US, and submit to a technical pre-screening.
Reach out to tim [dot] henrich [at] asetpartners [dot] com for more information.