dscpls

Organisations that have existing business processes to publish to print and pdf but now want to publish in responsive formata for mobile or even desktop web.

Changing their process might be more expensive than paying a lot of money for them to carry on as is for a few more years while getting the benefit of modern eyes on their content.

Edit: concrete example would be government publications like budget narrative documents.

I'm literally repeating words and phrases from the talk.

Please point out my

- baseless assertions

- gratuitous blanket personal attacks

Right now it looks like that's what you're doing, because I don't see that in my comment.

Did you watch the talk to the end?

Edit: line breaks

Awesome talk. Especially connecting how leaving an entrenched mindset behind applies both to architecture and to diversity in our communities.

And that our meritocracies are not as pure as we'd like to think.

Yeah while I think one of the hardest parts if a software developer's job (working at multiple levels of abstraction), that's literally the job. You're translating between the business and the sillicon.

By all means restrict yourself to assembly but yhe rest of us will get more done by using things at convenient levels of abstraction for those specific units.

This says it's very either or, and I think misses the point of a lot of nocode tools.

One of the best measures of tools is their composability. Can you use this for what it's good at, and integrate that solution with another tool that's much harder to use but can solve the last 5-10% that's just too hacky or not supported directly by this tool?

For my that's where zoho creator falls down a bit. Their APIs are just web form post handlers. But it works!

We're doing a lot of stuff on webflow by dropping some custom javascript in there to hook it up to an API or do some very data-driven stuff beyond their interactions.

The point is, nocode isn't just for proofs of concepts, although it's great for that.

When evaluating nocode tools, look for integration/extension points, and think about your migration path should you need to replace it. Hopefully you're succefful enough to need that but don't build 100% of your app by hand because 10% actually needs hand-written code.

Always amazes me that people find it necessary to downvote a comment like this

This is the best comment here

Why a service and not a library?

It looks like a great way for you to discover URLs but like a terribly slow way for people to avoid implementing robots.txt rules.

Wow. I literally just sat down to relax after building a cardboard prototype cat door fitting in my open window in winter. You just made me feel partly inferior, and partly like I'm in good company

Do we have any evidence that these issues are really the causes of people consuming news elsewhere?

- Clickbait headings with misleading information

Does this really put off more than about 10% of people? Even if people find it distasteful, do people actually resist clicking?

- Disabling the user from reading if ad-block is present

What percentage of users use ad blockers these days? And how many just disable it to read the thing they were willing to click for?

- Tracking the user with 3rd party scripts

Ok who actually leaves a site they believe tracks them? like 0.0001% of web users?

- Taking massive performance hits (specifically on mobile due to huge JavaScript blocks)

Maybe getting closer to what users actually care about

- Pop-up ads

Again - any evidence this puts normal internet users off so much they'd stop using a site? There must be a reason MEDIUM.COM and every single recipe blog pops up their newsletter subscription as intrusively as possible.

- Fixed headers or footers which leads to harder readability / accidental element interactions

Here's again an actual deterrent - if someone physically can't use a site, they might actually give up.

---

I'm not saying news sites are not dumpster fires, but I'm a techie and love a good boycott.

I'd question the premise of this article - it seems to be very much from a techie privacy-active (not just concerned, but actually willing to take action) perspective which I suspect does not represent the majority of the internet.

I suspect that if people are actually using news sites less, it's because of much simpler reasons...like that Google intercepts a user's attempt to read news linking to their favourite publications.

To be fair, erlang would have been the better choice here. Memory safety, concurrency and solid error handling all in one.

Erlang tends to have excellent cpu utilisation if you follow the most basic principles in Erlang and OTP.

The question is if you cannor want to write better concurrent code by rolling it yourself.

I could make the reverse argument: bad frontend programmers who dont use the facilities available to separate concerns create unmaintainable spaghetti when good backend programmers who separate concerns properly produce beautiful maintainable code.

The key being bad programmers dont isolate concerns and good ones do.

Why not firefox on mobile? Been using it for months and about as hapoy with it as firefox on desktop

Why would a tech solution change matters? I mean yeah having it all in one place helps, but it's all out there already.

What else is needed to make.it actually work?

How do we feel about this with regard to net neutrality? Are we ok with the blocking they choose to do here because we agree with them ethically in this case?

There's no question sails can move today's cargo volume. But the shape of the ships doesn't lend itself to sail power. I think these sails are specific to supporting other power. And the shape of today's ships is very much towards fitting more cargo. I think you'd need at least slightly bigger ships that are efficient for sail power alone, and able to carry similar cargo volume or mass.

I don't think it's necessarily two fundamentally different personalities (unless I have multiple...which I might...)

I grew up taking things apart, and I loved the courses where we build logic gates or modified compiler or interpreter code.

I now build things on the shoulders of giants.

But when I need to, I know I can dive to the deepest levels to debug something, or I can write or customise any part of the stack.

It sure is a mindset shift and a context switch. I consider choosing the right moment to switch approach to be one of the most important and hardest tasks of developing software systems.

I think it's as vague as it sounds. But the stereotype is probably something like translating rows to columns; or normalizing a column; or creating a composite column

Also look at kobo toolbox and kobo collect. They're based off the odk and forhub codebases I think.

Kobotoolbox provides a useful interface for previewing your data and building forms. Also an api for pulling collected data into other platforms

As long as we call it a company, its raison d'etre is precisely to maximise the value for its shareholders. A non-profit has the freedom not to, and can focus on a core mission. As much as I'd love to believe in social entrepreneurship, if you define yourself as something which by base definition maximises value for shareholders, that's what you're gonna have to do when push comes to shove.

So sure - some kinds of organisation can and do provide social glue. The problem is, the capitalist notion of organisation doesn't support this. Not to imply I'm against capitalism - it has its benefits, but social glue is not it.

Nice resource, thanks!

Note that this is exactly why they teach you not to rely on your gps for navigation between rocks. You should be using sightings, log and compass. And that's why you dont leave anchorage in fog.

Are you sure? AFAICT their method only uses debugging symbols for training. I haven't read it all but it would be a big omission if they didn't mention that it only works on binaries with debugging symbols. When actually reversing they work on numeric "symbols" for the assembly instructions.

One of the best punny titles I've ever heard. Well done. Really well done.

If you qear glasses, get contacts now!

syntactic analysis is generally a precursor to semantic analysis

EDIT: but sure, this is only the first step and semantic parsing is far from solved

This inference of "making implies jobs therefore make things" is just short sighted. Is making things really the _only_ option of making providing jobs?! It's not realistic when there's nothing more we need to make and consume!

I say gopher it!

I'm not impressed that they say condoms are not effective