Alexander's Sandbox

Outbox Pattern

2020-02-17T00:13:00.003-08:00

Implementing the Outbox Pattern by Sohan GanapathyOct. 25, 2019

Java Microservices in Docker?..

2020-01-31T08:19:00.002-08:00

- А ты точно маргинал?
- Да.
- А скажи что-нибудь на маргинальном!
- В чём смысл пихать Java Spring Boot микросервисы внутрь Docker контейнеров?

Export Tabs URLs

2020-01-13T22:57:00.002-08:00

https://github.com/alct/export-tabs-urls
https://addons.mozilla.org/en-US/firefox/addon/export-tabs-urls-and-titles/

Anon

2020-01-12T07:09:00.000-08:00

GitHub Education

2020-01-04T07:17:00.000-08:00

Github Comic - The Amazing Robopatchers

"GitHub Education helps students, teachers, and schools access the tools and events they need to shape the next generation of software development."

GitHub Guides

RESTful Java with JAX-RS 2.0

2019-12-19T07:01:00.001-08:00

[GitBook] RESTful Java with JAX-RS 2.0
[PDF]

Software Architecture Documentation

2019-11-13T05:23:00.000-08:00

Unified Modeling Language - Wikipedia
4+1 architectural view model - Wikipedia
Architecture decision records (ADR) (aka Design Choices Document)
The C4 model for visualising software architecture
Dependency diagrams

Интерактивная карта миграции в Латвии

2018-09-09T01:08:00.000-07:00

Интерактивная карта миграции в Латвии от Центрального Статистического Управления: migracija.csb.gov.lv

See also Latvian Open Data Portal.

Где сейчас сверкает? Карты гроз

2018-09-08T13:00:00.000-07:00

Карты, показывающие молнии на Планете с задержкой всего в несколько секунд (типа "почти в реальном времени"):
LightningMaps.org
Blitzortung.org

Первый использует (в том числе и) второй, а у второго есть генератор карт.

What went wrong with the IT-industry? - James Coplien

2018-08-19T07:39:00.000-07:00

The other side of Elmar

2018-07-18T08:04:00.000-07:00

(see also)

Как правильно писать коммит-сообщения в Гит?

2018-07-12T01:36:00.000-07:00

Наткнулся на такое обсуждение.

dmytrostriletskyi: Пулл реквесты должны иметь повелительное наклонение.

KvanTTT: Вот кстати меня всегда интересовал вопрос. Я обычно коммит-сообщения пишу в прошедшем времени, что было пофикшено: "Исправлен баг". Но также много встречал и в настоящем, в том числе и в этой статье: "Исправление бага". Как все же правильней?

vedenin1980: Я встречал в настоящем, в прошлом и будущем (если тикеты), более того бывает вместо глаголов просто существительные, бывает народ не парится и пишет по-разному. На самом деле, это как код стайл языка в одном языка записывают переменную как catInterface, в другом как cat_interface, в третьем СatInterface и т.д. Какой правильный? Все они правильные, это спор табов против пробелов, какие правила на проекте/команде/языке приняты — так и правильнее. ИМХО.

pesh1983: Вот тут отличный пост про это с доходчивым объяснением, зачем и почему chris.beams.io/posts/git-commit

Казалось бы "на вкус и цвет", ан нет. Возмущаемся, читаем статью Криса "How to Write a Git Commit Message", потихонечку проникаемся дзеном и переходим на сторону Силы. Таки действительно надо писать в повелительном наклонении: и короче, и Гит сам так делает, и это соответствует философии коммита, как некоему действию над кодом. Применяя соотвествующий коммит к коду, мы как бы даём (исполняем, вызываем) команду, сформулированную в заколовке коммит-сообщения. Очень хорошо, в частности, ложится на черри-пикинг, например.

Elmar, I need more JIRAs today!

2018-07-06T08:42:00.002-07:00

"Чуть-чуть музыки, и всё ОК!" :)

Will, Would, Shall, Should

2018-02-06T06:22:00.000-08:00

"have" collocations

2018-02-05T01:49:00.000-08:00

BBC Learning English

2018-02-04T01:56:00.000-08:00

BBC Learning English

including Tim's Pronunciation Workshop (most episodes require Flash Player)

- a great resource for English learners advised by a competent English teacher.

If you only have JRE... ;)

2017-07-05T06:56:00.001-07:00

[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Unable to locate the Javac Compiler in:
  C:\Program Files\Java\jre1.8.0_131\..\lib\tools.jar
Please ensure you are using JDK 1.4 or above and
not a JRE (the com.sun.tools.javac.Main class is required).
In most cases you can change the location of your Java
installation by setting the JAVA_HOME environment variable.
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:45 min
[INFO] Finished at: 2017-07-05T16:37:28+03:00
[INFO] Final Memory: 13M/139M
[INFO] ------------------------------------------------------------------------

WildFly Swarm in 15 minutes

2017-06-08T06:34:00.000-07:00

"how to have executable Jars, use standard Java EE APIs and write Micro, Nano and even Pico services using WildFly Swarm"

A presentation by Antonio Goncalves (
         @agoncal,
         author of "Beginning Java EE7" published by "Apress",
         Java EE trainer on PluralSight
)
on June 8 2016 at DevoxxUK (
         @devoxxuk,
         flickr,
         voxxed
)
demonstrating an opposite approach to the traditional "package code as war-file and deploy to a JEE application server", using
         WildFly,
         JBoss Forge,
         IntelliJ IDEA,
         JConsole.

Java User Group Latvia - 42nd meeting on 25-April-2017

2017-04-23T10:04:00.000-07:00

JUG LV Homepage
Free Registration for JUG LV #42, Konventa Seta, 9/11 Kalēju iela, LV-1050, Rīga. Kampenhauzens conference room, 1st floor.

Agenda

1. Look ma, no JavaScript – how you can build a modern web app 100% in Java by Sami Ekblad

Building great web apps is not an easy task. User expectations keep growing, and the technologies needed to fulfil them are increasingly complicated. Vaadin takes a very different approach to web development. For starters, there's no need to write HTML or JavaScript. No REST services. Instead, you build your app using ready-made UI components in Java and let Vaadin handle the rest. Come find out how fun and productive web development can be when you cut out all the nonsense.

2. Forget about Microservices, Micromodules is a new Silver Bullet by Dmitry Buzdin & Ilgvars Jecis

Do you think that you should use microservices in your next project, but are afraid of complexity and infrastructure issues? Do you want to find a middle ground between flexibility of system architecture and speed of development? If yes, then this talk is for you! We will go through micromodule architecture, which is pioneered in FinoTech.

We will go through how to combine benefits of both micro services and monolith worlds in one shot.

Rod Johnson on portability of J2EE applications

2017-04-23T09:56:00.002-07:00

Rod Johnson, the father of Spring, wrote in his famous book "Expert One-on-One J2EE Design and Development" (2002):

"Portability is a great bonus of the J2EE platform. <...> portability can be achieved in real applications, but it's not the point of J2EE. The requirement of the vast majority of projects is to build an application that solves a particular problem well on one target platform. An application that runs badly on one platform will never be ported to other platforms (the application might be ported to another operating system that runs on more powerful hardware to gain adequate performance, but that's not the kind of portability that professional developers aspire to).

J2EE orthodoxy holds that an application should be portable across J2EE application servers and must be able to work with different databases. The distinction between these two goals is important, and sometimes missed. Portability between application servers may deliver business value and is usually a realistic goal. Portability between databases is much more fraught, and often provides no business value.

Portability is usually taken to mean code portability: the ability to take the application and run it on another platform without any change. <...> this is an expensive misconception. Naïve emphasis on total code portability often leads to heavy costs in lost productivity and less satisfactory deliverables. Write Once Run Anywhere (WORA), while a reality where Java itself is concerned, is a dangerous slogan to apply to enterprise development, which depends on a range of resources.

<...>

The portability myth has led to wide acceptance that J2EE applications can't use the capabilities of today's relational databases, but should use them only as dumb storage. This does great harm in the real world."

Java User Group Latvia - 41st meeting on 30-March-2017

2017-03-24T08:53:00.000-07:00

JUG LV Homepage
Free Registration for JUG LV #41, Konventa Seta, 9/11 Kalēju iela, LV-1050, Rīga

Agenda

1. Service interaction patterns and anti-patterns by Dmitry Lebedev

Somehow, there are some important things in service-to-service interactions, which are often missed, when we are building our services in a hurry, but later those aspects may play a significant role in your application performance and stability. How to organize service-to-service calls, how to optimize them, what to do in order to make them fail safe, what to do when a request has failed and etc.
This talk is rather a general discussion of available approaches, than a prescription of which library or framework to use, but some Java-related recipes will be given. And as a cherry on top of it all - some real-life war stories.

2. Testing RESTful services: The What, The How and The Automated by Alexey Buzdin

Nowadays REST-like is a default architectural pattern for developing web services. Since Client and Server sides are completely decoupled and each web-service has a client-agnostic interface exposed over HTTP it would be a good idea to test that exact HTTP interface. Thus instead of using UI Automation for end-to-end tests we can use a more lightweight approach with testing HTTP. This presentation will cover my experience of writing robust and maintainable test suits for Java and non-Java web services with Cucumber DSL based on experience with more than a dozen projects.

git clone "fatal: remote error: Invalid username or password" (Windows)

2017-03-02T11:05:00.000-08:00

Проблемка:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\xyz>git --version
git version 2.10.0.windows.1

C:\xyz>git clone -v https://username@hostname.domainname.com/scm/git/superproject
Cloning into 'superproject'...
fatal: remote error: Invalid username or password.

Решеньице

Start / Control Panel / User Accounts / Credential Manager

Ну и там дальше уже совсем несложно.

"А ларчик просто открывался"...

Serverless

2017-02-01T04:04:00.002-08:00

Rewrite from scratch

2017-01-31T05:38:00.002-08:00

A "quote-style conspect" of the (IMO) main points from the famous article by Joel Spolsky.

the single worst strategic mistake that any software company can make: [..] rewrite the code from scratch
[..]
We’re programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We’re not excited by incremental renovation [..] There’s a subtle reason that programmers always want to throw away the code and start over. The reason is that they think the old code is a mess. And here is the interesting observation: they are probably wrong. The reason that they think the old code is a mess is because of a cardinal, fundamental law of programming:
It’s harder to read code than to write it.
[..]
When you throw away code and start from scratch, you are throwing away [..] knowledge. All those collected bug fixes. Years of programming work.
[..]
problems can be solved, one at a time, by carefully moving code, refactoring, changing interfaces [..] Even fairly major architectural changes can be done without throwing away the code.
[..]
when you start from scratch there is absolutely no reason to believe that you are going to do a better job than you did the first time. First of all, you probably don’t even have the same programming team that worked on version one, so you don’t actually have “more experience”. You’re just going to make most of the old mistakes again, and introduce some new problems that weren’t in the original version.

LeSS - Large Scale Scrum

2016-09-14T05:36:00.002-07:00

(via)

less.works
Wikipedia
Google