portray requires your project to be packaged for it's auto discovery - if you get this error and your project has a setup.py or pyproject.yaml in the root (and this is where you ran portray from) let me know and I'll create a ticket! Otherwise - I highly encourage looking at using poetry to setup your pyproject.yaml file: https://poetry.eustace.io/
I saw that as well, late into the project creation. The pdoc3 maintainer claims it's not that - but there are other reasons to want to want to avoid pdoc3. I'm going to be working on replace the pdoc3 dependency with pdoc in a way that is transparent to users.
Thanks so much for this great feedback! I haven't done any speed optimization on portray yet - as both at work and online I tend to organize my own projects as small self contained repositories. Clearly there is a lot of room for improvement there, I have a lot of ideas to make it faster.
And, yes write now Markdown only. I will say - this was a week only project: https://timothycrosley.com/project-2-portray so I think there's a good chance I could improve these points with one more week of time spent :)
I don't actually feel like this solves anything, but instead just adds one more avenue for name hijacking. Now instead of trying to register an angular package first, I'll try to register a google namespace, or similar. If google is taken, I'll make an official_google, or g00gle etc.
Black is amazing. I've added it to all my work projects and will be adding it to all my personal projects over time. My own opinion is that black is the future of Python formatting and it's a long time in coming. I disagree with many of the ways it formats things, but I mostly am just ecstatic to no longer have to discuss these things and just write code. If you are an isort user: isort's primarily goal for the next release is to add a mode that gaurentee's 100% compatibility with black (it can be achieved currently via config options). And of course, I'll be formatting the isort project itself using both isort and Black.
If you are asking if Cons in general or dying, I think that's a definite no. Every conference I've been to lately has only seen tremendous growth: PyCon, PyCascades, LinuxFest NW, SeaGL, etc. However, that is just my personal experience.
Honestly, what you've built looks super solid and polished. In many ways, it's what I wanted hug to be - it's really inspiring to see someone build that.
Note that if you are currently using Falcon, another route to get many of these features is to use hug (https://github.com/timothycrosley/hug) which inspired many of API Star features back in the day - and is part of the Falcon ecosystem. But there's also a lot of really amazing work done in this ecosystem that hug doesn't currently support - I may have a busy couple of months ahead :).
Bottomless is awesome! I've been part of the service for a while now - and only stopped using it recently because my neighborhood coffee roaster (who I'm trying my best to support!) isn't on the service: https://lovelicton.com/pilrim_coffee_comes_to_oaktree.html.
I don't necessarily have ideas about how to improve or expand your service - however since you are in Seattle and utilize Open Source software, I encourage you to hack on some of those projects with the community at our next OpenSource hackathon in Licton Springs. https://lovelicton.com/images/events/2019/hackathon.jpg (our next one is April 29th).
While there is def some sound logic to what you're saying I think the key piece you're missing is paying the same amount of monthly payments enables developers in Seattle to buy a home, which in the end means they are building equity by default while their counterparts in NYC could live their whole lives paying rent that keeps going up.
It's not hard. And they're not. You're friends are paying 1K-1.5 to have a room. In the end if you have to pay as much for a room in city A as a whole apartment or mortgage in city B, you are getting paid less. To expand, both the the average and median price per a room per apartment is readily available and easily calculable. If a 2BD is 4K in city A and most people put 4 people in that apartment that doesn't mean all the sudden that it's the same deal as the same 2BD in city B that only cost $1K a month because most people don't share the space. The share cost is still a function of the actual cost, and easily computable and available in every city. Many people in Seattle split apartments and pay 500-600 per a room. They just aren't forced to because on average per cost of goods they get paid more. If anything Seattle has the calculations set up against it, as it has much much smaller city boundaries than NYC.
You sort of prove the cherry picking argument. Average salary means nothing in a vacuum without cost of living considered. And when it is... Unsurprisingly NYC comes in at the bottom of the list, https://www.codementor.io/blog/best-cities-software-engineer... Seattle is actually #1
Way to spin trying new ideas and having determination to find a way to succeed despite failures in a negative light? The fact this has become the norm is good! People used to think that all the smart people just came up with a good idea all the sudden out of luck, and never failed. The reality is the people who succeeded in the past in spectacular fashion, are the same people who failed over and over again in spectacular fashion (pivoted).
This has happened to me on both services. It's inherent to the whole concept and has nothing to do with Lyft. If you ride enough it will happen to you to. The other day I ordered an uber, it was 5 minutes away, it drove to an entire different city, but uber wouldn't let me cancel without charging me, until 20 minutes had passed.
Even if you were right, and someone made 20% more total compansation, they would loose more than half of that right off the bat due to the mutliple layers income tax in San Francisco, and easily the rest and then some to increased housing cost. Not to mention Seattle tends to have a much more relaxed and healthy working culture, so your probably working less hours too.
This is all about perspective. Now that's definitely the case with AWS and service first design etc. But from the beginning it was trying to be a bookstore, an online one, for sure. But not pure technology, as say a search engine or an operating system - that don't require much integration with existing physical infrastructure.
The same people who make 300-400k in San Francisco, also do so in Seattle. I don't know where your getting your information from, but all existing stats disagree with you for a reason.
Eh, it doesn't really matter what stats you drive from they all paint the same picture. More and more engineers are moving here from San Francisco for that reason. People never report that there leaving net income on the table, especially once they have enough to be comfortable, and most never even search to look.
Not as many as San Francisco, but there's a ton of startups here and the city has a solid startup culture: https://www.geekwire.com/startup-list/. Some notible ones include Zillow, Redfin, Rover, and OfferUp. I agree houses are getting to be too expensive for most, but for those in the rental market things are increasing, but the Outlook looks good as soon many units are getting built.
What your describing is not a lack of engineers, it's a low uneployment rate. There are enough engineers for 100s of new startups. The only thing that excarbates more than San Francisco, is that there is much less a culture of jumping ship here, which is good for companies long term. Also, it's much easier to convince engineers to move to Seattle than San Francisco, which is probably why we are growing at over 3x the rate.
100% agree. We are doing better than most tech cities right now, but that's unfortunately a low bar. I want us to build so much that anyone who wants to live or start some crazy business here can without hesitation.