For example: demisexuality. Many that don’t identify as demisexual but hear of the term dismiss it altogether. Others that are members of lgbt fear that cishet people are trying to invade lgbt by splitting hairs.

Link to listing: https://www.ebay.com/itm/383666896955

Announcement from Vulfpeck member Jack Stratton: https://twitter.com/vulfpeck/status/1291766802817540102

This announcement came out of nowhere this morning and the eBay listing will likely continue to grow. Will be interesting to watch to see how much this spot is worth, and who ends up buying it.

Some songs from their latest album:

Radio Shack
Bach Vision Test
3 on E (feat. Antwaun Stanley)
Test Drive (Instrumental)

What have you been listening to this week? You don't need to do a 6000 word review if you don't want to, but please write something! If you've just picked up some music, please update on that as well, we'd love to see your hauls :)

Feel free to give recs or discuss anything about each others' listening habits.

You can make a chart if you use last.fm:

http://www.tapmusic.net/lastfm/

Remember that linking directly to your image will update with your future listening, make sure to reupload to somewhere like imgur if you'd like it to remain what you have at the time of posting.

As part of a weekly series, these topics are a place for users to casually discuss the things they did — or didn't do — during their week. Did you accomplish any goals? Suffer a failure? Do nothing at all? Tell us about it!

Hey everyone,

I've been programming for some time now but notice without any formalized education in CS I often get lost in the weeds when it comes to developing larger applications. I'm familiar with the principles of TDD and SOLID - which have helped with maintainability - however still feel that I'm lacking in the ability to architect a properly structured system. As an example, I'm currently developing a flask REST API for a website (just for learning purposes). This involves parsing a html response and serializing the result as JSON. I'm still quite unclear as to structuring this sort of thing. If any more experienced developers could point me in the right direction/offer up their opinion I'd be very appreciative. Currently I have something like this (based - I hope correctly? - on uncle bob's clean architecture).

Firstly, I'm defining the domain model. i.e the structure of the API response. Then, from outside in.

1. Infrastructure (Flask): User makes request via interface (in my case a request to some endpoint)
2. Adapters: request object checks if the request is valid (on the way back it checks if the response is valid) - Is this layer only for error handling?
3. Repository: I'm struggling a bit here, AFAIUI this layer is traditionally a database. In my case however, where the request is valid, is this where I should handle the networking layer? i.e all the requests to return the website source? I'm also confused given at this stage I should be returning the relevant domain model, like an ORM, but as my data is unstructured, in order to do this I need to transform the response first. Where would it be best to handle this?
4. Use Cases: Here I transform the domain model depending on the request. For example, filter all objects by id. Have I understood this correctly?
5. Serializers: Encode the domain model as JSON to return from flask route.

If you got this far, thanks so much for reading. I really hope to hear the opinions of more experienced devs who can steer me in the right direction/correct me should I have misunderstood anything.

I am a fullstack developer that spends a good portion of my time building out complex User Interfaces, and the rest building out back-ends for that software. In my opinion the current method that my company uses for a designer to developer hand off is a bit lacking in efficiency.

The current method is usually a designer will provide a developer with a Photoshop (or very occasionally an Illustrator) file containing the entire applications design. It is then up to the developer to export assets (both quick exporting things as pngs, going through and separating shadows from assets, or creating assets from the layers provided) and dig through the file to determine fonts and placement of items.

Is it a common expectation that a developer should be spending a good chunk of time in Adobe on asset manipulation?

Additionally does anyone have any process or program suggestions that may make life easier?

I’d like to suggest the practice of posting smaller excerpts. Long excerpts are less likely to be read and resemble articles in themselves.

Their comprehensiveness may render them irrelevant, and demotivate readers from going to the source before commenting.

IMHO an excerpt should generally have no more than two paragraphs, with exceptions for long reads (3500 words+).

For reference (and out of personal choice), 750 characters may be an ideal max, give or take.

For me it would be my pocket knife. I grew up on a farm where it's pretty important to have one and I never shook the habit. I don't use it often these days, but when I do need it it's really nice to simply have it on hand.