bgnm2000's comments

This is really cool, but I would need the dates with the results.. if I'm looking up something technical, dates really matter as libraries change etc.

I’m a designer who codes, and for those who have had trouble expressing the value and finding a role that enables both, here is how I’ve positioned it:

As the primary designer for a product, who can also implement the design - the amount of communication needed between design and engineering literally evaporates.

I tell my devs they can build an ugly v1 of any feature simply for the sake of speed, and I’ll go in after to clean it up and make it look consistent. they don’t need to waste time with CSS.

Design changes so often after implementation, that I don’t even keep a living design file, most changes happen directly in code. If I do need to design something as part of a pitch or meeting material I take a screen shot of the product and just modify that.

Having worked as only a designer, and then only as an engineer, I can’t express how much faster my team is when design is part of engineering.

Speed is most critical to startups, I’ve always found interviewing with startups and presenting this skill set is highly sought after when expressed properly.

thanks! We agree - this tech is really going to change how quickly someone can find the information they care most about in an event

Hey everyone - today we launched a demo for people try our “ChatGPT” like tool (but not using ChatGPT) for asking questions about recent Wall Street events. Would love any feedback!

Aiera | Senior Software Engineer | Remote | Full-time | https://www.aiera.com

Our platform analyzes events relevant to investors, company financials, and textual data to give investors an edge.

Our back end consists of Python and node based micro-services. We also utilize machine learning and big data to analyze equities and events, and to transcribe and analyze audio. We capture and re-broadcast audio via WebRTC, SIP, HLS, DASH. Our APIs are a mix of REST and GraphQL. We utilize Docker, AWS services, Terraform.

You may be a fit if:

* 3-5+ years of professional software development experience, ideally some of which was spent in a startup or fast-paced environment, but this is flexible for the right candidate * You enjoy thinking about systems design, and diving deep into the details * You are a self starter and can make decisions quickly * You have good communication skills and can support project stakeholders * You have experience working with Python, SQL, GraphQL, AWS, Docker, ElasticSearch * It would be amazing if you had WebRTC, SIP, telephony, experience, but is not required

reach out to elliot [at] aiera if you're interested!

> Why do you have a giant list of potentially stale bugs?

Most places I've worked have a bug log? Priorities balance between new feature development and fixing bugs / tech debt. If a bug isn't high priority, or the feature it was about has been changed or removed, the bug might now be stale - but still exists in a list somewhere.

> The policy described in the linked-to article is roughly equivalent to saying that every bug/issue must be passed to someone, who is in charge of that issue, including closing them.

It's the opposite, it's saying that if the bug / issue isn't easy enough to be solved right then, it needs to be reported again later, or added to the official prioritized road map.

> What happens if the stakeholder's sanity runs out first?

This is a good question :)

Obviously you’re entitled to your opinion. We don’t have jr. members on our team, but if we did, they’d be assigned a project like anyone else. If the project was a bug, that would be reasonable. This process is for the intern and every other dev to avoid reading a giant list of potentially stale bugs anytime they have a short gap between work. it keeps them working on A) what they were assigned, or B) something small that people have been clamoring for.

I have worked with only 2 architects who have made me understand what it means to be a good architect. 1 they make sure the code is organized in a meaningful way - consistently, and using places and patterns which make it feel easy and obvious. 2, they determine the code conventions used in a project and help to enforce them with tooling (git hooks, generators, PR reviews etc).

This helps scale a team, and build a cohesive lightning fast unit.

I’ve worked with fantastic devs in the past who had no real understanding of this kind of “architecture”, and as a team the difference was clear.

Love the design, looks great!!

React can make people better javascript developers.

A little over a year ago I was building an app, and decided I'd have literally no backend at all. I wanted to build something fast and ship it to the appstores as quickly as possible to go through the process. After I launched, it was featured by apple and was getting thousands of downloads per day. Users wanted to be able to save their data across devices - but it wasn't something I really had time to build in the ways I had in the past. I had heard what Dark was up to, and was lucky enough to join the beta. Dark now powers the backend for my app (nzd.life) - and I really can't express just how amazing it is to use. We added the functionality in just a weekend with a handful of LOC. Dark really is a game-changer. For any entrepreneur / dev who wants to move fast and ship things, they should try Darklang ASAP.

I have a side project running on Dark, highly recommend

I’ve used Dark for the backend of a mobile app (> 20k installs) during the beta, and it has been an incredible experience. Something like 30 lines of code do it all.

Dark is a game changer in my opinion for getting a prototype online as quickly as possible, or a lightweight backend - and I imagine it can and will support much more.

This was an interesting take, but personally I think lands with something that misses the mark. I collaborate with my team in slack. I’m really using github to get to my files quickly, view history, or I jump to issues. Any collaboration on github I would say is largely secondary (from my personal experience anyway). Nobody on my teams has ever been waiting on Github for any type of real-time activity, so even PRs review requests are generally communicated through some type of chat.

Personally I feel the author’s final design is also a step backward - while I realize things have been “cleaned up”, a horizontal menu with that many options is too many - and they are not of equal value. The existing division is helpful based on real life use - not the authors idea of what looks good. I don’t need menu items I rarely touch given the same importantance of the ones I use daily - I don’t want to even accidentally read them - it wastes my time. Also, how quickly does this need an alternative solution for narrower screens? Lastly, the authors design is looks to me just like stack overflow - I don’t think it’s fair to say it’s any more modern than githubs current design which has strong and consistent visual language I appreciate as a benchmark for how other products could look and feel. Github looks like GitHub in every part of GitHub, and for me at least, that’s a good thing.

That video demo is great - is it happening in real time?

I was thinking the first is Mint

I think many people are missing the inherit value of a decentralized currency. You trust your government today, and you have a stable currency. If that is not the case tomorrow, you will wish you held crypto.

It's simple, eyeballs, ads, and data. They can directly measure the value created through ads posted on those properties - and that scales up with the amount of potential ads. Then you have future value of the data being generated (personal habits, info on Facebook, watching patterns by demographic etc on YouTube).

For Reddit, it's one of the biggest communities online (maybe the world?) - there are many ways to leverage and monetize that even if they haven't figured out all the optimal ways to do that yet, the perceived value is enough to convince investors in its future.

I have a section called "notable projects", which lists about 4 or 5 in detail (I don't believe that resume's need to be a single page). But generally - the cover letter is always more important anyway (and especially if you don't have an intro). I usually like to try and tie why I'm the right person for a role, to some specific work I've accomplished in XYZ side project.

This is the only answer. I'm self taught, but even after working with different software companies for years, side projects are always the thing that gets me my next role.