jerluc

Thank you! Just fixed

Station A | Staff Software Engineer | Remote (US) | Full-time

Station A is a startup reimagining how clean energy is bought and sold. Our distributed team is made up of climate-minded technologists, strategists, and operators committed to making climate action a no-brainer for everyone.

We combine proprietary software with industry expertise to guide commercial real estate owners and operators through their decarbonization journey, starting with evaluation of their portfolios and culminating in transactions through our clean energy marketplace.

---

Learn more about the role and apply here: https://apply.workable.com/j/2E97BD0B53?utm_source=hn0226&ut...

Station A | Software, marketing, operations | Full-time remote (US-only) | https://stationa.com

Station A is the first AI-powered clean energy marketplace that aims to make clean energy cheaper, more accessible, and more transparent to everyone. Our mission is to transition the world to 100% clean energy.

We are a seed-stage company and passionate team of ten, based in the San Francisco Bay Area. Multiple projects have now run through our marketplace, we have over 2,000 providers in our network, and we have a growing pipeline of more than $600M in clean energy projects under evaluation by buyers. We're now looking to scale our impact and enable anyone to easily power a building with 100% clean energy.

We have four new openings:

- Software Engineer: https://boards.greenhouse.io/stationa/jobs/4186439004 - Senior Software Engineer: https://boards.greenhouse.io/stationa/jobs/4186466004 - Marketing Leader: https://boards.greenhouse.io/stationa/jobs/4186393004 - Operations Manager: https://boards.greenhouse.io/stationa/jobs/4183936004

I feel like there are times when zero values can make things awkward (e.g. boolean flags often need to be expressed in the "negative" form because the zero value is false), but this is a great idea for iota!

Station A | Full-stack software engineers | Based in SF/Oakland, but remote-friendly (NA-preferred) | https://stationa.com

Station A is the first AI-powered clean energy marketplace that aims to make clean energy cheaper and faster to deploy, build a cleaner and more resilient grid, and create an ecosystem that brings more equitable access to clean energy. Our mission is to transition the world to 100% clean energy.

We are currently a team of five, based in the San Francisco Bay Area, and recently closed our seed round (https://blog.stationa.com/2020/seed-round-closed). Our product currently serves over 20 customers and thousands of users. We're now looking to scale our impact and grow our team by adding two new full-stack software engineers to continue development of our product that enables anyone to easily power a building with 100% clean energy.

Specifically, if you're reading this and are thinking "I don't know the first thing about the energy industry," please do not hesitate to get in touch with us anyway! One of our key strengths is in combining diverse perspectives: industry outsiders who help challenge the status quo and industry experts who bring deep knowledge and experience. In fact, I personally started out working in e-commerce, ad-tech, and other "traditional" software companies, and I've found that nothing compares to the impact you can have by working on a problem that matters to you, alongside others who share our passion and drive to transition the world to clean energy.

If you'd like to learning more, reach out to us at careers@stationa.com with a recent copy of your resume and a brief note about why you're interested!

Just a note about Docker performance on Linux vs. others: this is likely because Docker on Linux runs without virtualization as more or less a normal subprocess in a separate cgroups namespace. Windows and macOS must use a virtualization layer (e.g. VirtualBox) to run any Docker process, which for obvious reasons is going to be much less performant.

This model looks to have a fingerprint reader, which may be good news to you. You can see the outline in the main photo, and it is also listed in the tech specs: https://store.google.com/product/pixel_4a_specs

Station A | Full-stack software engineers | Based in SF/Oakland, but remote-friendly | https://stationa.com

Station A is the first AI-powered clean energy marketplace that aims to make clean energy cheaper and faster to deploy, build a cleaner and more resilient grid, and ultimately to create an ecosystem that brings more equitable access to clean energy.

We are currently a team of five (three engineers), based in San Francisco and Oakland, and recently closed our seed round (https://blog.stationa.com/2020/seed-round-closed). We're now looking to grow our engineering team by adding two new full-stack software engineers. This team will continue development of our product that enables anyone to easily power a building with 100% clean energy.

If you're reading this and are thinking to yourself "I don't know the first thing about the energy industry," please do not hesitate to get in touch with me anyway! I too started out working in e-commerce, ad-tech, and other "traditional" software companies, and I've found that nothing compares to the impact you can have by working on a problem that matters to you. In fact, one of our key strengths is in combining these complementary perspectives: industry outsiders to challenge the status quo and industry experts to provide deep knowledge and experience. This will only continue as we strive to cultivate a diverse, resilient, and impact-driven culture.

If you're interested in learning more, reach out to me directly at jeremy[at]stationa.com

There are a decent number of branches, one of which is "fix/auth" which has commits from two months ago (but most are much older as you mention).

Not saying this necessarily means this project is alive and well, but just noting!

Completely agree with this. In my experience, LAB space really makes an observable difference in perception-based applications, as compared to the mostly arbitrary RGB cube space.

My assumption from that sentence is that both "ad malware" and "ad tracking" are injected by some ISPs somewhere between the client and the server. By forcing HTTPS, you'd prevent some amount of this by ensuring the data in transit from client-to-server-to-client is encrypted (and thus mostly tamper-proof) using the .dev domain's public cert.

Station A // early-stage clean energy start-up // SF Bay Area (remote considered) // Senior Software Engineer (full-time) // https://stationa.com

Station A is hiring its first senior software engineer!

Station A’s mission is to enable a carbon-neutral future by scaling and automating the clean energy development process. Our software platform connects clean energy developers with building owners and enables them to plan and execute projects that ultimately take any building to zero carbon emissions.

We are currently a team of four co-founders, based in San Francisco, CA, and recently closed a round of venture funding that we plan to use to scale quickly. We are looking for ambitious and driven individuals to help build a company that transitions the world to 100% clean energy.

If you're interested in learning more, check out the full job description at https://stationa.com/careers/2019/senior-software-engineer or reach out to us at careers[at]stationa.com

For those interested, the original paper on the Bkd-tree structure mentioned in the note about geo_shape updates: https://users.cs.duke.edu/~pankaj/publications/papers/bkd-ss...

Neat! Minor note, I think this should be https://someonewhocares.org/hosts (note the plural)

I don't understand, half of this announcement refers to the fact that this new feature is built upon Knative:

It leverages Knative, which enables autoscaling down to zero and backup to run serverless workloads on Kubernetes.

So what are you referring to?

I'm surprised they didn't consider hosting their own vector tile server, instead of painstakingly rasterizing their entire dataset and optimizing it over and over to fit into the Mapbox data caps.

My company recently hit the need for maps showing several of our own proprietary layers at various zoom layers, and considering how much of the data is already in GeoJSON, converting that to the Mapbox Vector Tile binary format (MVT) was a breeze to implement on our own servers, compared to rasterizing all of the layers and re-rendering whenever any part of our datatset changes.

Just came across this yesterday while planning my new rig!

I'm a bit late to the discussion, but I'm glad to see so many comments here in response to one of the Utility API founders.

Just wanted to note something very important:

As a co-founder of a very new cleantech software startup, and as a guy coming into the energy industry initially with only a background in software, you need to understand that the energy industry (especially in the US) is incredibly diverse and is really an ecosystem in itself.

The market is not just regulated utilities and their customers. There are unregulated markets, power generators, ISOs, cleantech vendors, project developers, installers, financiers, insurance companies, and plenty more players in the space. Each of these actors serves a different role in the process of getting a solar array or battery up and running on a building or out in the field.

And to echo some other comments, the hardware is pretty much all there by now, with prices getting lower by the month, and the only thing that's missing is the right software to help scale deployment of capital, energy assets, installation labor, etc.

[Impending plug is coming]

In fact, this is exactly what my company, Station A (https://stationa.com), is doing. We've realized that in the commercial and industrial sectors, renewables are seeing slower penetration because the high soft costs associated with project development for the medium-to-small energy consumers. This stems primarily from a lack of access to critical data, biased sales tactics (solar developers only want to sell you solar, even if it won't make a difference), and the inability for project developers to really find the right locations to develop with the right technology in a scalable fashion.

This sector is ripe for disruption purely with software, as the hardware has become so much more commoditized.

Our current solution is to use a "toolchain" git repository that helps to automate installation of 3rd-party software (so that we're using similar versions of things like Docker, Python, etc.), but also creates a company-specific directory with installed scripts that can be added to the individual's PATH.

Would love to see a similar post for USB C. I've been trying to find some way of doing a right-angle with these, but without much luck.

There are definitely several ad-blocking VPNs out there. And then there's PiHole [1] if you have a spare raspberry pi laying around on your network.

[1] https://pi-hole.net/

I think the ultimate issue specifically with Facebook is not that you shouldn't give people voices online, but rather that when the voices form small, tight-knit echo chambers with zero outside challenge, the outcome can be disastrous. I believe this is why the author calls it a "walled wonderland".

How can you find yourself at all sympathetic toward Facebook in this context? This is not about saying Facebook's moderators are doing terribly, the whole point here is to point out the fact that Facebook has a major conflict of interest when it comes to the issue of fake news, and they've avoided admitting that fact entirely.

I'm no expert, but I'd imagine fully dropping the quotes wouldn't allow you to use the same syntax as a map/dictionary in Javascript, whereby the keys could be [almost] any type, and string keys could contain characters such as - or even : which otherwise would prove ambiguous to a Javascript parser.

This is great news for me, maybe now I can finally merge my documentation repository with my code repository and have it make sense again :)

On another note, I wonder how I could change my Nanoc deploy to support this new kind of Github Pages setup (currently, it follows this process: http://nanoc.ws/doc/deploying/#with-github-pages-or-bitbucke...).

I would tend to agree, but find it incredibly hard to find any such modern examples of major content publishers using "good" advertising networks, especially in this modern age of social network infestation, 3rd party cookies, and data exchanges.

This is a great idea! I think it really attacks the (outwardly) worst part about advertising: deterring users. That being said, I wonder how this would effect the typical bidding-based models of major ad networks and how this would ultimately impact the ad revenue publishers take in.

Great, can't wait to see publishers "endorse" their advertising partners because they really "love" them so much. I wonder how many publishers would even buy into this given that their primary reason for integrating with an ad network is to make big ad revenue to support their (mostly) content-driven business.

Reminds me of Church encoding or even iota reductions, where you reduce a set of higher level symbols to primitive symbols that in combination have provably the same meaning.

If anything, it would seem that (from these comments and from my own personal experiences) Bluetooth is actually not doing very well at being invisible at all.