> In 2016, the IEEE Computer Society kicked off the SWEBOK Evolution effort to develop future iterations of the body of knowledge. The SWEBOK Evolution project resulted in the publication of SWEBOK Guide version 4 in October 2024.
So the thing called "SWEBOK Guide" is actually the reference text for SWEBOK.
The idea that someone's response to being fired should be the same as a manager's response to one of their reports quitting is hilariously out of touch.
Good advice! A rule of thumb I use is that the sentence should make sense if it was read outside of a browser, which results in roughly the same thing.
Permutive is hiring Scala Software Engineers (100% remote, full-time, optional London office)
Permutive is powering the future of targeted advertising on the Open Web today. As the only Audience Platform built on edge computing, we enable premium advertisers and publishers to plan, build and activate cohorts — all while keeping everyone’s data safe.
We’re a remote-first B2B SaaS company with 180+ people—centered around our London and New York hubs—and growing rapidly. We have received funding from some of the world’s best investors, including a recent $75m Series C led by SoftBank Vision Fund 2.
We’re hiring for Scala engineers in a number of teams. To find out and apply for each one, visit the links below:
You don't necessarily lose the stack trace. Typically the left side of an either is an Exception (or an error ADT that wraps one). When you want to handle the left case, you can log out the full trace as you would without Either.
The Monad instance for Either means that chaining them together with flatMap has a short-circuiting effect and the first failure will stop the rest of the chain from being evaluated. I find this actually makes it easier to know where your errors are happening, and also allows you to centralise your error handling logic.
I'm looking for help validating an idea for a product that provides multi-armed bandit optimisation over an API. The idea is that client sites will provide impression and conversion events to our API, which provides recommendations about which variant to display, optimising performance over time.
I think this could be useful to businesses that currently use A/B testing but am trying to understand if an API on its own is useful enough to be a standalone product.
Please have a look at the site and let me know if it's clear what the product is and if you think it'd be useful. I'd also appreciate any advice on how to validate an idea like this, how to identify problems this kind of product to solve, etc. Thank you!
London is good. I'm a self-taught dev who moved from tech support to QA to engineering. There's a lot of work here and quite a bit of competition, but I wouldn't say not having a degree has been a problem.
I recently started my first Clojure/ClojureScript project using the Reagent template for Leiningen[1]. It gives you Ring/Compojure/Hiccup on the backend for simple routing and views, and Reagent with a client-side routing framework on the frontend. It took me 10 minutes to get it running and figure out what the different components were doing. I'm sure ultimately I'll roll my own setup but this is a good way to get going if you're new.
__START__ mr. speaker , the gentleman is 110 percent right .
the gentleman from ohio mentioned an issue about being nonpartisan and being , i would say , third-party validators , i just want to make clear the supreme court cases made it clear that you could discriminate with your personal church money , but not with federal money .
all of the cases are consistent .
in fact , if my colleagues read the cases , they point out that if you are using federal money , you can not discriminate .
__END__